wasp-lang / wasp

The fastest way to develop full-stack web apps with React & Node.js.
https://wasp-lang.dev
MIT License
13.77k stars 1.18k forks source link

Add "Production advice" to the docs #2201

Open Martinsos opened 3 months ago

Martinsos commented 3 months ago

It would be great if we would have, in one place, a list of recommendations and advice on how to best deploy Waps app to production. We talk about it in docs for each feature, but having an overview in a single place would also be great, with best practices. One thing is techinical stuff on how to deploy Wasp app to produciton, but this could also be a good place to give some general recommendations that will be helpful for people with less experience in deploying such full stack web apps, for example how to organize branches on Github (release vs main), then about evironments (staging vs production), secrets management, database production workflow, ... . A checklist for release would also be nice, that they can take and then extend, and it would have stuff like "QA", "merge main into release", ... .

Here is one such question / convo we had on Discord: https://discord.com/channels/686873244791210014/1264357770363273297/1264357770363273297 .

Martinsos commented 2 months ago

We also had user asking about how Wasp scales up if needed, can it be used for enterprise apps, ... . Is it made for that. So maybe that could also be part of this page! We might want to have a Production and Scaling page in the Docs, or something like that.

https://discord.com/channels/686873244791210014/1277607531363172496/1277645496743231550

I think adding additional details for the “Production / Scaling” part of the docs would indeed be the best choice since you can pretty much explain what I was told here, that basically people have nothing to fear because at the end of the day they can use the same tools they could use directly from the JS ecosystem for scaling or tackling similar concerns (even if you don’t have internal solutions for that at this point).

In general, in these docs I would want to be reassured through that production section that Im “buying” into a framework(lang?) that takes care (or at least does not stop me from doing it) of security, scalability, maintainability since Im already sold on ease of use, speed and efficiency. Actually that would solve a major issue of choosing to develop (backend) in the JS ecosystem in general not just wasp

Martinsos commented 1 month ago

Here is another Discord convo where user is looking for advice on how to best deploy Wasp to production, some advice: https://discord.com/channels/686873244791210014/1295481966191185952/1295481966191185952 .

Martinsos commented 3 weeks ago

User asking how to deploy both to production and to staging (with Fly): https://discord.com/channels/686873244791210014/1296561251383513131/1296561251383513131 .

@infomiho recommended:

I'd advise going full manual mode smth like having folders for your Fly TOML files and having a Bash script that copies things around and redeploys things using the Fly CLI