HTTPS clone URL
Subversion checkout URL
Clone this wiki locally
Let’s admit it. RubyForge sucks. It’s been the same for years, has features we don’t need, and is simply not fun to work with. Gemcutter is the answer to these problems. What’s needed for gem hosting done right:
- A community-driven effort so it can be constantly improved
- A way to browse gems and download them
- An easy API to access information and upload/publish gems
The project’s name was originally gemesis, coined by technicalpickles. It seems that a company exists with the same name and a trademark. Hence, a change was necessary. The project was also called gemote for a day, but gemcutter is a lot snappier.
Let’s use this section for planning out the features of the site, the API, and how it will look.
- Project hosting, limited to:
- Project description
- Project page
- Download gem/tgz per version
- Hook into GitHub, Lighthouse
- API driven publishing
- /gems/show/my_gem – View the gem “My Gem”
- /gems/create – Create a new gem (HTTP POST)
- Determining who is the project owner. RubyForge does this by manually approving all new projects.
- Saving and storing gem files, and mirroring content
- Authentication over API. Should be done via a session key