Seems they're from Russia, so no native English speaker. Neither am I, and when I've first seen the site's name I've looked it up, found one of its possible meanings (backpackers' hostel) and liked the link to a vagrant.
You made me curious, and it seems that the words original (English) meaning was a "rest house for travelers" (From the French "hospice," which is from the Latin word "hospes, that also brings us the English "hospitality.) It is interesting how the meaning of words, especially English ones, can morph so.
But, yeah, anyway I would suggest changing the name. My first thought was of death, and it was really only a morbid fascination that caused me to click on the link.
I appreciate your saying that. I am definitely one of these people. For me, the word "hospice" only brings to mind the most difficult time of my life - taking care of my mom as she was dying from cancer.
I realize that there is a sense of the word that's related to "vagrant". But when I do a Google search, every single result on the first page has to do with end of life care. It's just stunning that someone could possibly think this is a good idea.
Rather than merely considering it, just do it. It's an early-stage project and now is the easiest time to do it. And, no, I wouldn't go with painfulcancerdeath.io.
I work in the homehealth/hospice software industry and I will say: Change your name.
Hospice is end of life care. Hospice is understanding that death is coming and approaching it painlessly, intentionally and hopefully as happily as possible. To get into hospice you must be certified by a doctor as being terminal, (generally) less than 6 months to live.
Hospice is about bringing a life to a close with as much dignity as the illness allows.
The people in that industry are amazing, magical individuals and I do not know how they have the strength and tenacity to face every day like they do (although their amusing brand of dark humor seems to help).
Seriously though -- why would you want your product associated with terminal end of life diagnosis and care?
Why the Ruby dependency for creating cookbooks?
I don't prefer installing frameworks I'm not using as add-ons for another product - can vagrant do the extras?
Well, Vagrant provides a hook for different provisioning frameworks. I believe that Puppet and Chef and officially supported. The project uses Chef, which is written in ruby and uses ruby-based cookbooks to do its work. So it is pretty unavoidable. Also, Vagrant is written in Ruby last I checked, so if you are using Vagrant you already have a Ruby dependency.
Sorry if I've misunderstood.
As an aside, I thought it would be cool to build a service like this, so it's great that somebody did it. However the name definitely has the wrong connotation.
We are waiting for 1.2.0 Vagrant release to make use of the librarian plugin. Vagrant self-installer will solve Windows issue. It contains several tiny bugs atm unfortunately :(
Really? This is possible without paying more than the cost of VMWare Fusion?
I'd love to switch to fusion (which would necessitate buying it), but I'm not going to pay more than the cost of fusion for the provider adapter for vagrant. Are there any free/open source ones about yet?
Because it works better. Less crash, freeze... And VMWare Fusion is product of VMWare so there is no other way to have it for free. But anyway it is not that much.
I'm new to both vagrant and chef, so this looks pretty useful for me . I selected rvm but it looks like it used rbenv, but I might be wrong. Also, the name really stinks.
