Deskeando is a hybrid word for booking a desk which we made up from mixing two languages together, Spanish and English. It is a desk booking app that allows for a safe hybrid working environment.
The main features of the app are:
- Easy way to book a desk to work from the office.
- Users can choose where to sit.
- Ability to add and delete a booking.
- Default assumption: people don't care where they sit, or want to choose when they arrive.
- Target company is medium sized with 10-100 desks.
- Anyone can add and remove bookings for anyone else as it's designed for people who work at the same company and trust each other.
Deskeando is the name of our final project for CodeYourFuture which we developed in 4 weeks. The participants are mentioned below with their linkedIn & Github profiles:
- Benjamin Mehrdad - www.linkedin.com/in/benjamin-mehrdad-306582a2
- Rebeca López-Santos - www.linkedin.com/in/rebeca-lpz-santos/
- Oneil Malik - www.linkedin.com/in/o-neil-malik-a82271123
- Colette Sweeney - www.linkedin.com/in/colette-sweeney-2504b124/
- Sokratis Kladouchos - www.linkedin.com/in/sokratis-kladouchos-02635b208
- Benjamin Mehrdad - https://github.com/Benjamin-GitHub
- Rebeca López-Santos - https://github.com/rebecalsantos
- Oneil Malik - https://github.com/Neil0696
- Colette Sweeney - https://github.com/TheCheekyGit
- Sokratis Kladouchos - https://github.com/socrateskld
- Full stack ES8+ with Babel
- Node LTS support (verified working on 12.x and 14.x LTS releases)
- Express server
- React client with Webpack
- Client-side routing with React Router
- Linting with ESLint and Prettier
- Dev mode (watch modes for client and server, proxy to avoid CORS issues)
- Production build (single deployment artifact, React loaded via CDN)
- Heroku deployment
- Cloud Foundry deployment
- Docker build
- Postgres database with node-postgres
Pick one member of the team to own the repository and pipeline. That person should do the following:
- Click the "Use this template" button above (see GitHub's docs) to create your team repository, select "Include all branches" and name it something appropriate for your project.
- In your new repo, go to "Settings", then "Branches", then switch the default branch to
postgres(optional: you can now delete the oldmainbranch and renamepostgrestomain,masteror whatever else you'd like) - see GitHub's docs again - In your repo, click the "Deploy to Heroku" button at the top of the README and create a Heroku account when prompted.
- Fill in the name of the application, select Europe and then click "Deploy App".
- Once it has deployed successfully, click the "Manage app" button to view the application details.
- Go to the "Deploy" tab, select "Connect to GitHub" and choose your repo.
- Click "Enable automatic deploys".
Whenever you commit to main (or e.g. merge a pull request) it will get automatically deployed!
You should now make sure all of the project team are collaborators on the repository.
Various scripts are provided in the package file, but many are helpers for other scripts; here are the ones you'll commonly use:
dev: starts the frontend and backend in dev mode, with file watching (note that the backend runs on port 3100, and the frontend is proxied to it).lint: runs ESLint and Prettier against all the code in the project.serve: builds and starts the app in production mode locally.
run psql -d cyf -f server\create_tables.sql
use / on MacOS
use \ on windowsOS
While running the dev mode using npm run dev, you can attach the Node debugger to the server process via port 9229.
If you're using VS Code, a debugging configuration is provided for this.
There is also a VS Code debugging configuration for the Chrome debugger, which requires the recommended Chrome extension, for debugging the client application.
If the project handles any kind of Personally Identifiable Information (PII) then make sure the following principles are followed:
- Only collect strictly necessary PII;
- Access to PII should be as restricted as possible;
- Access to PII should only be possible after authentication. Authentication must be done via GitHub. Ad hoc authentication solutions are not allowed;
- Admins must be able to control who has access to the platform and at which levels using only GitHub groups;
- There must be an audit mechanism in place. It is required by law to know who accessed what and when;
- Code must be reviewed by senior developers before being pushed to production;
- APIs must be secure. Make sure we are not handling security on the frontend.
See the guidance in the wiki.