I m developing my app locally on `<http dev app mycoolsite c Serverless Stack #help

I’m developing my app locally on `<http://dev.app....

Devin

11/12/2021, 12:45 AM

I’m developing my app locally on

<http://dev.app.mycoolsite.com|dev.app.mycoolsite.com>

<http://dev.api.mycoolsite.com|dev.api.mycoolsite.com>

and

<http://dev.mycoolsite.com|dev.mycoolsite.com>

. I haven’t yet pushed to prod because I don’t really have anything

prod

worthy yet. So my workflow is typically

Copy code

develop locally => push to main (this runs test etc… and deploys to dev)

Is there any reason that I should, or should not, promote to

prod

Michael Clifford

11/12/2021, 12:49 AM

I typically have merges to main deployed automatically to a lower environment. Once those changes are verified to be production ready (whether it be on lower-env integration tests or QA, etc) I have deploys to prod happen based on the creation of a git tag (or a git release which is just a tag with some meta data)

Adrian Schweizer

11/12/2021, 1:12 AM

if you don't have anything prod worthy, I see no reason why you'd want to go there

Adrian Schweizer

11/12/2021, 1:14 AM

but like I just noticed, it's probably a good idea to do an sst deploy some time before you plan to go live, because it generated some problems that didn't appear with sst start

Adrian Schweizer

11/12/2021, 1:15 AM

namely the bcrypt lib couldn't be built, because it was missing some modules that it didn't miss during sst start for some reason

Devin

11/12/2021, 12:18 PM

Thanks for the answers ya’ll!

Frank

11/13/2021, 7:02 AM

sorry to hi-jack this thread 😁 @Adrian Schweizer how did u fix the bcrypt issue in the end?

Adrian Schweizer

11/13/2021, 3:56 PM

@Frank I just had to install those modules it was complaining about, I think it was mock-aws-s3 and nock

Open in Slack

Previous Next