This is a membership application app written by members of Double Union, a feminist hacker/makerspace for nonbinary people and women in San Francisco.
This app is named after a famous Virginia Woolf essay, A Room of One's Own. You can learn more about it on Wikipedia!
Also, here is a puppy that is saying "arooo":
- Prospective members can apply for membership
- Current members can vote and comment on applications
- Current members can see a directory of members
- Current members adjust their dues via Stripe
- Current members can apply for scholarships
- Membership coordinators can manage member status
- Emails are sent for applicants, accepted member setup reminders, cancelling mailers, dues issues, and scholarship requests (see
mailersfolder)
The application supports three levels of membership: members, key members, and voting members, where any member can see and comment on an application, but only voting members can vote. Membership coordinators can set whether the app is accepting applications, accept or reject individual applications, manage membership levels, and review dues status.
You can see screenshots of the system here: see our Arooo announcement post.
We welcome contributions from anyone! Please see our Contributing Guide for an overview of how to help, including how to set up your development environment and run the application.
You only need this if you are deploying code, checking changes, or maintaining a production instance of arooo
Set up heroku commandline client: https://devcenter.heroku.com/articles/heroku-cli
Staging: $ heroku run rails console --remote staging
Production: $ heroku run rails console --remote production
www.bugsnag.com is a heroku plugin that records errors in the production app. This is helpful for debugging. For bugsnag access, ask someone with access to the board@ section of 1Password to log into bugsnag and send you an email invite to create an account. Thank you to Bugsnag for their OSS program :)
This section only pertains if you have heroku & deployment access. Only maintainers have heroku access and can deploy.
If you are a DU member, see https://docs.google.com/document/d/19LbIYB2RDy-17UXuQx6wLgKp2EdLdqj-pg1cm3EpSb8/edit for more information on getting permission.
Both staging and production Heroku environments are connected to this GitHub repo, making it possible to deploy directly through the Heroku UI. To deploy:
- Staging: Merge to
master, and your code will be automatically deployed tostagingas soon as CI goes green. - Production: Log into Heroku, and select the production Aroo app from your dashboard. Click on "Deploy", and scroll to the bottom. There will be a place to select a branch to deploy, and a button that you can click to deploy.
Database migrations will run automatically during the release process on Heroku. This is controlled by the release directive in our Procfile.
If you prefer to do deploys from the command line, here are the steps:
- Add Heroku remotes to your
.git/config(typegit remote --helpfor more instructions on how to configure git remote.)
[remote "production"]
url = [email protected]:du-arooo.git
fetch = +refs/heads/*:refs/remotes/heroku/*
[remote "staging"]
url = [email protected]:doubleunion-staging.git
fetch = +refs/heads/*:refs/remotes/heroku/*
- Pull down the latest code from
master
git checkout master
git pull --rebase origin master
- If CI tests are passing, push to the
stagingenvironment
git checkout master
git pull --rebase origin master
git push staging master
- If needed, perform rake tasks or set ENV variable settings on
staging - Test staging!
username: doubleunion
password: meritocracyisajoke
- After confirming that the code works on
staging, push it toproduction!
git checkout master
git pull --rebase origin master
git push production master
- If needed, perform rake tasks or set ENV variable settings on
production
As of July 2020, the environment variables set in Arooo's production environment are:
AWS_ACCESS_KEY_ID
AWS_REGION
AWS_SECRET_ACCESS_KEY
BUGSNAG_KEY
CANONICAL_HOST: app.doubleunion.org
DATABASE_URL
GITHUB_CLIENT_KEY
GITHUB_CLIENT_SECRET
GOOGLE_CLIENT_ID
GOOGLE_CLIENT_SECRET
HEROKU_POSTGRESQL_CYAN_URL
HEROKU_POSTGRESQL_RED_URL
HOST_URL: app.doubleunion.org
LANG: en_US.UTF-8
MANDRILL_API_KEY
MANDRILL_USERNAME
NEW_RELIC_KEY
NEW_RELIC_LICENSE_KEY
NEW_RELIC_LOG
RACK_ENV: production
RAILS_ENV: production
SECRET_TOKEN
STRIPE_PUBLISHABLE_KEY
STRIPE_SECRET_KEY
STRIPE_SIGNING_SECRET
You can get the current values from Heroku, either via the web UI, under Settings > Reveal Config Vars, or using the Heroku CLI: heroku config --app du-aroo.
In your local development environment, you can set these variables in config/application.yaml.
TODO: It would be great to document these variables further, and figure out which ones are still needed.
This app sends emails via AWS: TODO more info here (we also have env variables set for Mandrill, are these still needed?)
Currently neither github nor google auth works on staging- we should get this working again so we can actually test.
The basic-auth login is found in https://dashboard.heroku.com/apps/doubleunion-staging/settings under BASIC_AUTH_NAME/BASIC_AUTH_PASSWORD
To report a security vulnerability with Arooo, see SECURITY.md. Thank you!
Copyright (C) 2014 Double Union
This program is free software: you can redistribute it and/or modify it under the terms of the GNU 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 LICENSE.txt file for the full license.