You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That generates the site and uploads it to my staging bucket, and then regenerates it again and uploads to production.
This is slow, and it also creates an extra copy of the site in my /tmp directory. It's not eating a ton of disk space, but it's more than necessary. It would be nice if this worked:
$ tarbell publish staging production
This could generate a single copy of the site, then upload those same files to both staging and production.
The text was updated successfully, but these errors were encountered:
On Thu, Mar 10, 2016 at 4:10 PM, Chris Amico [email protected]
wrote:
I run this a lot:
$ tarbell publish && tarbell publish production
That generates the site and uploads it to my staging bucket, and then regenerates
it again and uploads to production.
This is slow, and it also creates an extra copy of the site in my /tmp
directory. It's not eating a ton of disk space, but it's more than
necessary. It would be nice if this worked:
$ tarbell publish staging production
This could generate a single copy of the site, then upload those same
files to both staging and production.
—
Reply to this email directly or view it on GitHub #406.
"Medical statistics will be our standard of measurement: we will weigh life
for life and see where the dead lie thicker, among the workers or among the
privileged." -- Rudolf Virchow
I run this a lot:
$ tarbell publish && tarbell publish production
That generates the site and uploads it to my staging bucket, and then regenerates it again and uploads to production.
This is slow, and it also creates an extra copy of the site in my
/tmp
directory. It's not eating a ton of disk space, but it's more than necessary. It would be nice if this worked:This could generate a single copy of the site, then upload those same files to both
staging
andproduction
.The text was updated successfully, but these errors were encountered: