vagrant sandbox on
vagrant ssh
vagrant sandbox commit
vagrant sandbox rollback
vagrant sandbox off
I happened to be building and testing some packages today and gave it
a go. Worked perfectly for me. Good job.
G
> You can use it to try out new stuff, without having to resort to a vagrant
> destroy for easy rollback.
>
> https://github.com/jedi4ever/sahara
>
> It's a first cut and I haven't got feedback if this works well within other
> people's environments.
> I'd love to hear your feedback (does it work for you? any feature requests?)
>
> Patrick
>
>
> Typical usage would be :
>
> Enter sandbox mode:
>
> vagrant sandbox on
>
> Do some stuff:
>
> vagrant ssh
>
> If satisfied apply the changes:
>
> vagrant sandbox commit
>
> If not satisfied you can rollback:
>
> vagrant sandbox rollback
>
> To leave sandbox mod:
>
> vagrant sandbox off
>
--
Gareth Rushgrove
Web Geek
P.S. Now what was that great Vagrant plugin you tweeted about ? :)
I haven't written it yet :)
Next couple of weeks hopefully I'll grab some time to finish it off
and make sure it's useful.
Gareth
--
Patrick, it's awesome! No problems so far.
*My scenario*
I installed sahara while having a Vagrant already box running.
Sahara simply "hooked in" the running machine and I could "sandbox"
right away.
So I could use "vagrant sandbox on" without stopping the machine, do my
tests and "vagrant sandbox rollback" to restored the original state.
Exactly what I expected.
Great work! And again a very smart Gem name :)
*Feature requests*
none.
Instead your Gem could probably make this feature request on Vagrant
obsolete:
https://github.com/mitchellh/vagrant/issues/143
Best
Christian
I think it's probably a dilemma: the integration of the gem is done
through executing the commandline Virtualbox commands.
In Vagrant we are aiming more for API calls through virtualbox API and
in the future via Libvirt maybe.
The same goes for the veewee gem, and is probably the main reason for
not integrating it into vagrant code base.