Create a collection/organization of CI examples for Codeberg Pages #498

Open
opened 2 months ago by adnan360 · 6 comments

I created some Drone CI yaml configs for popular static site generators for Codeberg Pages. So far I have these:

I think there should be a collection of repos somewhere to showcase that this is possible. GitLab has something similar. It works as a template for people starting out and works as a reference.

Just found this issue from which I learned about Woodpecker and other CI options. I haven't looked into them yet, but I think configs for them should also be in a repository somewhere if people want to use them. Maybe they can be under different organizations or the same, I don't know. Feel free to discuss.

Feel free to use my repos above for anything (consider CC0/public domain).

<!-- NOTE: If your issue is a security concern, please send an email to contact@codeberg.org (and if related to Gitea also to security@gitea.io) instead of opening a public issue. Thank you. Welcome to the Codeberg Community Tracker. This is the right place for bug reports, feature requests and feedback. It's the central place where we track progress and discuss, so please open issues here unless you are sure it's directly related to a specific Codeberg product and only some contributors there need to join the discussion. Easy rule: If you are unsure, report it here. When reporting bugs or asking for features in the software itself, please understand that Codeberg is a fork of Gitea. Please always check upstream (→ see FAQ) if your there is already an open issue. If not, you'd really help us if you could directly get in touch with the maintainers and open an issue here if you think a wider audience should know about that (e. g. when discussing hotfixes, backports or when discussing whether some feature should become part of Gitea or a Codeberg "add-on"). If you don't have a GitHub account, please mention this and we'll gladly forward your report to the Gitea maintainers. Thank you for reporting your findings and giving feedback on Codeberg. ## Some FAQ: ### What does upstream mean? Upstream refers to Gitea, the software Codeberg is built upon. If we ask you if you can report upstream, please visit https://github.com/go-gitea/gitea/issues and check for the bug there and report elsewise. It's usually good if the person interested in a feature or bugfix opens the request to react to questions and join the discussion. We would usually just fire the report, but won't find the time to properly react to that ... **If you do not have a GitHub account**, just tell us and we'll happily forward the report for you. ### I just noticed a typo in the sign_up / sing_up route when regis... No, this is not a typo, but intentional. It was a quick fix to avoid spammers targetting our instance and it actually worked out quite well to rename the route from sign_up to sing_up (few people notice, nice to see you have sharp eyes) ... we might have to take more effective countermeasures in the future, but for now we're actually quite good with that one ... ### How can I help? If you want to help improving Codeberg as a community home for software development, we'll gladly welcome your contribution. Check out the docs about improving Codeberg https://docs.codeberg.org/improving-codeberg/ and have a look at the open issues, especially those that are looking for contribution https://codeberg.org/Codeberg/Community/issues?state=open&labels=105 - some of them don't even require much coding knowledge. We are also happy if you forward bug reports to Gitea if the original author hasn't done that yet or hasn't got a GitHub account. --> I created some Drone CI yaml configs for popular static site generators for Codeberg Pages. So far I have these: - [Hugo](https://hugo-test.codeberg.page/) | [repo](https://codeberg.org/hugo-test/pages/) - [Hexo](https://hexo-test.codeberg.page/) | [repo](https://codeberg.org/hexo-test/pages/) - [Jekyll](https://jekyll-test.codeberg.page/) | [repo](https://codeberg.org/jekyll-test/pages/) I think there should be a collection of repos somewhere to showcase that this is possible. GitLab has [something similar](https://gitlab.com/pages). It works as a template for people starting out and works as a reference. Just found [this issue](https://codeberg.org/Codeberg/Community/issues/428) from which I learned about [Woodpecker](https://github.com/woodpecker-ci/woodpecker) and other CI options. I haven't looked into them yet, but I think configs for them should also be in a repository somewhere if people want to use them. Maybe they can be under different organizations or the same, I don't know. Feel free to discuss. Feel free to use my repos above for anything (consider CC0/public domain).
Collaborator

Thanks. Just a quick note from me: "Consider [them] CC0/public domain" does not work from a legal point of view. Please just add a LICENCE file to the repos and clearly state that the repo content is licenced under it, e.g. CC0.

