4Refugees

This app is built on the MEAN.JS stack, please see below for the MEAN.JS README, as well as for instructions on how to deploy this MEAN.JS app.

To see a prototype of the app running on the IBM Bluemix platform, please visit: https://4refugees.eu-gb.mybluemix.net/ Note that this website is just a demo, it is not actively monitored.

The 4Refugees app is meant to provide a marketplace where citizens and refugees can interact. Volunteers can offer services (such as language or job training), and refugees can search the list for offers near them (using geo-spatial searching) to select an offer that they need. Or, refugees can submit a particular service they need assistance with, and volunteers (or other refugees) can search requests near them to see if they can provide the needed assistance. The hope is that refugees can get individualized assistance to help them integrate into society and become productive citizens, and maybe also help new refugees integrate as well. Of course, besides the HTML text, there is nothing in the core app that is refugee-specific, the app can easily be tailored for any sort of marketplace situation trying to match offers and requests.

Taking from the basic MEAN.JS infrastructure, each feature of the app was designed as a separate module, and interactions/dependencies between modules are minimized as much as possible, to allow for easy integration and/or removal of specific modules as needed. The modules are:

• about - 'About us' display
• chat - not used, but came from MEAN.JS framework
• core - module to control header/footer, handle bootstrapping, etc
• firststep - resources to help newcomers find basic assistance before using the app marketplace
• geo - geospatial support, for providing coordinates of offers to be used in geo searches
• language - static and dynamic translation support. HTML text can be translated once, and displayed in the user's language of choice. Individual offers can use IBM Watson Language Translation service. 3 languages are currently supported - English, German, and Arabic.
• mails - send internal mail notifications to other registered users
• matches - handles matching of an offering between the 2 parties
• offerings - individual services being offered or requested
• share - common helper routines shared across modules, for example, SCSS for a common style
• tags - work in progress, codifying tags to make them easier to store in the database and to translate
• users - user profiles, user registration, login via social networks, etc

For language support, each 'view' (a module may have multiple views, for now, there is usually only a single view per module) obtains static text from the public/language/*/??_viewProperties. If adding new languages, the majority of the work is to translate all the text from one of the existing *viewProperties files to the new language. The other modules themselves do not (or should not) contain static text, they should always retrieve the properly-translated text from these properties files. Dynamic text entered by the user must be translated via a 3rd party service - the 4Refugees app is currently enabled to use IBM Watson Language Translation services, when available.

If you want to use 3rd party authentication or registration (i.e. via social websites), you will need to first register the proper IDs, credentials, and redirect URIs for your app, and then fill in the IDs and SECRETs in config/env/credentials.js.

The core design principle of the app is to keep things simple - users should be able to navigate through the site easily the very first time.


MEAN.JS is a full-stack JavaScript open-source solution, which provides a solid starting point for MongoDB, Node.js, Express, and AngularJS based applications. The idea is to solve the common issues with connecting those frameworks, build a robust framework to support daily development needs, and help developers use better practices while working with popular JavaScript components.

Before You Begin

Before you begin we recommend you read about the basic building blocks that assemble a MEAN.JS application:

• MongoDB - Go through MongoDB Official Website and proceed to their Official Manual, which should help you understand NoSQL and MongoDB better.
• Express - The best way to understand express is through its Official Website, which has a Getting Started guide, as well as an ExpressJS Guide guide for general express topics. You can also go through this StackOverflow Thread for more resources.
• AngularJS - Angular's Official Website is a great starting point. You can also use Thinkster Popular Guide, and the Egghead Videos.
• Node.js - Start by going through Node.js Official Website and this StackOverflow Thread, which should get you going with the Node.js platform in no time.

Prerequisites

Make sure you have installed all of the following prerequisites on your development machine:

• Node.js - Download & Install Node.js and the npm package manager. If you encounter any problems, you can also use this GitHub Gist to install Node.js.
• MongoDB - Download & Install MongoDB, and make sure it's running on the default port (27017).
• Ruby - Download & Install Ruby
• Bower - You're going to use the Bower Package Manager to manage your front-end packages. Make sure you've installed Node.js and npm first, then install bower globally using npm:

$ npm install -g bower

• Grunt - You're going to use the Grunt Task Runner to automate your development process. Make sure you've installed Node.js and npm first, then install grunt globally using npm:

$ npm install -g grunt-cli

• Sass - You're going to use Sass to compile CSS during your grunt task. Make sure you have ruby installed, and then install Sass using gem install:

$ gem install sass

Downloading MEAN.JS

There are several ways you can get the MEAN.JS boilerplate:

Cloning The GitHub Repository

The recommended way to get MEAN.js is to use git to directly clone the MEAN.JS repository:

$ git clone https://github.com/meanjs/mean.git meanjs

This will clone the latest version of the MEAN.JS repository to a meanjs folder.

Downloading The Repository Zip File

Another way to use the MEAN.JS boilerplate is to download a zip copy from the master branch on GitHub. You can also do this using wget command:

$ wget https://github.com/meanjs/mean/archive/master.zip -O meanjs.zip; unzip meanjs.zip; rm meanjs.zip

Don't forget to rename mean-master after your project name.

Yo Generator

-Another way would be to use the Official Yo Generator, which generates a copy of the MEAN.JS 0.3.x boilerplate and supplies multiple sub-generators to ease your daily development cycles.

Quick Install

Once you've downloaded the boilerplate and installed all the prerequisites, you're just a few steps away from starting to develop your MEAN application.

The first thing you should do is install the Node.js dependencies. The boilerplate comes pre-bundled with a package.json file that contains the list of modules you need to start your application. To learn more about the modules installed visit the NPM & Package.json section.

To install Node.js dependencies you're going to use npm again. In the application folder run this in the command-line:

$ npm install

This command does a few things:

• First it will install the dependencies needed for the application to run.
• If you're running in a development environment, it will then also install development dependencies needed for testing and running your application.
• Finally, when the install process is over, npm will initiate a bower install command to install all the front-end modules needed for the application

Running Your Application

After the install process is over, you'll be able to run your application using Grunt, just run grunt default task:

$ grunt

Your application should run on port 3000 with the development environment configuration, so in your browser just go to http://localhost:3000

That's it! Your application should be running. To proceed with your development, check the other sections in this documentation. If you encounter any problems, try the Troubleshooting section.

• explore config/env/development.js for development environment configuration options

Running in Production mode

To run your application with production environment configuration, execute grunt as follows:

$ grunt prod

• explore config/env/production.js for production environment configuration options

Running with User Seed

To have default account(s) seeded at runtime:

In Development:

MONGO_SEED=true grunt

It will try to seed the users 'user' and 'admin'. If one of the user already exists, it will display an error message on the console. Just grab the passwords from the console.

In Production:

MONGO_SEED=true grunt prod

This will seed the admin user one time if the user does not already exist. You have to copy the password from the console and save it.

Running with TLS (SSL)

Application will start by default with secure configuration (SSL mode) turned on and listen on port 8443. To run your application in a secure manner you'll need to use OpenSSL and generate a set of self-signed certificates. Unix-based users can use the following command:

$ sh ./scripts/generate-ssl-certs.sh

Windows users can follow instructions found here. After you've generated the key and certificate, place them in the config/sslcerts folder.

Finally, execute grunt's prod task grunt prod

• enable/disable SSL mode in production environment change the secure option in config/env/production.js

Testing Your Application

You can run the full test suite included with MEAN.JS with the test task:

$ grunt test

This will run both the server-side tests (located in the app/tests/ directory) and the client-side tests (located in the public/modules/*/tests/).

To execute only the server tests, run the test:server task:

$ grunt test:server

And to run only the client tests, run the test:client task:

$ grunt test:client

Development and deployment With Docker

• Install Docker

• Install Compose

• Local development and testing with compose:

$ docker-compose up

• Local development and testing with just Docker:

$ docker build -t mean .
$ docker run -p 27017:27017 -d --name db mongo
$ docker run -p 3000:3000 --link db:db_1 mean
$

• To enable live reload, forward port 35729 and mount /app and /public as volumes:

$ docker run -p 3000:3000 -p 35729:35729 -v /Users/mdl/workspace/mean-stack/mean/public:/home/mean/public -v /Users/mdl/workspace/mean-stack/mean/app:/home/mean/app --link db:db_1 mean

Getting Started With MEAN.JS

