|
|
|
|
|
|
by atmosx
3494 days ago
|
|
|
I use a static site generated called 'middleman' for my blog. I tested S3 deployment in the past and I must that it's not all that complicated. The PITA is that you need Cloudfront to handle SSL and if you're not using Route53 automating the upgrade process is more complex than it should be. > Can you deploy atomically? Hm, I'm not sure what atomically means in this context, S3 supports 'sync' so you basically can write a bash/ruby/python script to handle deployment (I use a rake task). > Can you rollback? Yes, I use git (gitlab) to keep track of changes, so rolling back is not a problem. |
|
|
I'm not saying it's super complicated but if extra features are costing you even a couple of hours of time it's probably worth paying to make the problem go away.
> Hm, I'm not sure what atomically means in this context, S3 supports 'sync' so you basically can write a bash/ruby/python script to handle deployment (I use a rake task).
Atomically means you either update all of the files or none of the files. If you're updating one file at a time there's a chance e.g. a visitor will see a new page but with the old CSS file. What happens with S3 here? Also, how do you deal with cache invalidation?
> Yes, I use git (gitlab) to keep track of changes, so rolling back is not a problem.
I personally prefer if you can rollback to a previously working deploy with a dedicated CLI/web rollback option than having to deploy again if that's what you mean. There's a chance your local setup or deploy script is messed up and it's quicker.