social.lumbung.space

fork hell

• https://github.com/mastodon/mastodon/pull/16221
• https://github.com/hometown-fork/hometown/issues/1153

release management

We're using Hometown with this PR merged in. Yes, that's a fork of a fork. The process of making a new release is basically merging that PR into the latest Hometown, building, tagging & pushing a container and then updating the hometown recipe configs.

How to do it, you ask? Abandon all hope. Computers were a mistake.

1. Clone hometown, git fetch -a, git remote add sso https://github.com/chandrn7/smalltown.git, git fetch -a sso
2. Check out the hometown tag you want, start cherrypicking the commits the PR. This view is handiest. You can copy/pasta each commit hash with that button and see what conflicts you need to resolve. Yep, you'll be blindly resolving conflicts between two forks.
3. If you're lucky enough to get this far, you now need to build a new container. docker build -t <name> . and see what happens . You might need to this absolutely random step in order to get bundler/gem/ruby to install the damn thing. Also try wiping out RUBY VERSION / BUNDLED WITH in the Gemfile.lock when running the build. You generally just end up reading the errors and then chaotically hacking the Gemfile / Gemfile.lock file until it works. If you get to the yarn building step, you might actually make it.
4. Push the container & update the Co-op Cloud recipe (compose.oidc.yml)
5. Deploy the thing & pray
6. Hope you never have to do this again