`setup` task should be able to change config file

[bruno-]

Currently, invoking this plugin's setup task makes updates only the first time. On consequent setup invocations, config files are not updated.

IIRC this was done this way because I didn't know how to makes updates to the unicorn initializer file - task here. By repeatedly invoking that task, the initializer file is not updated (even though as a user I would expect an update). Update: see next comment

To keep all the setup tasks consistent, updates were disabled for all of them.

With proposed updates in #13, @rhomeister suggested config files should be update-able.

The simplest way to do that would be:

• just remove all the "guards" for these tasks, example1, example2 (same for nginx)
• figure out a way to "force" updates for the config file in unicorn:setup_initializer task. Not really sure how to do this and that's why I'm starting a discussion... feel free to write ideas! Update: see next comment.

[bruno-]

I started investigating this and it turns out I had the wrong idea what is going on here this whole time.

I thought sudo update-rc.d -f unicorn_<appname>_production defaults creates some special files in /etc/rc<x>.d/ dirs, while in fact it only creates symlinks that point to the /etc/init.d/unicorn_<appname>_production script.

So actually - we're good here! All we need to do is this:

• just remove all the "guards" for these tasks, example1, example2 (same for nginx)

Sorry for this confusion here @rhomeister, feel free to open a PR whenever you want!

[rhomeister]

OK, I was confused as well. It worked perfectly without the guards and that is how I understood that the init.d files worked in Linux. ;) I'll get this done.