cool, consider codeberg or notabug

[ghost]

Github makes sense as a default choice. A small minority (<1%) might prefer having a github alternative option, if that fits in the longer term roadmap.

[lefessan]

Drom has a notion of skeleton that is a set of templates that are used to create/update a project. There is inheritance between them, so it should be possible in the future to create a skeleton for every Github alternative, all of them inheriting from the same ancestor (called virtual). Of course, we welcome such contributions, as it is often better done by experienced users of these alternatives.

[ghost]

Okay, I will try to understand the concepts a bit more and see what parts of gitea api that I should use. I am not sure if I will get to the point of PR, but will try to note specifications as I research.

[zapashcanon]

I'd rather not support directly a particular instance of gitea, gitlab or sr.ht but rather something where you specify the one you use (e.g. gitea) and the url of your instance (e.g. codeberg.org).

[ghost]

for codeberg (gitea), the static sites are associated with a user account/org, rather than in individual repo:

https://<your_username>.codeberg.page/

I'll try to look around the status of implementing pages inside of gitea proper later

[ghost]

For CI, there doesn't seem to be a community recommendation yet from gitea. Links to various self hosted CI. I will look to see if there is any high quality CI service that is built on free software. https://gitea.com/gitea/awesome-gitea#devops

[zapashcanon]

I have my own gitea instance that I use for personal projects. So I'm quite familiar with it. For the CI I use giteart + builds.sr.ht.

[ghost]

So, the template will need a build.sr.ht manifest file, installing ubuntu and ocaml? Do you have an example that I can read?

[zapashcanon]

Something like: https://git.zapashcanon.fr/zapashcanon/dddddml/src/branch/master/.build.yml