Thanks. Just a quick note from me: "Consider [them] CC0/public domain" does not work from a legal point of view. Please just add a LICENCE file to the repos and clearly state that the repo content is licenced under it, e.g. CC0.
n added the
docs
pages
labels 2 months ago
Poster

Sure, no problem. I've added a license to them.

Sure, no problem. I've added a license to them.
Collaborator

We first need the CI 😄

For examples i think it makes sense to link to real working repositories, so they don't become outdated. We can mention some very simple setups and more advanced. Not only for Codeberg pages, but also for our CI in general. Learning from examples is very effective.

We first need the CI 😄 For examples i think it makes sense to link to real working repositories, so they don't become outdated. We can mention some very simple setups and more advanced. Not only for Codeberg pages, but also for our CI in general. Learning from examples is very effective.
Poster

Not only for Codeberg pages, but also for our CI in general.

That's a good idea. Including other examples (not just pages) should definitely help new users.

We first need the CI 😄

Yeah. That'd be awesome. 👍 A lightweight but reasonably featured CI would be amazing to have built in. But I think we should also include other CI examples (maybe in a separate group or something) because they'll still be an option when Codeberg CI launches and they can help others learn how to use a specific CI for their use case within Codeberg. Maybe it's a specific use case that would not be possible to implement in Codeberg's own CI. More options could be helpful.

Plus, I think they're extra important now, because Codeberg does not have a CI yet and third party CIs are the only option. If anyone wants to use Codeberg and have a CI setup today and don't have time to wait, they'd have to setup something with those CIs.

> Not only for Codeberg pages, but also for our CI in general. That's a good idea. Including other examples (not just pages) should definitely help new users. > We first need the CI 😄 Yeah. That'd be awesome. 👍 A lightweight but reasonably featured CI would be amazing to have built in. But I think we should also include other CI examples (maybe in a separate group or something) because they'll still be an option when Codeberg CI launches and they can help others learn how to use a specific CI for their use case within Codeberg. Maybe it's a specific use case that would not be possible to implement in Codeberg's own CI. More options could be helpful. Plus, I think they're extra important now, because Codeberg does not have a CI yet and third party CIs are the only option. If anyone wants to use Codeberg and have a CI setup today and don't have time to wait, they'd have to setup something with those CIs.
n commented 4 weeks ago
Collaborator

Codeberg's CI will use Woodpecker, which is forked from Drone, so your repos probably work as is 👍

Keeping the source and build in the same repo isn't ideal. Till now people usually had seperate repos for each, but the new codeberg-pages would allow storing websites on a pages branch (also allowing multiple pages per org/user).

Codeberg's CI will use Woodpecker, which is forked from Drone, so your repos probably work as is 👍 Keeping the source and build in the same repo isn't ideal. Till now people usually had seperate repos for each, but the new [codeberg-pages](https://codeberg.org/momar/codeberg-pages) would allow storing websites on a `pages` branch (also allowing multiple pages per org/user).
Poster

Codeberg's CI will use Woodpecker, which is forked from Drone, so your repos probably work as is 👍

That's great to hear.

Keeping the source and build in the same repo isn't ideal. ... the new codeberg-pages would allow storing websites on a pages branch (also allowing multiple pages per org/user).

I know. I didn't find any other alternative way to deal with this. I literally had to keep a list of generated files in a text file just so that I can clean the output later. 😞 This will make life so much easier. GitLab has the site output saved as build artifact. But I think having a branch for the site output would be easier to understand and manage.

> Codeberg's CI will use Woodpecker, which is forked from Drone, so your repos probably work as is 👍 That's great to hear. > Keeping the source and build in the same repo isn't ideal. ... the new codeberg-pages would allow storing websites on a pages branch (also allowing multiple pages per org/user). I know. I didn't find any other alternative way to deal with this. I literally had to keep a list of generated files in a text file just so that I can clean the output later. 😞 This will make life so much easier. GitLab has the site output saved as build artifact. But I think having a branch for the site output would be easier to understand and manage.
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.