I'm working on packaging Factorio for NixOS.
Because I love pain, I decided to teach it how to download Factorio, rather than depending on the user to supply a tarball, and that... *sort of* worked, but not quite; I'm having TLS problems. The procedure goes somewhat like this:
The login works, as does the redirect, but the certificate you're using for eu2.factorio.com is failing to validate against the standard Linux keyring. It does work with Chrome, and okay, I could probably bundle the exact CA cert needed, but I thought you might want to know. What I'm actually going to use is the -k option, to disable verification; this is perfectly safe, as the Nix package repository will include the sha256 hash of the tarball anyway.> curl -c cookies -d 'username-or-email=Baughn&password=<REDACTED>' https://factorio.com/login
> curl -b cookies -L https://www.factorio.com/get-download/0 ... ha/linux64
Some questions, though.
> Are you fine with this, or is there a different download procedure you'd like me to use?
> Will the above curl commands remain usable in the long term?
> Is there a flag I can pass factorio to let it know that automatic updates will not be working? Although I'm going to make sure that scenario downloads do.
And because I really do love pain,
> Do you have plans for a mod repository? Because it'd be awesome if I could configure the mod setup with Nix expressions as well, although that's probably something I should worry about once I've actually gotten the binary running.