Reunite more stray animals with their human companions
You can see a running version of the application at http://straymapper.com/.
Instructions for creating a development environment for Ubuntu Linux. This has been tested using Ubuntu 12.04.
#Initial libraries needed
$sudo apt-get install build-essential git-core python-software-properties python-dev python-pip python-virtualenv
#PIL Dependencies
$sudo apt-get install build-dep python-imaging
Also symlink associated libraries:
sudo ln -s /usr/lib/`uname -i`-linux-gnu/libfreetype.so /usr/lib/
sudo ln -s /usr/lib/`uname -i`-linux-gnu/libjpeg.so /usr/lib/
sudo ln -s /usr/lib/`uname -i`-linux-gnu/libz.so /usr/lib/
#SQLite Dependencies
$sudo apt-get install sqlite3 libsqlite3-dev
#Spatialite Dependencies
$sudo apt-get install libproj-dev proj-bin libgeos-dev libgdal-dev libspatialite3 libspatialite-dev spatialite-bin
Instructions for creating a development environment on Mac. This requires that Homebrew is installed.
$ brew install sqlite3
$ brew isntall geos
$ brew install proj
$ brew install gdal
$ brew install libspatialite
Note: Without Homebrew
Install the correct libspatialite library from Spatialite for your Mac.
git clone git://github.com/codeforamerica/straymapper.git
cd straymapper
pip install -r requirements.txt
touch straymapperdb
spatialite straymapperdb "SELECT InitSpatialMetaData();"
./manage.py syncdb
./manage.py runserver
./manage.py runscript animals.scripts.populate
In the spirit of free software, everyone is encouraged to help improve this project.
Here are some ways you can contribute:
- by using alpha, beta, and prerelease versions
- by reporting bugs
- by suggesting new features
- by translating to a new language
- by writing or editing documentation
- by writing specifications
- by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
- by refactoring code
- by closing issues
- by reviewing patches
- financially
We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate support for an existing issue by voting it up. When submitting a bug report, please include a Gist that includes a stack trace and any details that may be necessary to reproduce the bug, including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with failing specs.
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix.
- Add tests for your feature or bug fix.
- Run
./manage.py test. If your changes are not 100% covered, go back to step 4. - Commit and push your changes.
- Submit a pull request. Please do not include changes to the gemspec or version file. (If you want to create your own version for some reason, please do so in a separate commit.)
Copyright (c) 2012 Code for America. See LICENSE for details.