docker compose not working #210
-
I spotted 2 problems with the docker compose deployment in the docs: 1/ services:
fief-server:
image: ghcr.io/fief-dev/fief:latest
command: fief run-server --port 8000
# does not work:
# expose:
# - "8000"
# works:
ports:
- "8000:8000"
env_file:
- .env
- 2/ Then I navitagate to The docker compose # Reference: https://docs.fief.dev/self-hosting/environment-variables/
# these params were created with the quickstart procedure
SECRET=XXX
FIEF_CLIENT_ID=XXX
FIEF_CLIENT_SECRET=XXX
ENCRYPTION_KEY=XXX=
PORT=8000
ROOT_DOMAIN=localhost:8000
FIEF_DOMAIN=localhost:8000
FIEF_MAIN_USER_EMAIL=[email protected]
FIEF_MAIN_USER_PASSWORD=Toto*/12345
# Read more: https://docs.fief.dev/self-hosting/deployment/setup-database/
DATABASE_TYPE=POSTGRESQL
DATABASE_HOST=postgres
DATABASE_PORT=5432
DATABASE_USERNAME=fief
DATABASE_PASSWORD=fief
DATABASE_NAME=fief
REDIS_URL=redis://redis:6379 The quickstart docker run env file is: SECRET=XXX
FIEF_CLIENT_ID=XXX
FIEF_CLIENT_SECRET=XXX
ENCRYPTION_KEY=XXX=
PORT=8000
ROOT_DOMAIN=localhost:8000
FIEF_DOMAIN=localhost:8000
FIEF_MAIN_USER_EMAIL=[email protected]
FIEF_MAIN_USER_PASSWORD=Toto*/12345
CSRF_COOKIE_SECURE=False
SESSION_DATA_COOKIE_SECURE=False
USER_LOCALE_COOKIE_SECURE=False
LOGIN_HINT_COOKIE_SECURE=False
LOGIN_SESSION_COOKIE_SECURE=False
REGISTRATION_SESSION_COOKIE_SECURE=False
SESSION_COOKIE_SECURE=False
FIEF_ADMIN_SESSION_COOKIE_SECURE=False What is the reason ? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
Hail, @oscar6echo 👋 I've noticed you shared secret values: For your security, I've taken the liberty to replace them with dummy values. |
Beta Was this translation helpful? Give feedback.
-
Hail, @oscar6echo 👋 Welcome to Fief's kingdom! Our team will get back to you very soon to help. In the meantime, take a minute to star our repository ⭐️ Farewell! |
Beta Was this translation helpful? Give feedback.
-
Hey 👋 Regarding point 1, there was indeed a mistake in the docs. I've fixed it, thanks for catching this 🙏 Regarding point 2, can you check in your DB that the main workspace was correctly created? In particular, look for the |
Beta Was this translation helpful? Give feedback.
-
re point 2: |
Beta Was this translation helpful? Give feedback.
Hey 👋
Regarding point 1, there was indeed a mistake in the docs. I've fixed it, thanks for catching this 🙏
Regarding point 2, can you check in your DB that the main workspace was correctly created? In particular, look for the
fief_clients
table in the workspace schema. Note that, with PostgreSQL, you have the "main" database in thepublic
schema and for each workspace, there is a dedicated schema named after the ID of the workspace. This is where you'll find the data of your workspace.