No description
| .vscode | ||
| nginx | ||
| public | ||
| src | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .releaserc | ||
| dev-entrypoint.sh | ||
| docker-entrypoint.sh | ||
| Dockerfile | ||
| env.d.ts | ||
| index.html | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| update-version.sh | ||
| vite.config.ts | ||
ScheduleTogether Frontend
Frontend for ScheduleTogether.
Testing:
npm run dev
In dev mode, the interface is exposed on http://localhost:5173/.
Note: you need to have the backend running in order to properly test the frontend. Dummy backend for development might be a focus in the future.
Building:
npm run build
Note: The recommended way of running ScheduleTogether is with the docker-compose file found here. It includes the frontend, backend and a database. If you want to run each service separately, remember to create a .env file. Example file for Frontend can be found here. If you won't be running in docker, you should instead edit the config.json file.