This is the Bike Index
Bike registration that works: online, powerful, free.
Registering a bike only takes a few minutes and gives cyclists a permanent record linked to their identity that proves ownership in the case of a theft.
We're an open source project. Take a gander through our code, report bugs, or download it and run it locally.
PostgreSQL >= 9.6
Requires 1gb of ram (or at least more than 512mb)
Running Bike Index locally
This explanation assumes you're familiar with developing Ruby on Rails applications.
bundle installinstall gems
rake db:setupcreate and seed your database
./startstart the server.
Go to localhost:3001
Run the test suit in the background with
bundle exec guard
You may have to manually add the fuzzystrmatch extension, which we use for near serial searches, to your databases. The migration should take care of this but sometimes doesn't. Open the databases in postgres (
psql bikeindex_test) and add the extension.
CREATE EXTENSION fuzzystrmatch;
Vagrant development box
For your convenience, this repository contains a Vagrantfile which is used to automatically set up and configure a virtual local (Ubuntu Xenial) development environment with all of the required dependencies preinstalled.
A computer that supports hardware virtualization (Intel VT-x/AMD-V)
At least 1.5GB of free memory
vagrant up to start the virtual machine. Upon first run, it will run various provisioning scripts to install all of the required packages, configure PostgreSQL, and run all of the Ruby commands to initalize a local Bike Index dev environment. Port 3001 is forwarded locally for testing. Be warned, it will take around a half hour or longer (depending on your internet connection) on first run to download additional Vagrant dependencies and to provision the dev environment. You may observe some informational warning messages during the initial setup which you can safely ignore.
vagrant halt to shutdown the VM. Subsequent startups will take considerably less time after the initial run.
If the initial provisioning fails for any reason, try running
vagrant provision and see if running the provisioner again completes without error. If not, please try to troubleshoot/google issues as much as possible before filing an issue. Many Vagrant related errors/issues have already been solved and are documented between Stackoverflow and Github. If you run in to an issue you're unable to solve, be sure to include all relevant stdout messages and errors.
Have a bug or a feature request? Open a new issue.
Keep track of development and community news.
Open a Pull request! The earlier you open the pull request, the earlier it's possible to discuss the direction of the changes.
If your pull request contains Ruby patches or features, you must include relevant rspec tests.
... and go hard