week-8-AGIL

Team AGILé

Installation instructions

1. clone the repo git clone https://github.com/fac18/week-8-AGIL.git
2. run npm i
3. set up a .env in your root folder with DATABASE_URL and TEST_DATABASE_URL paths (ask us!)
4. check our tests with npm run test

Or test database and server separately with:

• npm run testdb
• npm run testserver

5. start the server with npm start and go to localhost:1235!

Tests

Project

Build a server-rendered full-stack app

.... FAC 18 Yearbook!

Task

• Build an app using the Express framework
• Use a PostgreSQL database to store and retrieve your data
• Use the retrieved data to populate a Handlebars template for server-side rendering to be displayed on the front-end

User Stories

As a member of FAC, I would like to:

• see a gallery of fellow FACsters
• submit a profile with details about myself
• see the details of other FAC friends
• delete my profile if I so choose (GDPR!!)
• click on a link and be directed to the FAC projects gallery

Goals

✅ The primary aim of this project is to get comfortable with setting up an Express server and

✅ to discover the awesomeness of Handlebars! Spend time considering how to format your layouts, partials and helper functions.

✅ Include tests and set up code coverage

🤪 We expect to see unit tests of pure functions

✅ integration tests of your server routes

✅ including tests for errors such as 404

✅ You should write tests for your database and use a separate test database and build script

✅ Use Heroku or a similar service to host the app and the database

✅ Try to include ES6 syntax on the server

Schema

Cohorts table not currently in use

We learnt:

• In express this line means you don't need to ref public in the route for your images or css files coming from the html file because it's already done!

app.use(express.static(path.join(__dirname, "..", "public")));

• Don't change names of things! We changed some column names part way through (eg rename 'name' in the users table to 'user_name', and then had to go scouting for other instances all across different files

• Server tests wouldn't finish, causing Travis to fail. Fixed like this:

  app.close();
  t.end();
});

• THERE ARE TWO VERSIONS OF TRAVIS-CI!!!!! travis-ci.org and travis-ci.com. We had set ourselves up on both but only put env variables in one, and kept seeing conflicting messages!

• You can use Ctrl + Shift + F in VSCode to search across all files (to find those pesky old console logs!)