Testing instructions (let me know if there's a better way):

• Run nix-build -A dawarich.tests.dawarich.driverInteractive
• Start the tests with ./result/bin/nixos-test-driver
• In the Python console, run start_all() to init the VM
• Then forward the port with machine.forward_port(guest_port=3000, host_port=3000)
• Finally, open port by running machine.shell_interactive() and then nixos-firewall-tool open tcp 3000

You can then access Dawarich at http://localhost:3000

Add utility to enter rails console (it's used multiple times in upstream's documentation, so it might be useful)

I feel like this could be added as followup issue so it doesn't stop this to be merged as maybe someone can deploy without needing this.

@Pablo1107 I have a bit more time now and will resume work on this PR next week :)

This should now be ready. I'm just waiting on #454194 before removing the draft status.
I'll be deploying in my production instance to ensure everything still works, but local testing looked fine.

Reviews are welcome!

Update: deployed on my infrastructure, seems to work fine with my existing data at first glance!

Updated the list of queues available on sidekiq

@RossComputerGuy is everything good from your side? You are currently blocking the merge and I don't want to dismiss your review without pinging you first

Backport failed for release-25.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-25.11
git worktree add -d .worktree/backport-423867-to-release-25.11 origin/release-25.11
cd .worktree/backport-423867-to-release-25.11
git switch --create backport-423867-to-release-25.11
git cherry-pick -x 3fd55724a0fcd5c93d5b703392c9315e34c09c49 d6f3fdc6d921a15ab93042ce784829963822a5f7 b0cb5d3e8f52c0ecfd6205d033309ca70c39bb68 23d92890e0d321445d0a2b8c0f91878ed1cc13ab f14353c14118659611bddf4d65b30b56b3d0be52

Update: deployed on my infrastructure, seems to work fine with my existing data at first glance!

@diogotcorreia Any tips on how to go about migrating from a docker compose setup to this new awesomeness? If this is documented somewhere and I missed it, I apologize for the redundant question.

@genebean I believe I only had to dump and restore the PostgreSQL data, but it was a while ago.
If you figure it out, I recommend writing it down on https://wiki.nixos.org

Update: deployed on my infrastructure, seems to work fine with my existing data at first glance!

@diogotcorreia Any tips on how to go about migrating from a docker compose setup to this new awesomeness? If this is documented somewhere and I missed it, I apologize for the redundant question.

@genebean I will be moving from my docker setup to the nixos module. I'm not very experienced in it, but I will come back once I figure it out if no one else has responded by then.

Turns out migration is a breeze now!

1. Make sure the docker version is updated (ideally to the same as the nix one)
2. Go to your account page and click export user data
3. In the nix version, update the default account to match the old instance’s
4. In nix, set nginx’s client_max_body_size to something larger than your export so that uploads do fail (I picked 200m as that covers future large GeoJSON files and such)
5. Go to the account page and click import user data.
6. Shortly you will see all the things back! The only difference is you will need to update clients that use the api with a new key.

I’m going to try to write up a wiki page today too