Currently updating a website might incur downtime or glitching due to obvious reasons. There are two ways to combat this:
- Have a staging area that, at the end of upload, replaces the original directory
- rollback: rollback can utilize the trash bin
- Opt-in to create timestamp named dirs and finally
current.txt selects the active website to be served
- allows easy rollback but hurst the native SPO version tracking even more
There might be no obvious way to make the SPO version tracking work well.
On the other hand, perhaps this is too advanced feature for such a simplistic deploy tool. If zero downtime is needed, perhaps Ship is not the right too in the first place.
Currently updating a website might incur downtime or glitching due to obvious reasons. There are two ways to combat this:
current.txtselects the active website to be servedThere might be no obvious way to make the SPO version tracking work well.
On the other hand, perhaps this is too advanced feature for such a simplistic deploy tool. If zero downtime is needed, perhaps Ship is not the right too in the first place.