BaseURL + Interface Setting for semi-unattended installs

Is your feature request related to a problem? Please describe. Unable to define a baseurl and serve on a specific interface from the ubuntu build. This would allow for people to run an easy-to-run script that’s built into their seedbox software without needing to modify too many things. Essentially I’m advocating for something as easy as sudo box install petio.

Describe the solution you’d like Both of these features should be added so those using something like quickbox or swizzin can have an easy install that is carried out.

Describe alternatives you’ve considered Setting up a firewall on the port is a good temporary solution, although for us to deploy this via a script that configures reverse proxy, etc. it makes more sense for us to be able to set the interface and baseurl as flags on startup. Something like --interface="127.0.0.1" --baseurl="/petio" would be perfect.

I was in the discord this afternoon and was told that baseurl can be set, however it was not a great solution, as it still required me to create firewall rules to block port 7777 and more configuration to nginx. It also required me to complete the setup before I could set the baseurl.

Additional context This is in the context of this temporary build script for swizzin installs that I’ve created.

In this context, we’d ideally be able to setup the basics for the user, and the installer would be still served at https://example.com/petio, just ommiting the parts about baseurl / interface to serve on.

Thanks /b

[AshDyson]

It didn’t really seem clear this was an option — essentially, will it skip over that step in the setup if it’s set in the config @AshDyson? Or does the config need to be complete?

It’s not a suggested method but it can be used if you’re running a specific unattended setup like this. Yes you’ll need a complete config with all prefs set correctly. But you could just write this into whatever CLI config you’re using and it will just completely bypass the setup wizard

[AshDyson]

Hm, I just think personally if you’re automating the setup process you should automate the whole process through CLI. Altering our setup process to accommodate this isn’t something I’m looking to do. I appreciate the issue but if its a maintained service there is an alternative option as suggested above to manually configure the config.json in your own wizard.