Skip to content
This repository has been archived by the owner on Dec 4, 2020. It is now read-only.

how to keep the vagrant instance up to date? #13

Open
hanoii opened this issue Oct 4, 2014 · 3 comments
Open

how to keep the vagrant instance up to date? #13

hanoii opened this issue Oct 4, 2014 · 3 comments
Assignees
Labels

Comments

@hanoii
Copy link

hanoii commented Oct 4, 2014

Once you have the vagrant up, what's the proper way of keeping up with code chagnes? What should be updated on it?

I think this worth documenting on the readme.md

@hanoii hanoii changed the title update code how to keep the vagrant instance up to date? Oct 4, 2014
@niwinz niwinz self-assigned this Oct 5, 2014
@niwinz niwinz added the bug label Oct 5, 2014
@niwinz
Copy link

niwinz commented Oct 5, 2014

You are completely right! I mark it as a bug.

Thanks for report it!

@anler
Copy link

anler commented Oct 5, 2014

I think the better approach is, in your side, to pull updates from taiga-vagrant repo and reprovision you instance:

git pull origin master
vagrant up --provision

and in our side, to add a script that takes care of the update when you re-provision your instance.
Doing that shouldn't be too difficult.

@niwinz
Copy link

niwinz commented Nov 4, 2014

Reprovisioning is almost ready on taiga-scripts repo (the vagrant repo does not need changes, I'll try to release them in few days.

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

No branches or pull requests

3 participants