To some extent, the task here is to
decide how it's all layered. (-:
One reasonable way to layer things is:
* Create a Sandstorm Docker image, if the Synology box supports Docker, and
* Make sure that Sandstorm Docker image knows how to auto-update Sandstorm, and
* Figure out the best way to make it easy to install that. (Perhaps this is merely a matter of writing a draft of documentation?)
* Figure out the best way to prompt the user for a
sandcats.io subdomain, per the current Sandstorm install script. Maybe there's a way for Docker images on the Synology box to take an environment variable, and then pass it through to "install.sh", and maybe we have to say if your subdomain is already taken by someone else, the install fails, and you get told to pick a new one. Or maybe we make the install succeed, but we append a random string to it. We'd have to show the new hostname to the user, if so. Somehow. Maybe that means you'd want a different way to install than Docker. Or maybe all the above can be done tidily by their web interface for Docker, if they have one.
* Figure out what the best way is for this Sandstorm install to have port 6080 exposed to the world. Maybe that means UPnP? You can just say how we should do this; you don't have to actually do it necessarily.
I think in general, the thing we need someone to do is to take one of these machines, read the documentation, and make a recommendation on what should be done. Figuring out who would do it is secondary; actually doing it is tertiary. Yes, getting things done is important, but I think we're at the "Figure out what needs to be done" phase, which is also an important phase.
I think it'd be a fun project, but I clearly haven't done it yet, so someone else can have that fun, I figure. How about you, Scott? (-:
In doing this, you'll learn more about Sandstorm itself, which would hopefully be interesting!
Naturally, I'm happy to be a person you can bounce ideas off.