Skip to content
This repository

The main site and assets of Rails Girls London

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 app
Octocat-spinner-32 bin
Octocat-spinner-32 config
Octocat-spinner-32 db
Octocat-spinner-32 lib
Octocat-spinner-32 log
Octocat-spinner-32 public
Octocat-spinner-32 spec
Octocat-spinner-32 vendor
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .rspec
Octocat-spinner-32 .ruby-version
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 Makefile
Octocat-spinner-32 Procfile
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
Octocat-spinner-32 config.ru
Octocat-spinner-32 logfile
README.md

Code Climate Build Status Coverage Status

Rails Girls London

This is the website and asset repository for the Rails Girls London website.

This app helps us run our local organisation.

Rails Girls London logo

On the web

Contributing to This Site

  1. Fork the repository
  2. Create your own branch git checkout -b mybranch
  3. Apply your changes
  4. Run rake to verify that the tests are passing
  5. Submit a pull request

Documentation should use Github-flavoured Markdown, but with explicit links.

We use Kippt for collecting resources. The mainpage dynamically pulls in resources from kippt if it's configured. If you'd like to see the links, either sign up for kippt yourself and configure it (look at config/kippt.yml.example for reference), or ask one of the core members for the username/token information. If you don't know what this means, feel free to ask or ignore it all together!

Please stick to Github's style guide

Deployment

Make sure you have access to the Heroku app. One of the organisers can arrange that.

heroku git:remote -r production --app=railsgirlslondon
heroku git:remote -r staging --app=railsgirlslondon-staging

Since we are using Heroku, the deployment is done via a git push to the appropriate remote repository. Since doing it properly involves several steps, we have a Makefile for the deployment. This means you can just use make to deploy:

git checkout staging
make deploy_staging

This will turn on maintenance mode for the staging app, add a tag for the release, push changes to the heroku app, run migrations and turn maintenance mode off again.

Backups

You can create a backup with:

make backup_production
make backup_staging

These commands will create a local copy of the PostgreSQL databases on Heroku.

Something went wrong with that request. Please try again.