The infrastructure layer for my apps, websites.
- coilysiren/infrastructure is the home of the DNS route that points to coilysiren/website
- coilysiren/infrastructure uses docker images that are built inside of coilysiren/images
- Setup AWS CLI access
- Create a new SSH key via the AWS UI. Name it simply
ssh. Delete any old keys that might already be parked on that name.sudo cp ~/Downloads/ssh.pem ~/.ssh/aws.pemchmod 400 ~/.ssh/aws.pemssh-add ~/.ssh/aws.pem
invoke deploy-shared- This deploys simple shared infra. Run it just to make sure everything is on the same page.invoke build- This will cut a new build of the AMI, and push it to AWS. This doesn't need to happen often. The primary reasons you would run this are 1. to add new game servers or 2. to install security updates. The bulk of the config for this build is in three places. You don't need to edit them unless you are starting a new game server. Those places are:ubuntu.pkr.hclscripts/ubuntu-setup.shassets/<== which has game server specific files
invoke deploy-server- Deploys an EC2 game server. Runinvoke deploy-server --name WHATEVERto deploy a different type of server, although honestly you are better off with editingtasks.py. Just make sure you only edit thename="WHATEVER"parts.invoke ssh- Hope into the server. Look around a bit. Everything beyond this point is iterative. Good luck have fun!
See: eco.md
- https://store.steampowered.com/app/105600/Terraria/
- https://terraria.fandom.com/wiki/Guide:Setting_up_a_Terraria_server#Linux_/_macOS
⚠️ the site above has many ads⚠️
You must run
sudo mkfs.ext4 /dev/nvme1n1exactly once, when configuring a new game type, to format its EBS volume
this command is dangerous because if can wipe your drive if there's already data in it!
via https://unix.stackexchange.com/questions/315063/mount-wrong-fs-type-bad-option-bad-superblock