Closed jwred5 closed 11 months ago
Basic list of things to do:
Article about triggering a deployment script: https://lightrains.com/blogs/deploy-aws-ec2-using-github-actions/
As of 7f271e0c48d35fe093e9f78bd211ffcf9a521290 the build workflow will always run, though only push an artifact on tag. Also, the server now have the minecraft server running with a startup script in etc/init.d
As of 6ebf9c426fd4051934979077647dca0653229571 the repo will publish upon tag. Still need to finish deployment script, and figure out versioning. Not sure what we want to do about notifying of mod updates
As of ed61dbcc1e62aecb7f08e8d5d7afcef5c485f38f the repo will automatically deploy to the server upon new release tag. Last pieces are to figure out how to make people aware of new mod version, and document versioning scheme
We need to have the mod automatically deployed to the server every time we merge a new feature into main Let's use AWS CodeDeploy and Github Actions to do this automatically every time