Add 'no delete' option

[paulbowler]

I use s3_website to deploy my octopress blog to an S3 bucket that also contains my website.

Running s3_website deploy deletes all these website files first, which I do not want. These website files change regularly and there are too many to list as exceptions to delete.

An option such as 's3_website deploy -nodelete' or an item in the config to disable all deletes would be very useful.

[laurilehmijoki]

Hi @paulbowler, have you taken a look at the ignore_on_server setting? The documentation is here: https://github.com/laurilehmijoki/s3_website#ignoring-files-you-want-to-keep-on-aws.

Does that setting solve your problem?

[paulbowler]

Yes, I've seen that. It works but the problem is that all files and folders need to be named individually. In my example there are many hundreds of files and folders, some of which are shared with the blog.

A general 'no delete' option would be very welcome to ensure deploying either the website or blog does not break anything.

[laurilehmijoki]

Out of curiosity, why do you keep the other files in the blog bucket? I'd like to understand your use-case.

[laurilehmijoki]

I just released the version 2.4.0. In that version you can define a magic word that prevents all S3 object removals:

ignore_on_server: _DELETE_NOTHING_ON_THE_S3_BUCKET_

How does this work for you?

The commit is here: c64c749. I appreciate any feedback on it.

[paulbowler]

I'll give it a go - many thanks for the rapid code update.

Regarding my use case, I host note than just the blog on the bucket - the static website it also hosted there. At the moment, when I update the blog, all the website files are first deleted effectively bringing it down. Once the blog has been updated I then need to redeploy the website.

This is not a good update flow.

[paulbowler]

Code update does the job! Many thanks again.