infra/scripts contains strings explicitly for Xania.org

[seamer1977]

install-xania.sh: curl -sL "$(aws s3 presign s3://mud.xania.org/releases/xania-$VERSION.tar.xz)" | tar Jxf -

crontab.root: [email protected]

setup.sh: hostname mud.xania.org

You could probably roll these (and the others) into one master config file for easier management.

[mattgodbolt]

The infra directory is specific to a specific deployment of Xania. I guess the fact it's here is confusing and we should probably move it out to a separate repo; or at least extract specifics to an overridable for other folks' installing.

What's your use case for looking at the infra stuff here @seamer1977?

[seamer1977]

If I pull your code into a server I would like to see what's inside my firewall...

I was looking for an install script

[mattgodbolt]

@seamer1977 the README.md has some info under "Going live". Basically, make install should put everything into a directory you can run from. If you want to build the release build make install BUILD_TYPE=Release.

The result of this is a directory install:

$ ls -l install/
total 12
drwxr-xr-x  2 matthew matthew 4096 Aug 18 15:31 area/
drwxrwxr-x  2 matthew matthew 4096 Aug 18 15:31 bin/
lrwxrwxrwx  1 matthew matthew   28 Aug 18 15:31 gods -> /home/matthew/dev/xania/gods/
drwxr-xr-x 12 matthew matthew 4096 Aug 18 15:31 html/
lrwxrwxrwx  1 matthew matthew   27 Aug 18 15:31 log -> /home/matthew/dev/xania/log/
lrwxrwxrwx  1 matthew matthew   30 Aug 18 15:31 player -> /home/matthew/dev/xania/player/

You can see that this contains all the things needed to run Xania, with symlinks from the things that should be persisted (e.g. player files and logs) between installs.

Xania and doorman need to be run from the area directory in here (at least until #53 is fixed).

I'm not sure what you mean by "see what's inside my firewall" - do you want to know what port xania runs on? It's port 9000.

Is there anything else we can help with here?