aluxian/uninet repository overview

⁠UniNet

Live here: http://uninet.biz/⁠

⁠Intro

UniNet este o retea de socializare creata pentru universitati. Aceasta le ofera studentilor:

• Posibilitate de postare anunturi, notite etc.
• Un feed unde pot urmari postarile celorlalti
• Pagina Conversations unde pot avea conversatii cu alti utilizatori (pentru a intra in conversatie cu cineva: 1) click pe numele persoanei pe pagina de Feed sau 2) cauta-i numele in dreapta pe pagina Conversations)
• Social Events unde studentii pot anunta evenimente precum petreceri, iesiri in oras, intalniri de studiu
• Roommate finder pentru a-si gasi usor colegi de camera, pe baza intereselor comune
• Veteran help center ajutor pentru boboci de la studentii mai mari
• Book Bazaar pentru ca studentii sa poate vinde si cumpara carti intre ei
• Peer Workout: stim cu totii ca studentii sunt lenesi. Se pot ingrasa din cauza stresului si alimentatiei nesanatoase, si nu fac sport. Peer Workout ii ajuta sa nu mai amane inotul, alergatul, sau orice sport in felul urmator: studentii creeaza o intalnire, la o anumita ora, cu un anumit grup de prieteni. Acestea nu pot fi amanate, iar efectul psihologic este de peer-pressure: e mai putin probabil sa nu mai vii cand prietenii tai te asteapta. Nu am implementat inca
• Points Of Interest le arata studentilor punctele de interest din jurul lor, cum ar fi: restaurante, sali de sport, parcuri etc. Nu am implementat inca

⁠Features

• Autentificare locala cu Email si Parola
• Proiect structurat MVC (Model-View-Controller)
• Posibilitate de rulare in cluster Node.js (pentru a rula serverul pe mai multe nuclee ale procesorului)
• Stylesheet-urile scrise in LESS
• HTML-urile scris in Jade
• Design Frontend: Bootstrap 3 cu Material Design
• Angular.js ca frontend framework
• Administrare Cont
• Gravatar
• Detalii Profil
• Schimbare Parola
• Resetare Parola
• Protectie atacuri CSRF
• Baza de date document-based: MongoDB
• Conexiunea dintre backend si frontend pentru pagina de chat realizata prin WebSockets (cu socket.io)

⁠Necesare pentru rulare:

• MongoDB⁠
• Node.js⁠

Note: If you are new to Node or Express, I recommend to watch Node.js and Express 101⁠ screencast by Alex Ford that teaches Node and Express from scratch. Alternatively, here is another great tutorial for complete beginners - Getting Started With Node.js, Express, MongoDB⁠.

⁠Build

# Make sure you have a MongoDB instance running
$ mongod

# Install the NPM dependencies
$ npm install

# Load some faculties in the DB. Necessary only the first time the DB is created.
$ node test-data.js

# Run the app; it'll be available at http://localhost:3000
$ node app.js

⁠Structura proiect

⁠Lista de module folosite

⁠Extra

You need to have a MongoDB server running before launching app.js. You can download MongoDB here⁠, or install it via a package manager. Windows users, read Install MongoDB on Windows⁠.

Tip: If you are always connected to the internet, you could just use MongoLab⁠ or Compose⁠ instead of downloading and installing MongoDB locally. You will only need to update the db property in config/secrets.js.

⁠Deployment

Once you are ready to deploy your app, you will need to create an account with a cloud platform to host it. These are not the only choices, but they are my top picks. From my experience, Heroku is the easiest to get started with, it will automatically restart your Node.js process when it crashes, zero-downtime deployments and custom domain support on free accounts. Additionally, you can create an account with MongoLab and then pick one of the 4 providers below. Again, there are plenty of other choices and you are not limited to just the ones listed below.

⁠1-Step Deployment with Heroku

Note: To install Heroku add-ons your account must be verified.

Note: As an alternative to MongoLab, there is also Compose⁠.

Add these two lines to app.js, just place them anywhere before app.listen():

var IP_ADDRESS = process.env.OPENSHIFT_NODEJS_IP || '127.0.0.1';
var PORT = process.env.OPENSHIFT_NODEJS_PORT || 8080;

Then change app.listen() to:

app.listen(PORT, IP_ADDRESS, function() {
  console.log("✔ Express server listening on port %d in %s mode", PORT, app.settings.env);
});

Add this to package.json, after name and version. This is necessary because, by default, OpenShift looks for server.js file. And by specifying supervisor app.js it will automatically restart the server when node.js process crashes.

"main": "app.js",
"scripts": {
  "start": "supervisor app.js"
},

• Finally, now you can push your code to OpenShift by running git push -f openshift master
• Note: The first time you run this command, you have to pass -f (force) flag because OpenShift creates a dummy server with the welcome page when you create a new Node.js app. Passing -f flag will override everything with your Hackathon Starter project repository. Please do not do git pull as it will create unnecessary merge conflicts.
• And you are done!

• Login to Windows Azure Management Portal⁠
• Click the + NEW button on the bottom left of the portal
• Click WEB SITE, then QUICK CREATE
• Enter a name for URL and select the datacenter REGION for your web site
• Click on CREATE WEB SITE button
• Once the web site status changes to Running, click on the name of the web site to access the Dashboard
• At the bottom right of the Quickstart page, select Set up a deployment from source control
• Select Local Git repository from the list, and then click the arrow
• To enable Git publishing, Azure will ask you to create a user name and password
• Once the Git repository is ready, you will be presented with a GIT URL
• Inside your Hackathon Starter directory, run git remote add azure [Azure Git URL]
• To push your changes simply run git push azure master
• Note: You will be prompted for the password you created earlier
• On Deployments tab of your Windows Azure Web Site, you will see the deployment history

• Go to Codename: Bluemix⁠ to signup for the free trial, or login with your IBM id
• Install Cloud Foundry CLI⁠
• Navigate to your hackathon-starter directory and then run cf push [your-app-name] -m 512m command to deploy the application
• Note: You must specify a unique application name in place of [your-app-name]
• Run cf create-service mongodb 100 [your-service-name] to create a MongoDB service⁠
• Run cf bind-service [your-app-name] [your-service-name] to associate your application with a service created above
• Run cf files [your-app-name] logs/env.log to see the *environment variables created for MongoDB.
• Copy the MongoDB URI that should look something like the following: mongodb://68638358-a3c6-42a1-bae9-645b607d55e8:[email protected]:10123/db
• Then set it as an environment variable for your application by running cf set-env [your-app-name] MONGODB [your-mongodb-uri]
• Run cf restart [your-app-name] for the changes to take effect.
• Visit your starter app at http://[your-app-name].ng.bluemix.net
• Done!

Note: Alternative directions, including how to setup the project with a DevOps pipeline are available at http://ibm.biz/hackstart⁠. A longer version of these instructions with screenshots is available at http://ibm.biz/hackstart2⁠. Also, be sure to check out the Jump-start your hackathon efforts with DevOps Services and Bluemix⁠ video.