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

Capistrano deployment #205

Closed
DemocraciaPopular opened this issue Sep 30, 2022 · 3 comments
Closed

Capistrano deployment #205

DemocraciaPopular opened this issue Sep 30, 2022 · 3 comments

Comments

@DemocraciaPopular
Copy link

DemocraciaPopular commented Sep 30, 2022

Hi guys. I was finally able to get to the point to be able to deploy with Capistrano. However, I have a question.

The instructions in the installer docs for local development allow the user/developer to run latest Consul master branch.

On the other hand, the instructions guide to deploy Capistrano guide the user to deploy a production instance of Consul from stable (1.5.0) branch.

I my case, the stable branch works on remote server but not on local environment. On the other hand, deploying master branch on local and remote works fine.

So my question is, is this workflow intended mostly to work with latest master branch and leave stable production install untouched? That would make sense as deploying a stable version through capistrano wouldn't make sense if the stable version doesn't work locally (it would require to manually modify files on the vps, defeating the purpose of capistrano).

Anyway, I would appreciate some further elaboration on this workflow.

kind regards

ps: in the instructions, it instructs the user to run git checkout origin/1.5.0 -b stable but for me only works removing the "origin" word from the commmand.

@DemocraciaPopular
Copy link
Author

DemocraciaPopular commented Sep 30, 2022

An update: for some reason yesterday stable release didn't work on local environment but todays it works (apparently the app doesn't work immediately after creating and checking out into a branch, so have to checkout some where else and be back and then it works?)

Anyway, the question still stands. Is it better to have a stable release working on production, or the latest master version?
What is more convenient in terms of, say, upgrade to next release?

@javierm
Copy link
Member

javierm commented Oct 4, 2022

Hi, @DemocraciaPopular 😄.

It's better to have a stable release on production because we don't guarantee that the master branch is production-ready at all times. We also provide instructions to upgrade from one release to the next one (usually it's just running the consul:execute_release_tasks task), but upgrading from a non-stable version is not officially supported.

Hope that clarifies the point!

@javierm
Copy link
Member

javierm commented Mar 21, 2023

Hi, @DemocraciaPopular 😄.

I'm closing this issue as it was already answered. By all means, if you think this issue should still be open, please reopen it and tell us what we can do to solve it.

@javierm javierm closed this as completed Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants