REFUGE restrooms indexes and maps safe restroom locations for trans, intersex, and gender nonconforming individuals.
JavaScript Ruby CSS HTML CoffeeScript Shell Gherkin
Latest commit 8ec906a Jun 13, 2017 @DeeDeeG DeeDeeG committed with mi-wood Activate high-res splash page background image on high-density screens (
#337)

* Activate high-res image on high-density screens

Devices with standard "1x" density will get a less detailed image.

Right now only city-photo.jpg (the splash page image)
has high-res alternate versions.

* Add compressed images, rename original

Compressed with Guetzli (1x), jpeg-recompress (2x), and Mozjpeg (3x)

Original-fullsize is direct from the camera
Permalink
Failed to load latest commit information.
.github add another checkbox Mar 27, 2017
.rake bumped bundler version for gemlock file, allowed bundler to function … Mar 15, 2017
app Activate high-res splash page background image on high-density screens ( Jun 13, 2017
bin Rails 5 Upgrade (#307) May 10, 2017
config Rails 5 Upgrade (#307) May 10, 2017
db Template changes for changing table Oct 18, 2015
features Remove sensor parameter from Google Maps API calls. (#340) May 2, 2017
lib Revert "changed test prepare to specify test schema" Dec 26, 2014
log initial commit. new rails app. Nov 27, 2013
promo Adding a promotional branch, to hold assets for promotion Apr 6, 2014
public cleaned up the people in the restroom signs to reflect the RefugeRest… Jul 5, 2014
script add pg_hba.conf changes Nov 24, 2014
setup fix setup with ruby_version newlines Mar 20, 2017
spec Rails 5 Upgrade (#307) May 10, 2017
vendor/assets initial commit. new rails app. Nov 27, 2013
.env Rails 5 Upgrade (#307) May 10, 2017
.gitignore remove .rake_tasks Mar 26, 2017
.ruby-version ruby: upgrade to 2.3.1 Nov 12, 2016
.travis.yml ruby: upgrade to 2.3.1 Nov 12, 2016
CONTRIBUTING.md use default vagrant sync (#328) Apr 5, 2017
Gemfile Rails 5 Upgrade (#307) May 10, 2017
Gemfile.lock Rails 5 Upgrade (#307) May 10, 2017
LICENSE.txt updated license to AGPLv3 Mar 5, 2014
Procfile Add heroku port support Feb 2, 2014
README.md Update README.md (#329) May 2, 2017
Rakefile add rake vagrant:shell helper command Apr 12, 2015
Vagrantfile use default vagrant sync (#328) Apr 5, 2017
app.json Add Heroku generated app.json Mar 27, 2017
config.rb Pend susy import Feb 2, 2014
config.ru initial commit. new rails app. Nov 27, 2013

README.md

Production CI: Build Status

Develop CI: Build Status

Stories in Ready

REFUGE restrooms

Providing safe restroom access to transgender, intersex, and gender noncomforming individuals.

REFUGE is an effort to fill the void left by the now-defunct Safe2Pee website. It provides a free resource to trans* and queer individuals in need of gender neutral and other safe restrooms.

This project is open source. Feel free to contribute. We could use the help.

Deployed Environments

Production: Link

Staging: Link

Contributing

Changes to the site can be tested locally before deploying to the web. To get set up to edit the site and test your changes, see CONTRIBUTING.md.

Deployment

This repo is set to automatically deploy to Heroku. Any time there is a merge into develop, the develop branch will be deployed to refugestaging.herokuapp.com. Any time there is a merge into master, the master branch will be released to refugerestrooms.org

When making a release, you should do the following:

  1. Check the status of the app on refugestaging.herokuapp.com and make sure it's functional.
  2. Make sure the the most recent build of develop is passing on TravisCI
  3. Run git flow release start %{release number}
  4. Run git shortlog --grep "Merge pull request #" %{previous release}..HEAD and copy the contents into a new issue with the release tag here on github. This command gives you a list of PRs merged since the previous release.
  5. git flow release finish and copy the contents of #4 into the release tags.
  6. git push in the master branch and git push --tags
  • this will trigger the heroku deploy to production.

Manual Releases

Currently, we deploy to Heroku. Our application is small enough that it is free to host on Heroku, and we dont mind the server having to wake up if nobody has accessed the site in a while.

We have both a staging and a production instance on Heroku. The staging instance can be found at http://refugestaging.herokuapp.com/

Here are the steps to deploy:

  1. Talk to @tkwidmer about getting access as a collaborator for both the production and staging Heroku instances.
  2. Link your local repo to the Heroku remote repos. I suggest doing it this way:
  • git remote add production git@heroku.com:refugerestrooms.git
  • git remote add staging git@heroku.com:refugestaging.git
  1. git flow release start %{release number}
  2. git push staging release/%{release number}:master and verify your changes on staging. (run any migrations heroku run rake db:migrate --remote staging)
  3. Run git shortlog --grep "Merge pull request #" %{previous release}..HEAD and copy the contents.
  4. git flow release finish and copy the contents of #5 into the release tags.
  5. git push and git push --tags
  6. git push production master and run any migrations heroku run rake db:migrate --remote production

Tech

  • Ruby Version - ruby-2.3.0
  • Ruby on Rails
  • RSpec
  • Javascript
  • HTML / SASS
  • Postgres
  • Geocoder Gem
  • Google Maps API
  • Twitter Bootstrap Framework
  • Deployed on Heroku

Links to Refuge project on other platforms

IRC

Server: irc.freenode.com Channel: #refugerestrooms

License

Copyright (C) 2014–2017 Teagan Widmer and contributors

This program is free software; you can redistribute and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License along with this program. If not, see http://www.gnu.org/licenses/.