Forgejo
-
What do you mean?
For example, could the Cloudron project be hosted on Forgejo? Also, I think there is a github requirement for an application to be supported on Cloudron, so could Forgejo be used as an alternative to this requirement? (If that requirement is indeed real.)
-
@LoudLemur I too am unclear about your question.
There's already Gitlab, Gitea and Gogs on Cloudron.
Doesn't mean Forgejo can't added, of course. -
@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.
-
@timconsidine said in Forgejo:
@LoudLemur I too am unclear about your question.
There's already Gitlab, Gitea and Gogs on Cloudron.
Doesn't mean Forgejo can't added, of course.I think @LoudLemur meant could Cloudron itself host it's own code on Forgejo instead of GitLab.
Presumably the answer is yes, but why? Not broke, don't fix it, etc. (although I guess the - actually pretty good - answer is because it's 100% free software maintained by a nice community driven non-profit instead of a large for-profit open core project like GitLab).
Some back story here: https://forgejo.org/2022-12-15-hello-forgejo/
-
@bartmathijssen brilliant, thank you!
-
@bartmathijssen said in Forgejo:
This is my first Cloudron package, so let me know if there's anything I can improve.
Thank you very much for packaging forgejo for Cloudron! I hope that it is made available soon.
Please let us ask you a few questions about the packaging. First of all, what prompted you to package an application for Cloudron? How was your packaging experience? For example, was the documentation stronger in some areas than in others? After you completed the package, are you left with the urge to package another? Do you think you might suggest packaging apps for Cloudron to other developers?
It is great to have you here!
-
@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.
-
@bartmathijssen thanks for the package! Have to discuss internally though how to proceed with this. Nothing against Forgejo but given we have very similar apps (as in both the projects it's forked from), we have to check whether we want to take this maintenance burden.
-
@bartmathijssen said in Forgejo:
Please let me know if you have any further questions.
Thank you very much! These are great answers, and it is kind of you to offer to answer some more.
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?
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.
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.
One more fun question: Which Cloudron supported application makes you feel good that it is there? Why do you like it?
-
@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.
-
Thank you very much indeed for taking the time to answer these questions. I hope that team Cloudron will find your replies of interest. I think they will!
We were fortunate that you decided to package an application. I think one way Cloudron could improve faster is by recognizing at an earlier stage when we have a talented developer in our midst and then offering them some encouragement or incentive to start participating. I hope Cloudron can work out a way to do this. Perhaps offering some sort of voucher in exchange for packaging to a required standard.
Perhaps Cloudron could be more direct with new users and offer a Typebot form to onboard and even task people, if they indicate they might be willing.
I also note that Cloudron let a year go by without a contribution from you. Anonymity is important and good, but if we had approached you earlier all this might have happened a year ago. There might be another developer who arrived at Cloudron today, and we won't have any packaging from them for a year because we aren't in conversation.
In my experience, there are usually a few, key sites which bring in the bulk of people. In your case, it was /r/selfhosted. I think Cloudron could investigate which are the best sites like that and try and establish an active presence there. I don't know what sort of marketing effort Cloudron has. I imagine the core team are far too busy on coding to manage these other aspects of the project, too.
Thanks for telling us your fun application. I like Nextcloud too.
-
Thanks for the inspiration folks ! I'm developer myself and would be happy to contribute to package Cloudron apps as there are some apps I want to use and I'm not the only one, of course I never dig into the docs of how to package Cloudron apps but I'm not too scared
(I'm usually busy at SRE/DevOps and Development/Automation tasks on day2day for the last 14 years and still enjoy it). -
@MorganGeek said in Forgejo:
SRE/DevOps
DevOps stands for Development Operations, and SRE stands for Site Reliability Engineering.
Excellent! I am keen to hear what sort of apps you might like to package. Do tell! It is quite exciting to hear.
Maybe there some other developers lurking who might like to try, too!
-
I moved from Gitea to Forgejo some time ago (https://www.tobru.ch/migrating-from-gitea-to-forgejo/) and don't look back. It would be fantastic to see Forgejo in Cloudron (maybe even move from Gitea to Forgejo so that not both have to be maintained?)
