mirror of
https://github.com/IT4Change/Ocelot-Social.git
synced 2025-12-13 07:45:56 +00:00
10418f061b
* Use `production` docker images for cypress tests. As one of our contributors pointed out: It is bad practice to end-to-end test sth. else than the actual production images. * Have a dedicated `docker-compose.travis-integration.yml` to test backend integration tests. The backend *needs* a database when doing integration tests. So there is no way around using docker-compose. But we could stop using the `build-and-test` stage when we do cypress tests. * Remove a couple of unused ports and DRY `docker-compose.override.yml` * Build and tag all images first and then run `docker-compose .. up` - I hope this will not rebuild the image. * Reduce docker image size
Webapp
Installation
# install all dependencies
$ yarn install
Copy:
cp .env.template .env
cp cypress.env.template.json cypress.env.json
Configure the files according to your needs and your local setup.
Build for Development
# serve with hot reload at localhost:3000
$ yarn dev
Build for Production
# build for production and launch server
$ yarn build
$ yarn start
Styleguide
All reusable Components for example avatar should be done inside the Nitro-Styleguide repository.
More information can be found here: https://github.com/Human-Connection/Nitro-Styleguide
If you need to change something in the styleguide and want to see the effects on the frontend immediately, then we have you covered. You need to clone the styleguide to the parent directory ../Nitro-Styleguide and run yarn && yarn run dev. After that you run yarn run dev:styleguide instead of yarn run dev and you will see your changes reflected inside the frontend!