/fl-maps

Map in Meteor: used to organise social events globally, and list resources on a street sleeper map

Primary LanguageCSSMIT LicenseMIT

Focallocal logo

Official Website Build Status

Focallocal: Gathering Map and Brighter Tomorrow Map

Focallocal events is a part of the Focallocal movement.

Focallocal is an open, encouraging and supportive community for people who want to explore creative and fun ways to make our communities friendlier, more connected, safer and happier for everyone to enjoy living in.

Together, our ideas and the success stories from community members activities are shared and repeated by other Focallocallers all around the World, each making a positive difference to life in their local community.

Because organising social events to make our communities happier, and supporting people who are homeless in your local community, should both be as simple as ordering pizza

Project Information

There are 2 instances of this Meteor app running:

Travis CI builds from the master branch and pushes changes to the street-sleeper branch. Code for the two branches are mostly identical, and any differences between the two branches are achieved throught the il8n plugin.

Contributing

Meteor installation:

  • for windows, please follow the meteor installation steps on the Meteor website.
  • for linux, you can use curl https://install.meteor.com | /bin/sh to install meteor.
# clone the repository 
# if you forked the repo, clone your forked downstream repo 
git clone https://github.com/focallocal/fl-maps.git fl-maps

For repo setup:

  • Obtain the settings.json file from the slack channel and place it at project root.
  • Submit PRs to master. street-sleeper will be updated through Travis CI.
# enter the project folder
cd fl-maps

# Install npm dependencies
meteor npm install

# Install meteor packages and start meteor server
# make sure that you have the settings.json file at project root.
npm start 

Testing

Note that tests are being upgraded to Chimp/Mocha/Chai, please refer to issue #437.

CI

We have Travis build in place which monitors this repository.

Every commit to master branch results in a new build being triggered.

  1. Deploying
    • Deploy to http://gather.focallocal.org if it's a push to master branch
    • Changes are pushed to the Brighter Tomorrow Map, with variables between the two set in i18n
    • The workflow is configured in .travis.yml and deployment is configured in the expect script deploy.exp
  2. Pull Request
    • You first create a fork of fl-maps.
    • Then you clone your fork on your computer.
    • You set up 2 remotes: your fork named 'origin', and the fl-maps named 'upstream'
    • Before begining working on the code, you always pull everything from upstream inside your version of master, then you create a new branch, example - fixingBug32
    • When you are ready to upload the code, you create a push on you're ORIGIN remote.
    • Lastly, you go on github, inside your fork page, and you will see a button -- CREATE PULL REQUEST
    • ALWAYS pull everything from the UPSTREAM remote