Specify sub-folder location for Codeberg Pages index.html #410

circlebuilder commented 2021年03月05日 09:23:59 +01:00

My pages repository contains html generated via Jekyll,

The process of publishing requires another repo. In a separate Jekyll source repository I first do a jekyll build. This places site output in the _site folder, and the contents of this directory I then commit to pages repo.

Is there a means by which I could use just a single repo and specify the subdir where Codeberg Pages should pick up the index.html to render from?

My `pages` repository contains html generated via Jekyll, The process of publishing requires another repo. In a separate Jekyll source repository I first do a `jekyll build`. This places site output in the `_site` folder, and the contents of this directory I then commit to `pages` repo. Is there a means by which I could use just a single repo and specify the subdir where Codeberg Pages should pick up the `index.html` to render from?

hw commented 2021年03月05日 18:16:10 +01:00

Does jekyll's jekyll build --destination <DIRECTORY> option work for you? I think this can also be specified in the jekyll project config file.

Does jekyll's `jekyll build --destination <DIRECTORY>` option work for you? I think this can also be specified in the jekyll project config file.

fnetX commented 2021年03月05日 21:02:16 +01:00

The process of publishing requires another repo

Please note that you do not need to split the generator and the output into separate repositories, you can also use different branches in the same repo if this is more convenient to you. The pages will be served from the default branch, so you could create a "source" (or "whatever") branch and point to that in the Readme. I do not know if there's a more elegant way for generation than having two clones of the repo locally with different branches.

I think, in the medium term we could also introduce some pages config file placed in the repo to specify behaviour like this.

> The process of publishing requires another repo Please note that you do not need to split the generator and the output into separate repositories, you can also use different branches in the same repo if this is more convenient to you. The pages will be served from the default branch, so you could create a "source" (or "whatever") branch and point to that in the Readme. I do not know if there's a more elegant way for generation than having two clones of the repo locally with different branches. I think, in the medium term we could also introduce some pages config file placed in the repo to specify behaviour like this.

circlebuilder commented 2021年03月06日 06:50:13 +01:00

Thank you @hw and @fnetX .. both these solutions are not ideal.

The jekyll build --destination might work locally to avoid a manual copy/paste, but I think a jekyll clean will erase the .git subdir then (have to test). In a single-repo setup I don't want the output in the root of the repo (plus this already contains an index.html which would clash).

The two branches solution is an option, but I find it unintuitive that the design files are not in the default branch, and by default not visible to others.

I'll stick with current procedure and wait for a config-file option, which would be great to have. And it may also be used for other config e.g. if/when you decide to add custom domain name support (#115).

Thank you @hw and @fnetX .. both these solutions are not ideal. The `jekyll build --destination` might work locally to avoid a manual copy/paste, but I think a `jekyll clean` will erase the `.git` subdir then (have to test). In a single-repo setup I don't want the output in the root of the repo (plus this already contains an `index.html` which would clash). The two branches solution is an option, but I find it unintuitive that the design files are not in the default branch, and by default not visible to others. I'll stick with current procedure and wait for a config-file option, which would be great to have. And it may also be used for other config e.g. if/when you decide to add custom domain name support (#115).

momar commented 2021年05月14日 11:06:46 +02:00

The next version of pages will always try to use a "pages" branch first, so that should solve the default branch problem.

For the sake of feature creep, the rest of this won't happen from my side - you can use branches & worktrees for that like this though:

tempdir=$(mktemp -d)
git worktree add "$tempdir" pages
jekyll clean --destination "$tempdir"
jekyll build --destination "$tempdir"
( cd "$tempdir" && git add -A && git commit -m "Build at $(date -Is)"; )
git push origin pages
rm -r "$tempdir"

The next version of pages will always try to use a "pages" branch first, so that should solve the default branch problem. For the sake of feature creep, the rest of this won't happen from my side - you can use branches & worktrees for that like this though: ```bash tempdir=$(mktemp -d) git worktree add "$tempdir" pages jekyll clean --destination "$tempdir" jekyll build --destination "$tempdir" ( cd "$tempdir" && git add -A && git commit -m "Build at $(date -Is)"; ) git push origin pages rm -r "$tempdir" ```

circlebuilder commented 2021年05月14日 11:14:21 +02:00

Thanks for pasting that script, and for the great work you do on Pages 💚 This will work fine for me.

Thanks for pasting that script, and for the great work you do on Pages 💚 This will work fine for me.

Tealk commented 2022年02月07日 15:07:51 +01:00

tempdir=$(mktemp -d)
git worktree add "$tempdir" pages
hugo --destination "$tempdir"
( cd "$tempdir" && git add -A && git commit -m "Build at $(date -Is)"; )
git push origin pages
rm -r "$tempdir"

Hello,

i tried this with hugo but somehow it mixes the source files and the created files:
https://codeberg.org/ButterflyAspect/page-source/src/branch/pages

```bash tempdir=$(mktemp -d) git worktree add "$tempdir" pages hugo --destination "$tempdir" ( cd "$tempdir" && git add -A && git commit -m "Build at $(date -Is)"; ) git push origin pages rm -r "$tempdir" ``` Hello, i tried this with hugo but somehow it mixes the source files and the created files: https://codeberg.org/ButterflyAspect/page-source/src/branch/pages

circlebuilder commented 2022年02月07日 15:12:13 +01:00

Can confirm. Happened to me too. We use a different script now, but - though it works - it still has issues to solve (this is with Jekyll).

Can confirm. Happened to me too. We use [a different script](https://codeberg.org/SocialCoding/website/src/branch/main/build.sh) now, but - though it works - it still [has issues to solve](https://codeberg.org/SocialCoding/website/issues/2#issuecomment-292722) (this is with Jekyll).