Hi there, is there a possibility of raising severa...
# sst
j
Hi there, is there a possibility of raising several instances of the project locally? If a teammate raises his instance, mine stops it, e.g.
f
Hey @Joel Corona, each of ur teammates just have to use a different stage name.
j
Thx @Frank
f
The scenario you are describing often happens when u and ur teammates are sharing the same AWS account.
And if everyone is using the same stage ie.
dev
, only 1 person can run
sst start --stage dev
and he will kick out the previous person
j
uhmm that its
t
@Joel Corona what version of sst are you using?
f
We actually released a change to address this recently v0.41.0. 1. upgrade to the latest SST 2. remove
stage
from your
sst.json
3. next time when you run
sst start
, it will prompt you for a personal stage, for example u can use the stage name
joel
4. SST will store the stage name inside
.sst
5. add
.sst
to ur
.gitignore
So if everyone on ur team followed this, when running
sst start
, each person would automatically use their personal stage name stored in their
.sst
p
Can I suggest a small tweak to the implementation for this? When I followed these instructions it tried to set an invalid stage name because of an _ in my username. Can you tweak the script to make it suggest only valid defaults?
t
ah good catch, will make an issue
j
Hi there, where can I get an example of the .sst file? @Frank @thdxr
t
There is no
.sst
file, there's a new folder in the latest versions that includes a
stage
file where we temporarily store the local stagename.
j
oh nice
j
@Joel Corona If you have shared infrastructure that you do not want to replicate for each developer in your team, you can also extract it into another stack and then map your stacks and stages appropriately.