how do you guys manage dev and prod deployments?
So i have built my saas product front end with opensaas. Got me 60% through at god speed👌. Now i need to deploy it. As i got cool GCP credits under their startup program I would like to deploy it on GCP. Need Dev and prod env. Is there any documentation around it. i saw fly.io and netlify. I am primarily a backend developer 😬.
Thanks to vince for opensaas.
7 Replies
we don't have any documentation around GCP and dev and prod environments, but if you try things out and post your questions here along with details and background info, I'm sure one of us can help you out.
With that said, when you're referring to dev vs prod environments, perhaps you mean adding the environment variables in your
.env.server file to GCP?@azuriete yeah we do have "general" instructions, which basically say:
this is how you get static files for fonrtend, and this is how you get dockerfile for backend, now go deploy it wherever.So you should be able to follow these and deploy it on GCP. As @Vinny (@Wasp) said, we are here to help, and maybe we can even produce some docs on how to deploy to GCP based on that together. Btw from what I know, GCP might also have some kidn of "startup consultancy" where they even can help you with that if needed -> you know, to pick the best service they offer. AWS has something similar, although it can be slow enough to not be useful when you need to move fast. So dev vs prod -> we normally refer to dev environment as the one on your local machine, and production as to your final, deployed app, that users use. Sounds though like you alto want to deploy another, testing environment? That is usually called "staging" -> is that what you meant by "dev in GCP"? If so, we don't have any special instructions for that yet, that is true, but it will basically end up with you doing eveyrtying the same as for production, just setting up different env vars up there in the cloud (that is the point of "staging", you want it to be as similar to "production" as possible). Btw I am also more backend dev than frontend dev or dev op guy, so I undrestand the position :). Anyway, we are here to help, let's talk!
dang! saw it
be able to depoy now. thanks
hi , thanks i saw that instruction now. will try it 🙂
Thanks for elaborate answer. GCP does have cold start issues. i use cloud run for my core product api with global LB. But for fronend maybe will use something else and not cloud run. Also, considering azure container app for this as they don’t have cold start issue and have multi container support. And yes, need a test env. call it dev stage uat anything 🙂.
Got it!
GCP has cold start issues? Interesting. You could have your wasp server running all the time though, right? Keep in mind, for
jobs feature to work (if you are using it), you do need to have your wasp server constantly running. But you are instaed going for an option where server goes to sleep until client needs it (Fly has something similar, as an option, I don't have experience with GCP).
Yeah for frontend you can use enything really, it is quite easy to put it on netflify for example.
I am curious to hear what will work for you at the end, do please keep us posted!So i just went with fly.io. Keeping it simple for now. All the effort to manually deploy in GCP or other cloud wasn’t worth it cost wise as i am not expecting heavy traffic on my frontend (Product is B2B SaaS api. So users will just subscribe and create api keys. All the heavy work is being done by gcp cloud run! I might just get by fine with fly.ion free/basic plan for a long time🙂
Wohooo @azuriete, you just became a Waspeteer level 1!
Yeah, you did a right choice there I think, bset to get something going and then later you can optimize execution costs and similar!