Serve from pages branch when available #39

adnan360 commented 2021年12月15日 13:36:13 +01:00

I'm interested in using static site generators like Hexo, Hugo etc. with Codeberg CI + Pages v2.

Right now if I create:

organization > pages repo > pages branch > index.html

It shows index.html from main branch (see #36 for reference), meaning:

organization > pages repo > main branch > index.html

I usually commit to main branch. So I'll have to keep source for the website with its output.

This has disadvantages like:

• pollutes source with build outputs, which many don't like as discussed before
• difficult to clean previous output; e.g. if I had a page, generated output, committed the output, then decided to delete the page, it will be difficult to deal with it esp. if I have lots of content and if the output is on repo root.

Workarounds I can think of:

• Add a @pages at the end of URL: like https://hexo-test.codeberg.page/@pages/; while this may work, the URL is difficult to type and not good to look at
• Set pages branch as default, commit to main: Suggested by @momar here. This may work, but working like this seems a bit odd. I've used GitLab Pages and I don't have go through all these to get it working.

Since workarounds are not actually perfect, I think pages-server should serve from pages branch if such a branch exists. It will help keep the source clean.

If you agree with this, give an upvote ( 👍 ) to this post.

I'm [interested](https://codeberg.org/Codeberg/Community/issues/498) in using static site generators like Hexo, Hugo etc. with Codeberg CI + Pages v2. Right now if I create: > organization > pages repo > pages branch > index.html It shows index.html from main branch (see #36 for reference), meaning: > organization > pages repo > main branch > index.html I usually commit to main branch. So I'll have to keep source for the website with its output. This has disadvantages like: - pollutes source with build outputs, which many don't like [as discussed before](https://codeberg.org/Codeberg/Community/issues/498#issuecomment-250296) - difficult to clean previous output; e.g. if I had a page, generated output, committed the output, then decided to delete the page, it will be difficult to deal with it esp. if I have lots of content and if the output is on repo root. Workarounds I can think of: - Add a `@pages` at the end of URL: like `https://hexo-test.codeberg.page/@pages/`; while this may work, the URL is difficult to type and not good to look at - Set pages branch as default, commit to main: Suggested by @momar [here](https://codeberg.org/Codeberg/pages-server/issues/36#issuecomment-289916). This may work, but working like this seems a bit odd. I've used GitLab Pages and I don't have go through all these to get it working. Since workarounds are not actually perfect, I think pages-server should serve from pages branch if such a branch exists. It will help keep the source clean. If you agree with this, give an upvote ( 👍 ) [to this post](https://codeberg.org/Codeberg/pages-server/issues/36#issuecomment-289916).