Ignoring Files

[jescalan]

So while you can ship to different environments, it would be excellent to be able to ignore certain files from push. For example, if you have a configuration file that you'd like to have different between development and production, you could have the development version locally but ignore it from ship. Then you could manually place a production version of the config file on the server. Because your local one is ignored, it would never overwrite the production one.

Bonus points for figuring out a way to make this process even smoother. Perhaps there could be a config folder somewhere outside the public folder you ship that holds all versions, and if ship could push individual files rather than just folders (which it should be able to do anyway) you could set up an after task to also ship that environment's config file.

[hhsnopek]

Add this feature to be found in ship.conf & a cmd line option -i ,--ignore [folders] for pre-defining the ignored folders/files. When used in roots I'm assuming ship.conf will be used, if so then we'll have to have ship.conf automatically ignored(security purpose). That being said we could have ship.conf pull ignored folders/files from app.coffee, yet this seems wrong to have a function mainly for roots.

[jescalan]

Dont see any reason to define it on the command line, you can just keep it in the conf file then not have to remember the command line option every time you deploy

[jescalan]

Going back on my word and closing this to prevent confusion and since we do have this implemented in s3