F-Droid.org is just a repo out of hundreds of repos created by individuals all around the globe. With the tools of F-Droid, everyone can create their own repo.
with Repomaker, you are able to create your own repo and do not need to have any special knowledge to do so. Check out the installation guide for information on how you can install Repomaker on your device.
@ruihildt I found some time, and was able to create a working package based on the Gitea package. The source code can be found on my Codeberg profile.
https://codeberg.org/bart/forgejo-app
This is my first Cloudron package, so let me know if there's anything I can improve.
@LoudLemur said in Forgejo:
These are quite a lot of questions, and I will do my best to answer them to the best of my ability.
It is fantastic that you discovered Cloudron. We need more people like you. How did you find out about Cloudron? What was it that persuaded you Cloudron was a platform that you would like to support?
I discovered Cloudron a couple of years ago on r/selfhosted. I was already hosting multiple services using different deployment methods: Docker, Snap, and binaries, so I never really gave it a chance.
The problem is, since I only use open-source software, I self-host all the software I use. The applications I host are all critical infrastructure for me, and self-hosting was beginning to take up more and more hours of my day, which is hard if you already have a day job. I had less time to experiment and was losing the joy of self-hosting.
Since I discovered Cloudron a few years prior and needed to remove the burden I was experiencing, I decided to try it out. It is so much easier than what I was doing before. I bought my license the same day and have been a happy customer ever since.
What do you think might make packaging applications for Cloudron easier? For example, if there was a team of packagers with different roles and working to a monthly schedule, maybe that would have helped ease onboarding.
I've been a software developer and open-source contributor for a while, and I think one of the most important aspects of having an active community is having core developers who are as excited about your contributions as you are. Make sure the contributor is recognized for the time and effort they put in and that their opinion is respected by having them participate in the decision-making process. Having these contributors be part of some kind of Hall of Fame or team of recognized contributors seems like a good way to do this.
When specifically talking about package development, I think it needs to be easier for people to install and test packages that other developers have created.
Did it take you long from discovering Cloudron to going ahead and packaging? Maybe it was very quick, but it might have been a while till you decided to begin.
Well, I discovered Cloudron a couple of years ago and have been a customer since the beginning of last year. I was always interested in creating my own package, but this is the first time I gave it a proper go.
One more fun question: Which Cloudron supported application makes you feel good that it is there? Why do you like it?
That is a tough one, there are so many applications to choose from. I am choosing Nextcloud because my family and I have been using it for multiple years now. It is a very versatile piece of software. I previously hosted it using Snap or rented a Storage Share from Hetzner, however, the ease of hosting it using Cloudron is great.
Webtrees is the web's leading on-line open-source collaborative genealogy application.
There are a few packaged versions on Docker Hub already
@LoudLemur said in Forgejo:
First of all, what prompted you to package an application for Cloudron?
Given some of the actions the Gitea developers have been taking over the last couple of years, I really want Forgejo to be available on Cloudron.
How was your packaging experience? For example, was the documentation stronger in some areas than in others?
The documentation provided all the necessary information for me to create this package. I'm not sure in what areas the documentation could be improved. I may change my mind about this when I start making other packages that need to be built entirely from scratch.
After you completed the package, are you left with the urge to package another?
Yes. Developing this package wasn't difficult, especially since I built further on the Gitea package. I just need to find an application that I want to package and use myself.
Do you think you might suggest packaging apps for Cloudron to other developers?
Sure, I think it is important for developers to contribute to the community by also developing packages.
@LoudLemur I hope these answers answer your questions. Please let me know if you have any further questions.
