5.2 #31
5.2 #31
Conversation
Fix DB_ROOT_PASS as well [5.1.x]
…docker-compose.override.yml
…nd the docker-compose.override.yml
Fix db root password
Since we are using environment variables like $EDITION in the prepare.d/ scripts, this is required
Update docker-compose.kerberos-proxy.yml
|
|
||
| wire: | ||
| container_name: ${COMPOSE_PROJECT_NAME:-bluespice}-wire | ||
| image: ${BLUESPICE_SERVICE_REPOSITORY}/wire:${VERSION} |
There was a problem hiding this comment.
Would be necessary to first publish docker-bluespice-wire and webservice-wire, as stateless services will be loaded in all cases
There was a problem hiding this comment.
True. We will probably do soon.
|
|
||
| chat: | ||
| environment: | ||
| CHAT_AI_CHAT_SERVICE_URL: http://${COMPOSE_PROJECT_NAME:-bluespice}-ai:8000 |
There was a problem hiding this comment.
for urls in the new chat and ai ymls, would addresses like http://ai:8000 (as we previously used) be sufficient already?
There was a problem hiding this comment.
I noticed that this manipulation might encounter problems, as the compose project name might not be exactly the network name:
when I set name: dev-5.2.x in the main yml, the network I get will become:
✔ Network dev-52x_default Created 0.1s
✔ Container dev-52x-cache Started ...
where the dots are actually stripped away. It would be more robust if we remove the in-URL project names and use the default network routing.
compose/docker-compose.ai.yml
Outdated
| AI__IONOS__BASE_URL: ${IONOS_BASE_URL:-https://openai.inference.de-txl.ionos.com} | ||
|
|
||
| volumes: | ||
| - ${DATADIR}/bluespice/cache/rag:/watch |
There was a problem hiding this comment.
The wiki writes to ${DATADIR}/bluespice/rag so no data is shared betwen wiki and ai
compose/docker-compose.ai.yml
Outdated
| environment: | ||
| NEO4J_AUTH: ${AI_DB_USER:-}/${AI_DB_PASS:-} | ||
| volumes: | ||
| - ${DATA_DIR}/ai-data:/data |
There was a problem hiding this comment.
Is ${DATA_DIR} intentional here? Should this be ${DATADIR} instead?
No description provided.