🚀 Rewrite of maintenance.newtelco.de with a modern stack.
- Gmail API - Create maintenance entries directly from incoming Emails
- Google Translate API - Translate mails directly in the read preview
- Google Calendar API - Create calendar entries from the application
- Clean, professional, responsive UI
- WYSIWYG Editor
- Export data to CSV
- LogRocket error tracking
- Keyboard Shortcuts
There is an API sister project to this one located in the following repo: (newtelco/api-maintenance
). This must be running during dev / prod to get anything going.
- MySQL DB
- G Suite Service Account .json credential file
- SMTP Server
git clone https://github.com/newtelco/next-maintenance
cd next-maintenance && npm i
npm run dev
This will then start the frontend on port 4000
git clone https://github.com/newtelco/api-maintenance
cd api-maintenance && npm i
npm run dev
This will then start the backend on port 4100
It is currently setup so that the host is dynamic, you can reverse proxy it out under any domain, however it is important that wherever you reverse proxy out the frontend, the backend must be under the location /v1/api
of the same domain. So, for example, if you have the frontend available at myapplication.com
, then the backend must be available at myapplication.com/v1/api
. An example nginx config file is included in the api repo.
Internal Application used by NewTelco GmbH