This repository has been archived by the owner on Jun 28, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment
James Bennett edited this page Feb 28, 2019
·
2 revisions
We decided to use Heroku as the platform to deploy our app. The rationale being:
- Positive previous experience (having deployed web apps through Heroku before)
- Free tier (we can fully develop and test our live web app without paying)
- No need for integrated database services.
- Other candidates included Amazon Web Services (AWS), but much of the feature set provided by AWS would be surplus to requirements. e.g. close integration with DynamoDB wouldn't be needed as our database is implemented through Mongo and mLab.
The temporary free version of our live web app is created at https://office-jukebox.herokuapp.com/
.
As such, what has previously been located under localhost:3000
is now located under the new URI.
This impacts the environment variables within our Node.js codebase,which have to be altered to point towards the new deployment.
Furthermore, our Spotify API integration must be updated to include the relevant 'callback'.
Group 14 - BJSS Office Jukebox
- Directory Structure
- Requirements
- Architecture
- Specification
- User Interface
- Deployment
-
Front End
- Components
- Pages
- Startup
- Alexa
- Static (assets)
-
Back End
-
Functions