rn we're using Docker, which is great but doesn't work on i686 (no T60) and currently has some stupid cgroups bug on RPi (Kali and Raspbian) which is a major blocker until they push out the patch in a release. Docker has the whole EE/CE thing where CE is only supported on some distros. For example, ppl on RHEL can't easily run CE (FOSS) Docker, only the paid EE version. While Docker is useful in our RedAlliance server environment, it tends to be a general hindrance elsewhere, ex. the issue of getting the commit hash into the builder code.
Other options for non-container route, multi-distro are snap, flatpak, and AppImage. AppImage is flexible but you're responsible for packing it all. Snap is a little more contained and uses AppArmor for security. Flatpak is not suitable for servers apparently.
Snaps have really nice, flexible multi-channel versioning unlike pip, so we'll use for aidanh010/StrangeNet as well.
Decided next steps:
Package StrangeScout server as a snap. Now that we have the domain name not hardcoded, we can set at runtime for anything that may need it. We'll convert the build script into a more traditional npm format so that we can easily deploy as a snap. I guess this means we could put it on NPM as well, although that route would involve a full compile of everything so not sure if it's useful.
We'll be able to use this to finally do #6 (CI/CD), we can possible autobuild snaps eventually.
Relegate Docker to a layer either around the snap or around the npm module, dockerfiles should not have much build logic of their own. We can continue to use this with Traefik on RedAlliance scouting server.
Quick review of discussion on the matter:
Decided next steps: