You can pick the provider but I would prefer you pick between AWS, Azure, or Google Cloud.
[ ] Figure out the resources we would need to provision/configure. Off the top of my head this could be:
a place to host the static frontend. In aws i think this can be S3.
a 'serverless' service as backend / servicing the requests from frontend. in aws i think this can be lambda
a database. in aws this can be dynamodb since its cheaper than documentdb.
something for mapping the dns entries to actual instances. (Route 53 in aws)
[ ] make note of any changes that would need to be made in the code to make this easier/ more flexible. We can discuss this after you get more understanding of the plan / approach we should take.
[ ] make the definitions
[ ] write documentation on commands to use and config to change to deploy your own version of gamestock to the cloud.
You can pick the provider but I would prefer you pick between AWS, Azure, or Google Cloud.