Renamed api to server. From now on, backend progress should be done in server/server/new folder for your api. Then add the tables (and their names) to server/server/constants.js (follow further instructions in there as well).
Basic structure is the same:
npm run server : to run server
npm start : to run frontend
Added:
npm run deploy-server : deploy backend (AKA: the server folder) to IBM Cloud Foundry
npm run deploy-frontend : deploy frontend (AKA: everything but the server folder) to IBM Cloud Foundry
npm run add-tables : initialize new tables to the database
npm run remove-tables : remove all tables on the database
To deploy to the cloud, you will needed to be added as dev on the project (on the IBM Cloud) by mePull from master and rebase as always
Massive Backend Updates
We are now able to deploy both the backend and frontend to their own separate server on the IBM Cloud Foundry.
Notifications:
Checkout Frontend at: https://ibm-goodtechscholars.mybluemix.net/ Checkout Backend's status at: https://ibm-scholars-server.us-south.cf.appdomain.cloud
Changes:
Renamed
api to server
. From now on, backend progress should be done inserver/server/new folder for your api
. Then add the tables (and their names) toserver/server/constants.js
(follow further instructions in there as well).Basic structure is the same:
npm run server
: to run servernpm start
: to run frontendAdded:
npm run deploy-server
: deploy backend (AKA: theserver
folder) to IBM Cloud Foundrynpm run deploy-frontend
: deploy frontend (AKA: everything but theserver
folder) to IBM Cloud Foundrynpm run add-tables
: initialize new tables to the databasenpm run remove-tables
: remove all tables on the databaseTo deploy to the cloud, you will needed to be added as
dev
on the project (on the IBM Cloud) by me Pull frommaster
andrebase
as always