Skip to content
This repository has been archived by the owner on Jun 7, 2022. It is now read-only.

Virtualization #38

Closed
kfatehi opened this issue Aug 7, 2013 · 1 comment
Closed

Virtualization #38

kfatehi opened this issue Aug 7, 2013 · 1 comment

Comments

@kfatehi
Copy link
Owner

kfatehi commented Aug 7, 2013

I'm finding myself hesitating to setup bait for some of my larger ruby projects. Why? Because I'm not using RVM on this particular box.

Bait is awesome and simple as it stands right now -- but perhaps one of the first configuration options it should get is to virtualize for tests. How? Well, we have Vagrant at our disposal.

It would be pretty trivial to enable the bait server owner to flick on an option to use Vagrant.

The first step towards this ticket would probably be to use slop instead of the current Bait::CLI module, then to establish a convention for config -- at first this can just be a flag passed into bait.

This ticket is in development and might get trashed, I'm not sure yet -- but I'm definitely not comfortable running things outside of a VM in a production run of Bait.

@kfatehi
Copy link
Owner Author

kfatehi commented Oct 15, 2013

user can do this via script.

@kfatehi kfatehi closed this as completed Oct 15, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant