immich/docker/.env.test

# Database
DB_HOSTNAME=immich_postgres_test
DB_USERNAME=postgres
DB_PASSWORD=postgres
DB_DATABASE_NAME=e2e_test

# Redis
REDIS_HOSTNAME=immich_redis_test

# Upload File Config
UPLOAD_LOCATION=./upload

# JWT SECRET
JWT_SECRET=randomstringthatissolongandpowerfulthatnoonecanguess

# MAPBOX
## ENABLE_MAPBOX is either true of false -> if true, you have to provide MAPBOX_KEY
ENABLE_MAPBOX=false

# WEB
MAPBOX_KEY=
VITE_SERVER_ENDPOINT=http://localhost:2283/api
Add e2e testing setup (#163) * Setup e2e testing * Add user e2e tests * Rename database host env variable to DB_HOST * Force push (try to recover DB_HOST env) * Rename db host env variable to `DB_HOSTNAME` * Remove unnecessary `initDb` from test-utils The current database.config is running the migrations: `migrationsRun: true` 2022-05-20 01:30:47 +02:00			`# Database`
Fix user e2e tests (#194) * WIP fix user e2e tests The e2e tests still don't seem to work due to migrations not running. Changes: - update user.e2e tests to use new `userService.createUser` method - fix server `typeorm` command to use ORM config - update make test-e2e to re-create database volume every time - add User DTO - update auth.service and user.service to use User DTO - update CreateUserDto making optional properties that are optional * Fix migrations - add missing `.ts` extension to migrations path - update user e2e test for the new returned User resource 2022-06-06 18:16:03 +02:00			`DB_HOSTNAME=immich_postgres_test`
Add e2e testing setup (#163) * Setup e2e testing * Add user e2e tests * Rename database host env variable to DB_HOST * Force push (try to recover DB_HOST env) * Rename db host env variable to `DB_HOSTNAME` * Remove unnecessary `initDb` from test-utils The current database.config is running the migrations: `migrationsRun: true` 2022-05-20 01:30:47 +02:00			`DB_USERNAME=postgres`
			`DB_PASSWORD=postgres`
			`DB_DATABASE_NAME=e2e_test`

Fix user e2e tests (#194) * WIP fix user e2e tests The e2e tests still don't seem to work due to migrations not running. Changes: - update user.e2e tests to use new `userService.createUser` method - fix server `typeorm` command to use ORM config - update make test-e2e to re-create database volume every time - add User DTO - update auth.service and user.service to use User DTO - update CreateUserDto making optional properties that are optional * Fix migrations - add missing `.ts` extension to migrations path - update user e2e test for the new returned User resource 2022-06-06 18:16:03 +02:00			`# Redis`
			`REDIS_HOSTNAME=immich_redis_test`

Add e2e testing setup (#163) * Setup e2e testing * Add user e2e tests * Rename database host env variable to DB_HOST * Force push (try to recover DB_HOST env) * Rename db host env variable to `DB_HOSTNAME` * Remove unnecessary `initDb` from test-utils The current database.config is running the migrations: `migrationsRun: true` 2022-05-20 01:30:47 +02:00			`# Upload File Config`
			`UPLOAD_LOCATION=./upload`

			`# JWT SECRET`
			`JWT_SECRET=randomstringthatissolongandpowerfulthatnoonecanguess`

			`# MAPBOX`
			`## ENABLE_MAPBOX is either true of false -> if true, you have to provide MAPBOX_KEY`
			`ENABLE_MAPBOX=false`
Fix user e2e tests (#194) * WIP fix user e2e tests The e2e tests still don't seem to work due to migrations not running. Changes: - update user.e2e tests to use new `userService.createUser` method - fix server `typeorm` command to use ORM config - update make test-e2e to re-create database volume every time - add User DTO - update auth.service and user.service to use User DTO - update CreateUserDto making optional properties that are optional * Fix migrations - add missing `.ts` extension to migrations path - update user e2e test for the new returned User resource 2022-06-06 18:16:03 +02:00
			`# WEB`
			`MAPBOX_KEY=`
chore: improve default setup (#234) * chore: remove UPLOAD_LOCATION as it isn't used in the server * docker: remove network in docker compose as docker creates one by default * nginx: update reverse proxy to put web at root and api at /api * docker: remove unneeded exposed ports and docker network Align dev setup with prod, but with ports exposed for direct connection Most communication between services happens on the internal network, so we don't need to expose all these services. With the nginx changes, the api and web panel are both server through the reverse proxy on / for web and /api for the API. The only service that should expose ports is nginx as that is the entrypoint to the application. * chore: remove CORS now we serve the api on /api in the default setup * docs: update README.md to include /api * Fixed docket-compose file for dev environment and websocket on web and mobile Co-authored-by: Alex Tran <alex.tran1502@gmail.com> 2022-06-24 05:18:50 +02:00			`VITE_SERVER_ENDPOINT=http://localhost:2283/api`