Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage Capistrano rollback #2

Open
nicolas-brousse opened this issue May 5, 2017 · 3 comments
Open

Manage Capistrano rollback #2

nicolas-brousse opened this issue May 5, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@nicolas-brousse
Copy link
Member

On Capistrano rollback, check that the services installed and who are running are the goods ones.

@nicolas-brousse nicolas-brousse self-assigned this May 5, 2017
@nicolas-brousse nicolas-brousse modified the milestone: 1.0.0 May 5, 2017
@nicolas-brousse
Copy link
Member Author

The current problem with rollback is that there is no way (with the current structure) to get the previous services files and their content.

@nicolas-brousse
Copy link
Member Author

@nicolas-brousse
Copy link
Member Author

So, does the process of apply Procfile update on servers is really a good idea?
May be the best is to apply manually or even directly use foreman gem to make exports. The advantage of this plugin for now is some methods to start/stop/restart/kill, enable/disable and the fact that the creation of services do not need a gem installed on the application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant