To do so simply requires thus. First, create a directory tree accordingly (wherever you want--under your user, under a separate user, whatever):
starbound/
starbound/server
Then copy/upload the contents of your Steam/SteamApps/common/Starbound/linux64 directory to starbound/server. If you copied it to the correct location, this should place a starbound_server file under starbound/server on your remote host.
Next, copy/upload the contents of Steam/SteamApps/common/Starbound/assets to starbound/ (this will create a starbound/assets directory).
I should note that you can configure this by modifying the file bootstrap.config in the Starbound server directory and changing the assetSources path. I have no idea if this file will be overwritten in the future, so I've instead elected to keep it at sane defaults. Modify at your own risk.
Finally, set starbound_server as executable (chmod a+x starbound/server/starbound_server) and change to the server directory, then launch the server binary!
- Code: Select all
$ cd starbound/server
$ LD_LIBRARY_PATH=. ./starbound_server
What you're doing is setting the environment variable LD_LIBRARY_PATH to the current directory (hence the dot) so that the linker looks for the supporting libraries here and then on the system path. The reason for this is because the Starbound server is dynamically linked; if it were statically linked, all the appropriate libraries would be compiled into the binary. Sadly, this isn't the case. So, it does imply that there may be breakage in the future.
Hope this helps!