is there any way to force a static site deployment...
# help
k
is there any way to force a static site deployment when running
sst start
and using the StaticSite construct? The issue is that I have a single step where I need to access the deployed static site (to setup some auth) and then the remainder of my access will be through localhost, but at the moment this means I first need to run
sst deploy
and after auth I run
sst start
. Also, it seems like
sst start
replaces the deployed static site with the placeholder site after a
sst deploy
, so if there was an option to suppressing the placeholder deploy, it would also solve my problem.
t
Ah interesting. I don't think there's a way to do this right now I can make an issue for it. The problem is if we add a boolean to force it, you still have to remember to turn it off so you don't have to way for a full deployment every time you do SST start.
k
Ok thanks.. so the reason for the placeholder is a faster start? I think I'd be fine with that caveat given the current cycle of sst deploy + auth + sst start
t
I'll make an issue an implement that