Server Advanced Tab Documentation - Gamocosm/Gamocosm GitHub Wiki

Gamocosm works with a lot of moving parts to automate hosting with cloud servers. Although we do our best to make Gamocosm as robust as possible, things may go wrong. Some people may want to try to fix things themselves, if they know there's only a simple error. This page documents the fields under the "Advanced" tab.

ssh_port

The default value is 4022 (see Additional info for server admins for the reasoning). The first time a server starts, Gamocosm always connects on port 22 (the default for SSH). Gamocosm will edit /etc/ssh/sshd_config to listen on this port. You can see everything Gamocosm does to set up a server in app/workers/setup_server_worker.rb. During future starts, Gamocosm will use this value to SSH.

For example, if you don't want Gamocosm to change the default SSH port, update this field to 22 before starting it.

If you want to change the port on an existing server, first read the instructions on Additional info for server admins. Do that, then update the value on Gamocosm.

remote_setup_stage

Used to show the status messages when starting a server, and to know when a server has finished setting up. As of 2014 October 25, the finished value is 5.

pending_operation

Keeps track of whether Gamocosm is busy doing something with a server (e.g. starting it, stopping it, backing it up, etc.). When this field is not empty, Gamocosm will show the "busy" page. Empty this field if you know the background workers have failed and you want to stop the refresh cycle/fix the server yourself.

digital_ocean_saved_snapshot_id

If not empty, Gamocosm creates the server from this snapshot, and deletes it if it is successful. If empty, Gamocosm creates the server from the vanilla fedora-20-x64 image.

digital_ocean_region_slug

Used when creating servers.

digital_ocean_size_slug

Used when creating servers.

mcsw_key

Used for authentication with the Minecraft Server Wrapper. Gamocosm generates a password for each new server (saved in Gamocosm's database). On each actual server, this is saved in /opt/gamocosm/mcsw-auth.txt. You can view the contents while SSH-ed with cat /opt/gamocosm/mcsw-auth.txt, or you can download the file with SCP/FTP.

api_key

Used for the Gamocosm API.

preserve_snapshot

By default, preserve_snapshot is false. When preserve_snapshot is false, stopping a Gamocosm server involves stopping the Minecraft server process, shutting down the Digital Ocean server, snapshotting the Digital Ocean server, retrieving the new snapshot ID, destroying the old snapshot, and destroying the Digital Ocean server. If any step up to and including "retrieving the new snapshot ID" fails, the process should abort (i.e. at least one of the active server or up-to-date snapshot should exist at any time). In addition, deleting a server will also delete the saved snapshot.

When preserve_snapshot is true, stopping a Gamocosm server will immediately destroy the active Digital Ocean server. The next time a server is created, it will be restored from the last saved snapshot ID. If there is no saved snapshot ID (i.e. a new Gamocosm server that has never been stopped before), it will be created brand new. This behaviour may be unintuitive, but can be useful for running ephemeral "mini-game" servers where you want to start over from a saved snapshot. In addition, deleting a server will not delete the saved snapshot.