PLEASE FOLLOW THIS GIT BRANCHING STRATEGY BEFORE ANY COMMIT!!!!!!!: https://www.abtasty.com/blog/git-branching-strategies/

• Install node (this includes NPM) https://nodejs.org/en/download
• Install PostgreSQL (UNTICK PGADMIN FROM INSTALLATION!!) https://www.postgresql.org/download/
• Install latest pgAdmin https://www.pgadmin.org/download/
• Install Postman (app for simulating HTTP methods and database interaction) https://www.postman.com/downloads/

Run terminal as administrator (if on Windows) Otherwise, add 'sudo' before each install (Mac, Linux)

npm install -g nodemon
npm install -g db-migrate
npm install -g db-migrate-pg
npm update -g npm

cd server
npm install
cd ..
cd client
npm install

START the servers:

cd server
npm start
cd ..
cd client
npm start

If there are any errors whatsapp me, there shouldn't be.

run the psql script, login with your postgres account(copy what parameters it tells u to write) once logged in, enter the following commands:

CREATE USER unihive WITH PASSWORD 'unihiveftw';
\du

The user unihive should pop up next to postgres, however, it has no permissions. Let's give it superuser permissions.

ALTER USER unihive SUPERUSER;
\du

unihive user should now have superuser permissions. We will now switch to the unihive user and create the database

SET ROLE unihive;
CREATE DATABASE unihive;
\l

You should now see a new database 'unihive', with the owner being 'unihive', as opposed to postgres

Now it's time to create the tables in the database. open a terminal and run the following command:

cd server
npm run create-db

To insert dummy data into the database, run the following command:

cd server
npm run insert-data

To delete the tables (if need be at any point), run the following command:

cd server
npm run drop-db

Now that the database is set up and created on the local machine, let's set up the environment variables. Check .env.example file in both client and server. Copy what is in .env.example, then in the same directory create a .env file. Paste the example variables into the .env. You can leave the SESSION and the JWT variables the example variables while testing. But in production build we will need to provide the app cryptographically random keys for those variables.

• Set up project integrations

• Invite team members and collaborators
• Create a new merge request
• Automatically close issues from merge requests
• Enable merge request approvals
• Set auto-merge

Use the built-in continuous integration in GitLab.

• Get started with GitLab CI/CD
• Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)
• Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy
• Use pull-based deployments for improved Kubernetes management
• Set up protected environments

First Year Team Project

Our first year team project for the University of Manchester.

Contact @criseda or leave an issue on the repo.

Completed (Minor Updates Ongoing)