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
The Netlify-CLI 2.x (see #13 for progress on compatibility) allows to deploy in preview/staging mode before pushing to production.
In a way it would double up with your Wagtail installation on which you can already preview your content, but it would offer an opportunity to review the built website before pushing live.
I'm not too sure how to best implement that just yet but for starter, there would probably be some sort of settings to decide whether to go live directly or in stages. In the latter case, maybe we could use the success hook so running the netlify command would trigger a deploy to staging and Netlify would notify the backend of its status. Then, there could be a button on that deploy to push to production. There's a catch though, pushing to production isn't like saying "take this staging version and set it live" but is actually a whole new deploy. Therefore if the site had been re-built in the meantime, it wouldn't push the same version live.
Any thoughts welcome.
The text was updated successfully, but these errors were encountered:
After pushing to the staging site, there is a Publish Deploy button on the Netlify admin which sets live the given version without the need to re-publish from scratch (with the risk of the version having changed). I can't find the way to do this from the CLI but I'll contact their support to confirm that.
The Netlify-CLI 2.x (see #13 for progress on compatibility) allows to deploy in preview/staging mode before pushing to production.
In a way it would double up with your Wagtail installation on which you can already preview your content, but it would offer an opportunity to review the built website before pushing live.
I'm not too sure how to best implement that just yet but for starter, there would probably be some sort of settings to decide whether to go live directly or in stages. In the latter case, maybe we could use the success hook so running the
netlify
command would trigger a deploy to staging and Netlify would notify the backend of its status. Then, there could be a button on that deploy to push to production. There's a catch though, pushing to production isn't like saying "take this staging version and set it live" but is actually a whole new deploy. Therefore if the site had been re-built in the meantime, it wouldn't push the same version live.Any thoughts welcome.
The text was updated successfully, but these errors were encountered: