All the server stuff + deployment

[ahmerb]

Server: this is creating or adapting a server, either programming it yourself or using express and its add-ons

C means you've created a server by minimally adapting the one provided, or closely following a tutorial to set up express B means you've dealt with things like port numbers, URL validation, content negotiation for old browsers, sending redirections to browsers, handling UTF-8 A means you've dealt with things like https and certificates, or web sockets, or cloud hosting, or security issues beyond URL validation, or auto-testing, or cookies, or running under reduced privilege

• [x] set up different NODE_ENV's on server
• [x] deploying to heroku netlify heroku
• [x] https and certificates
• [x] port numbers
• [x] url validation
• [x] content negotiation for old broswers
• [x] sending redirections to browsers
• [ ] handling UTF-8
• [ ] running under reduced privilege

[ahmerb]

Ports Done the following.

Refactor server so start point is the module ./server/index.js and it imports the app from ./app.js, where the app sets up middleware chain etc.

In server.js, we do the following:

• choose port 8080 or port specified by env.
• the normalizePort(val) function simply normalizes the port into a number, string, or false.
• the startServer(serverPort) function starts the server using the specified port number.
• The onError listener function handles server errors but most interestingly is that it would handle a busy-port-error by checking if the port is already in use and would try to restart the application on a different port. So for example, if you try to start the app on port 3000 but that port is already taken, it would try to restart the app on port 3001. If that fails as well, it would try again with port 3002 and so on.
• onListetning logs a message that we have successfully started server on some port

[ahmerb]

Also added morgan logging framework.

[ahmerb]

URL validation Dont' really know what this is. Currently, if a URL doesn't match an api route or home page, we return a 404. Going to mark as done for now. According to this , we just need to ensure that urls start with http:// or https:// server side.

[ahmerb]

Content Negotiation Servers text/html or application/xhtml+xml depending on request headers.

[ahmerb]

Deploy to heroku

Deployed to heroku. See readme. Setup with redis-heroku, jawsdb (mysql), db-migrate scripts etc, postinstall script, set up db and seeded it. See readme / my notes for more info.

Now, on local can run with heroku local and cd frontend && npm run devbuild. To deploy, on master branch only, do git push heroku master. Make sure its working with heroku local first.

[ahmerb]

HTTPS & Certificates Done by @lun3x