I have added the stop hook [1] and taken a close look to the cause of not working deployment [2].
As you might read from [2], I think it is just a bug on PostgreSQL side, hence I have added some specific workaround instructions on README.
Final note: I usually rsync any change from GitHub repository [3] to the branch related to this issue [4], while I see you've been pulling the code from GitHub. I am naturally fine with this but I was wondering: what is the best practice?
I have added the stop hook [1] and taken a close look to the cause of not working deployment [2].
As you might read from [2], I think it is just a bug on PostgreSQL side, hence I have added some specific workaround instructions on README.
Final note: I usually rsync any change from GitHub repository [3] to the branch related to this issue [4], while I see you've been pulling the code from GitHub. I am naturally fine with this but I was wondering: what is the best practice?
Regards.
[1] https:/ /github. com/Tirasa/ SyncopeJujuChar m/issues/ 16 /github. com/Tirasa/ SyncopeJujuChar m/issues/ 17 /github. com/Tirasa/ SyncopeJujuChar m /code.launchpad .net/~francesco -chicchiricco/ charms/ precise/ syncope/ trunk
[2] https:/
[3] https:/
[4] https:/