hey guys, great conference today! so i’m going to launch my SST app in about a week and i’m looking for advice on how to deploy & manage my production environment. for now i’m deploying my prod stack from the cli using

sst deploy --stage prod

. obviously that’s not the technique i want to use going forward. my current plan is to use SEED as you describe here (https://serverless-stack.com/chapters/getting-production-ready.html) . • is SEED still the path you’d recommend? • what other things should i be aware of for my production deployment process? thank you!

Something like SEED provides a lot of benefits, of course, but do you really need them? There's nothing wrong with cli deployment IMO, if you are on a solo project and don't have to constantly push out new features

The nice thing about using a platform like Seed is that it's consistent. Less prone to human error. You'll never forget to yarn(install dependencies), or have the right

.env

file before actually deploying. And once it's setup, it's either CI/deploy on commit(to your branch of choice), or at the click of a button.

You can also eliminate human error with some simple scripting, but the nice thing about the CI/CD platforms is that they pull everything together and make it easy to work with it as a team

@Adrian Schweizer yes, this is a solo project and the CLI certainly would work. but i think i’m more prone to human error than other humans, so i want to have an infrastructure that defends against my mistakes…

SEED is certainly a good fit for SST

oh man, you’re telling me. i’ve build ML, the SST infra w/graphql, a react native app working on both iOS and android, and a nextjs site. i’m tired. lol.

yeah, we got a long way from apache + some cgi + html to what we have now

i’ll check out tailwind at some point. i initially built on the serverless framework and it just wasn’t sustainable. thank goodness for SST.

tailwind is just some prepared css classes with very good granularity and combined with a good frontend framework like react, you can almost completely avoid having to write any CSS at all

the web is the area i’ve invested the least and will likely need a refactor. i’ll take a look and perhaps swap out bootstrap for tailwind

yeah, no hurry. if you can deal with bootstrap, it's fine, too, in my opinion

yeah, i’m not in love with it, but i used it years ago and just wanted to move quickly with the www stack…

but if I already had a bootstrap app, I would probably not rip it out and replace it with tailwind, because there would certainly be more pressing matters

ok, cool. thanks for the advice! 👍🏻

would be cool if you could update this thread with your deployment experiences, once you've gone into prod (and remember it and have the time, of course)

yeah i’d love to give back to the community with some of those experiences.