Setup infrastructure and cloud service (AWS)

[alisomay]

I suppose we're using AWS for remote.

This may become an umbrella issue but we can discuss the steps and details under this one.

No rush, but maybe you may take this part @ozankasikci.

[dvtkrlbs]

I think fly.io and Cloudflare in front might work well as well.

[alisomay]

Sure why not. I haven't worked with fly.io before is the workflow similar to AWS or GCP container deployment and infra setup? Working with AWS is a win because they have a Rust SDK. Does fly.io have one? If not and the service is very attractive we can write an API wrapper though, SDK is not a must but it would definitely make things easier.

On the other hand I'm not very strong with devops. Maybe @ozankasikci might would like to share his opinion also.

[dvtkrlbs]

They are mostly for just shipping applications similar to Heroku (in good ways). The main way is to use their command line tool called flyctl. They also have an API but it is relatively simple since it mostly reduced complexity https://fly.io/docs/machines/working-with-machines/. They have also have a guide for using with Github Actions https://fly.io/docs/app-guides/continuous-deployment-with-github-actions/. If we want we can definitely go with AWS but I think it will cause additional complexity for us.

[ozankasikci]

Nice, discussion. fly.io was on my radar for a while but haven't tried it yet. I think it boils down to pricing and the ease of use, fly.io seems to be cheap and easy to use, and encourages a portable application by default.

My 2 cents: I think we can give it a try before falling back to AWS or some other cloud provider.

[alisomay]

I'll also take a look 👀

[dvtkrlbs]

I am going back on my word about fly.io. It seems they have a good product but they don't seem to be that reliable and they don't seem to handle their issues well. https://news.ycombinator.com/item?id=36808296