WIP: Docker deploy #29

Draft
kawaiipunk wants to merge 4 commits from kawaiipunk/new-website-jekyll-theme:docker-deploy into coopcloud.testing.sutty.nl
Owner

Hi folks, I wanted to get an easy local docker/podman dev environment going for this. Is this ok?

I had some issues with the existing code and ruby dependecies. The root Gemfile used gems.sutty.nl and I couldn't locate the versions there in rubygems.org.

It also had gems that target x86_64-linux-musl, with specific versions that also aren't available rubygems.org.

Bit out of my depth here but I had to make the gem stuff in docker/dev/ to get it working with different versions. Pls advise as I might have broken something.

Hi folks, I wanted to get an easy local docker/podman dev environment going for this. Is this ok? I had some issues with the existing code and ruby dependecies. The root Gemfile used gems.sutty.nl and I couldn't locate the versions there in rubygems.org. It also had gems that target x86_64-linux-musl, with specific versions that also aren't available rubygems.org. Bit out of my depth here but I had to make the gem stuff in `docker/dev/` to get it working with different versions. Pls advise as I might have broken something.
kawaiipunk added 2 commits 2026-10-29 16:07:17 +00:00
kawaiipunk added 1 commit 2026-10-29 16:20:58 +00:00
kawaiipunk added 1 commit 2026-10-29 16:24:07 +00:00
Owner

My 2c: I think it would be better to focus on improving haini.sh (and collaborating closely with @fauno to do that) since it also does use docker and is a good system from what I have seen so far. This changes introduces a lot of new moving parts (including podman support?) while basically re-creating what haini.sh tries to achieve (simple setup with isolation). I think we're just missing some good docs for how to get started with haini.sh. PS. If this is AI generated also, that should really be disclosed.

My 2c: I think it would be better to focus on improving `haini.sh` (and collaborating closely with @fauno to do that) since it also does use docker and is a good system from what I have seen so far. This changes introduces a lot of new moving parts (including podman support?) while basically re-creating what `haini.sh` tries to achieve (simple setup with isolation). I think we're just missing some good docs for how to get started with `haini.sh`. PS. If this is AI generated also, that should really be disclosed.
Owner

thanks! the idea with haini.sh is that we have a dev env that's the same in each developer's computer, since we've had a lot of trouble with people working on different distributions. we didn't go with docker or podman because everyone would have to set it up on their computers, but it was an idea to port haini.sh to a container that we can also use on CIs.

this is also why gems.sutty.nl exist, to pre-compile binary gems (we're also removing test files and signing them) and avoid issues with linked libraries being called differently on each distro.

can you explain why you say gems.sutty.nl is a private repository? it's open and should work for alpine containers. some versions are missing from rubygems.org, for instance safe_yaml, because they've been abandoned for a long time and we publish our own patches to this repository.

i think the readme is ok, but it should mention that most tasks can be run from the Taskfile using go-task. for instance the fork awesome generation is run entirely from the taskfile and not through the helper scripts directly.

thanks! the idea with haini.sh is that we have a dev env that's the same in each developer's computer, since we've had a lot of trouble with people working on different distributions. we didn't go with docker or podman because everyone would have to set it up on their computers, but it was an idea to port haini.sh to a container that we can also use on CIs. this is also why gems.sutty.nl exist, to pre-compile binary gems (we're also removing test files and signing them) and avoid issues with linked libraries being called differently on each distro. can you explain why you say gems.sutty.nl is a private repository? it's open and should work for alpine containers. some versions are missing from rubygems.org, for instance safe_yaml, because they've been abandoned for a long time and we publish our own patches to this repository. i think the readme is ok, but it should mention that most tasks can be run from the Taskfile using go-task. for instance the fork awesome generation is run entirely from the taskfile and not through the helper scripts directly.
Checking for merge conflicts…
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u https://git.coopcloud.tech/kawaiipunk/new-website-jekyll-theme docker-deploy:kawaiipunk-docker-deploy
git checkout kawaiipunk-docker-deploy
Sign in to join this conversation.