Cross-compile arm releases & include insert-user in release

[ahdinosaur]

hi, i'm keen for go-ssb-room on a Raspberry Pi. 🥧

so i improved the release dev tools, using Vagrant (a friendly wrapper around VirtualBox).

open to feedback! 💜

related:

• github.com/mattn/go-sqlite3 requires CGo #79

also now i see #266 and #241, happy to incorporate other changes as need be, could also cross-compile armel and armhf if need be.

[ahdinosaur]

this is ready for review! 🍰

here's some compiled releases: https://github.com/ahdinosaur/go-ssb-room/releases/tag/v2.1.0-pre.1

/cc @mhfowler

[ahdinosaur]

i stole these systemd script things from peachcloud/peach-package-builder who stole them from mmstick/cargo-deb 📦

[ahdinosaur]

however, they do change things such that the service starts automatically when installed (and is enabled to start on boot), as this is the usual behavior on Debian. if we follow this behavior, we should update the postinstall message to tell you to restart the service rather than reload daemon after making changes.

would there be a problem with the service first running with the wrong config, then changing it and restarting the service?

as a side note, we shouldn't be recommending updating services by writing to the systemd file directly, there's a whole built-in edit workflow with conf overrides and such that we should be doing: https://askubuntu.com/questions/659267/how-do-i-override-or-configure-systemd-services.

[decentral1se]

would there be a problem with the service first running with the wrong config, then changing it and restarting the service?

According to:

go-ssb-room/docs/files/debian-postinstall.sh

Line 26 in 641069a

Before you start using room server via the systemd service, you need to at least change the https domain in the systemd service.

The startup will fail? Maybe we can avoid automatically starting up & recommend the commands? Unsure what Debian does when installed packages need to be configured first? Or perhaps there is a standard way to ask for input here and then sed'in the relevant files / updating templated files? Just throwing out some options...

as a side note, we shouldn't be recommending updating services by writing to the systemd file directly, there's a whole built-in edit workflow with conf overrides and such that we should be doing: https://askubuntu.com/questions/659267/how-do-i-override-or-configure-systemd-services.

One for the docs I guess, can do here or let's open an issue to catch that another time?

[decentral1se]

Nice work! I'm curious if it is possible to avoid the vagrant/vm requirement and instead use Docker? As far as I understand, you're using a Debian image & running a series of build commands which could be done with Docker?

[ahdinosaur]

I'm curious if it is possible to avoid the vagrant/vm requirement and instead use Docker? As far as I understand, you're using a Debian image & running a series of build commands which could be done with Docker?

🤷

i usually use Docker, but here i used Vagrant and had a lovely time. 😺

[decentral1se]

@ahdinosaur

Thanks for this PR. I'd love to get it out in the near future and am doing a review now.

I think the current change set needs a rebase, sorry for letting it sit for so long.

i usually use Docker, but here i used Vagrant

Would you be up for using Docker instead? I think I'd love to avoid having to work with Vagrant going forward because it assumes a workstation that has virtualisation wired up and sometimes that is a bit tricky / can be a barrier to working on this. We could wire up a Debian-based Dockerfile and acommpanying commands instead? I could do that or if you feel like it, please go for it.

[ahdinosaur]

@decentral1se great, i'm happy for you to continue from where i left off, i'll be here on the sidelines if you need me. 😺

[decentral1se]

Cut a trimmed version of this in #355. Opened #354 also.