Vagrant configuration update

[Subhas Dandapani]

Hi folks,

TL;DR -

With the latest commit, Vagrant will be noticeably slow during development.

If you want the speed boost back, run vagrant plugin install vagrant-faster

We had some Vagrant config for checking the available RAM/CPUs in your machine, and then setting the VM memory/cpus accordingly for good performance.  Although the result was good, it made the Vagrantfile ugly. So I extracted it out into a separate Vagrant plugin vagrant-faster. It will do exactly the same - check your machine capacity and increase VM memory/cpus when possible.

- Subhas

[John D. Hume]

Considering that looking at the Vagrantfile should not be required for using vagrant, it seems like it's worth letting the file look ugly to avoid adding a step to the dev setup. Can you put the ugliness back in, or hide it away in some way that doesn't require every user doing an extra step (and worst of all, a step that, if you miss it, allows things to still technically work, but be worse than they should)?

--
You received this message because you are subscribed to the Google Groups "rapidftr" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rapidftr+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Subhas Dandapani]

Hi John, generally this now reflects Standard Vagrant, so maybe not worse than what Vagrant users are normally accustomed to without any hacks. Maybe its only me who has been adding this "hack" on every vagrant project that I work on? But yeah, makes sens to add those back temporarily.

Btw - I've seen you active on vagrant developer groups. And as you know, they deprecated Vagrant.require_plugin, making plugin management harder. I've proposed an alternative, perhaps you could offer any insights into that...

--

- Subhas

[John D. Hume]

Unfortunately my tracking of what's going on in vagrant ended a couple years ago, so I have very little context, but I'll take a look.

[Subhas Dandapani]

Quick updates:

1. @RaoufAghrout reported that without those optimizations, cucumber browser tests fail with out of memory.

2. Interim measure - I updated the Vagrantfile in a little different way - it will prompt the user to install the plugin.
3. Am looking at a straight-forward way to directly install the plugin - either through vagrant actions, or by just shelling out.

[Subhas Dandapani]

Another Vagrant update:

* Sunspot will now automatically start whenever we boot the VM, so no need to start it manually

* RSpec/Cucumber tasks have all now been standardized. You now no longer need to specify RAILS_ENV, just run rspec or cucumber as you please!

- Subhas

--

- Subhas