You have your application running, but there is a lot of stuff to understand. We recommend you go over the Official Documentation. In the docs we'll try to explain both general concepts of MEAN components and give you some guidelines to help you improve your development process. We tried covering as many aspects as possible, and will keep it updated by your request. You can also help us develop and improve the documentation by checking out the gh-pages branch of this repository.

Community

• Use the Official Website to learn about changes and the roadmap.
• Join #meanjs on freenode.
• Discuss it in the new Google Group
• Ping us on Twitter and Facebook

Live Example

Browse the live MEAN.JS example on http://meanjs.herokuapp.com.

Contributing

We welcome pull requests from the community! Just be sure to read the contributing doc to get started.

Deploying To Cloud Foundry

Cloud Foundry is an open source platform-as-a-service (PaaS). The MEANJS project can easily be deployed to any Cloud Foundry instance. The easiest way to deploy the MEANJS project to Cloud Foundry is to use a public hosted instance. The two most popular instances are Pivotal Web Services and IBM Bluemix. Both provide free trials and support pay-as-you-go models for hosting applications in the cloud. After you have an account follow the below steps to deploy MEANJS.

• Install the Cloud Foundry command line tools.
• Now you need to log into Cloud Foundry from the Cloud Foundry command line.
  • If you are using Pivotal Web Services run $ cf login -a api.run.pivotal.io.
  • If you are using IBM Bluemix run $ cf login -a api.ng.bluemix.net.
• Create a Mongo DB service, IBM Bluemix and Pivotal Web Services offer a free MongoLabs service.
  • $ cf create-service mongolab sandbox mean-mongo
• Clone the GitHub repo for MEANJS if you have not already done so
  • $ git clone https://github.com/meanjs/mean.git && cd mean
• Run $ npm install
• Run the Grunt Build task to build the optimized JavaScript and CSS files
  • $ grunt build
• Deploy MEANJS to Cloud Foundry
  • $ cf push

After cf push completes you will see the URL to your running MEANJS application (your URL will be different).

requested state: started
instances: 1/1
usage: 128M x 1 instances
urls: mean-humbler-frappa.mybluemix.net

Open your browser and go to that URL and your should see your MEANJS app running!

Deploying MEANJS To IBM Bluemix

IBM Bluemix is a Cloud Foundry based PaaS. By clicking the button below you can signup for Bluemix and deploy a working copy of MEANJS to the cloud without having to do the steps above.

After the deployment is finished you will be left with a copy of the MEANJS code in your own private Git repo in Bluemix complete with a pre-configured build and deploy pipeline. Just clone the Git repo, make your changes, and commit them back. Once your changes are committed, the build and deploy pipeline will run automatically deploying your changes to Bluemix.

Setting up your local development environment in a docker container

Start your docker container (as local root) with the latest ubuntu image - I've been using ubuntu:wily and run /bin/bash interactively with docker run -i -t --net=host ubuntu:15.10 /bin/bash

now you're 'root' in the container - in this environment run installation (and respond 'Y' to questions) apt-get update apt-get upgrade apt-get install nodejs Dialog git ssh passwd gitk vim lsof rsyslog couchdb x11-apps npm nodejs-legacy ruby sass

create a non root user mkdir /home/<User Name> chown <User Name> /home/<User Name> useradd <User Name> -d /home/<User Name> -p <Password> -s /bin/bash

and edit /etc/ssh/sshd_config and comment out UsePAM to allow non root access to the container without setting up PAM in the container

then start sshd with /usr/sbin/sshd

last step as root is to install the grunt-cli used for dev/test with npm install grunt-cli

Now save your work as local root - outside of the container in a separate shell find the docker container id used to commit your container with docker ps

and commit your container to disk with docker commit <docker container id> wily:node where is the result of the docker ps command

Now logon to the container as user with ssh <User Name>@localhost

and clone the repository git clone https://hub.jazz.net/git/nicolefinnie/4Refugees

then cd into 4Refugees directory and run npm install to install supporting modules

cp 4Refugees;npm install

then edit ./config/env/local.js to configure mongodb access - example `'use strict';

module.exports = { db: { uri: 'mongodb://172.17.93.10:3661/mean-dev', options: { user: '', pass: '' } } }; `

now run grunt to start up the server. Done.

Credits

Inspired by the great work of Madhusudhan Srinivasa The MEAN name was coined by Valeri Karpov

License

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.