-
-
Notifications
You must be signed in to change notification settings - Fork 909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
private gem subdomains? #91
Comments
Awesome idea. Backlogging this until subdomains are ready. |
Unless there's going to be a fee associated with private subdomains that will go to some kind of common pot to improve Gemcutter I'm against this idea. Gems are made to be open source, and supporting this kind of private domain in what is becoming the de facto standard of gem hosting will only encourage companies to go closed source on more gems. |
Ooh, good concern. I have no intentions of ever making this a pay service. I can barely manage my own wallet at that. Perhaps we should instead encourage orgs to fork the project and run it within their firewall. |
To add my 2 cents... +1 for private gem hosting, with a fee that goes to support Gemcutter. |
I plan to spin jrun/rubygems-proxy_server into a intranet gem server. The goal is to make it api compatible with gemcutter so "gem push" (and therefor tools like Jeweler) just work. |
I've been suggesting cwninja/geminabox if anyone needs to run a private gem server. Considering this a non-issue. |
According to this, you guys are planning on using subdomains for namespaced gems. One thing I've wanted to do is store private gems in a central location. I don't really know how the rubygems protocol works, but I imagine private gems could be installed like this:
Just a thought...
The text was updated successfully, but these errors were encountered: