Show HN: Hospice.io – Vagrant configurations generator | Hacker News Reader

Show HN: Hospice.io – Vagrant configurations generator

hospice.io

93 pointsinossidabile46 comments

I'm not sure what connotations you were going for with the word "hospice", but I'd really suggest choosing a different name.

A worse combination of TLD (io) and name (hospice) I have probably not seen. The graphical imagery conveyed by hospice I/O is tragic and sad.

To me .io is generic. It is more expensive, though.

To me the name is so bad that even after the name changes I might prefer to use something else, all other things being close to equal.

Yeah...

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.

They did a good enough job on picking a new name and changing everything to use it that I no longer feel it's a weakness. http://rove.io/

We moved it to http://rove.io

But what was the thinking behind hospice in the first place?

hos·pice

/ˈhäspis/

Noun

A home providing care for the sick, esp. the terminally ill.

A lodging for travelers, esp. one run by a religious order.

Which part of my comment made you think I was asking for a definition?

hos·pice /ˈhäspis/ Noun 1 home providing care for the sick, esp. the terminally ill. 2 lodging for travelers, esp. one run by a religious order.

A weird choice of name indeed

One would associate 'shelter' with the word 'vagrant' more than 'hospice', which also makes it a strange choice.

It's now been renamed to http://rove.io (301s to it).

Definitely does feel as if the project name was chosen based on domain availability. Unfortunate example of putting the cart before the horse.

Came here to say this.

Well... That's just a name after all. Short and memorable.

For a lot of people that word will primarily be associated with memories of their relatives or loved ones dying.

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.

Makes sense. We will consider changing it. Thank you.

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?

Very cool. Django and the associated stuff (south, virtualenv, etc) would be a nice addition.

Yes. Also adding mercurial as a vcs option would be great.

Love it. Where can I find the source code for this nifty little utility so that I can add JVM/Clojure support?

http://github.com/aderyabin/hospice

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.

>>Vagrant is written in Ruby

Well, so it is. I'll sit down now.

I tried to run gems (and ruby) from the command line, but it was local to the /embedded directory (on Windows) so not part of the path.

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 :(

I just started using Vagrant. Can anyone recommend me any guide or tips?

This configuration generator looks like a very nice way to skip all the intitial setup, which looks confusing for a new Vagrant user.

A tip: use it with VMWare Fusion and not VirtualBox. It is the best.

Sorry I don't have any tutorial but it is not so hard to use.

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.

Pretty sure thats the only provider for Fusion.

Why?

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.

Any chance you could add salt stack generation as well?

It is usually more effective to create issues in GitHub repo, so I have created one for you: https://github.com/aderyabin/hospice/issues/11

Thanks! I was just thinking the other day about how I preferred when people do that rather than put requests in comments. Guess I'm just as guilty...

Any chance you could add Node.js? Perhaps installing bundler would be a good option too. That way you can get straight into development.

Could you please add lighttpd as well?

terrible name

git, svn, where is mercurial?

We were only able to add packages that we use ourselves for now. It will take some time but we are going to expand the list.

The only thing generated from a hospice is sadness...

Reply on news.ycombinator.com