No edit summary |
Robert Vogel (talk | contribs) No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 18: | Line 18: | ||
Create a <code>docker-compose.overrides.yml</code> file with the following content: | Create a <code>docker-compose.overrides.yml</code> file with the following content: | ||
<syntaxhighlight lang="yaml"> | <syntaxhighlight lang="yaml"> | ||
x-common-dev: &x-common | |||
image: docker.bluespice.com/bluespice-qa/wiki:latest | |||
volumes: | |||
- ${CODEDIR}:/app/bluespice/w/ | |||
services: | services: | ||
wiki-installer: | wiki-installer: | ||
<<: *x-common | |||
wiki-web: | wiki-web: | ||
<<: *x-common | |||
restart: no | |||
wiki-task: | wiki-task: | ||
<<: *x-common | |||
restart: no | |||
mailhog: | mailhog: | ||
image: mailhog/mailhog | image: mailhog/mailhog | ||
container_name: mailhog | container_name: ${COMPOSE_PROJECT_NAME:-bluespice}-mailhog | ||
environment: | environment: | ||
VIRTUAL_HOST: ${WIKI_HOST} | VIRTUAL_HOST: ${WIKI_HOST} | ||
VIRTUAL_PATH: /_mailhog | VIRTUAL_PATH: /_mailhog/ | ||
VIRTUAL_PORT: 8025 | VIRTUAL_PORT: 8025 | ||
VIRTUAL_DEST: / | VIRTUAL_DEST: / | ||
restart: no | |||
cache: | |||
restart: no | |||
collabpads: | |||
restart: no | |||
collabpads-database: | |||
restart: no | |||
database: | |||
restart: no | |||
diagram: | |||
restart: no | |||
formula: | |||
restart: no | |||
pdf: | |||
restart: no | |||
proxy: | |||
restart: no | |||
search: | |||
restart: no | |||
wire: | |||
restart: no | |||
</syntaxhighlight> | </syntaxhighlight> | ||
| Line 59: | Line 91: | ||
image: bluespice/wiki:dev | image: bluespice/wiki:dev | ||
... | ... | ||
</syntaxhighlight>or you set<blockquote>BLUESPICE_WIKI_IMAGE=bluespice/wiki:dev</blockquote>in your .env | </syntaxhighlight>or you set<blockquote>BLUESPICE_WIKI_IMAGE=bluespice/wiki:dev</blockquote>in your <code>.env</code>-File | ||
Latest revision as of 07:03, 17 March 2026
This page contains information about how to set up a local development environment for BlueSpice.
Local development environment based on bluespice-deploy
A developer can use the default deployment stack and alter is to quickly set up a development environment. To do so, first clone the stack to your local machine and navigate into it:
git clone -b 5.2.x git@github.com:hallowelt/bluespice-deploy.git
cd bluespice-deploy/compose
Create a proper .env file from the .env.sample and alter/add the following lines:
DATADIR=~/workspace/REL1_43-5.2.x/data
CODEDIR=~/workspace/REL1_43-5.2.x/code
SMTP_HOST=mailhog
SMTP_PORT=1025
Create a docker-compose.overrides.yml file with the following content:
x-common-dev: &x-common
image: docker.bluespice.com/bluespice-qa/wiki:latest
volumes:
- ${CODEDIR}:/app/bluespice/w/
services:
wiki-installer:
<<: *x-common
wiki-web:
<<: *x-common
restart: no
wiki-task:
<<: *x-common
restart: no
mailhog:
image: mailhog/mailhog
container_name: ${COMPOSE_PROJECT_NAME:-bluespice}-mailhog
environment:
VIRTUAL_HOST: ${WIKI_HOST}
VIRTUAL_PATH: /_mailhog/
VIRTUAL_PORT: 8025
VIRTUAL_DEST: /
restart: no
cache:
restart: no
collabpads:
restart: no
collabpads-database:
restart: no
database:
restart: no
diagram:
restart: no
formula:
restart: no
pdf:
restart: no
proxy:
restart: no
search:
restart: no
wire:
restart: no
This will make the stack use your local codebase from $CODEDIR and also expose a Mailhog web interface on $Wiki_HOST/_mailhog.
In addition, if you want to work with a custom build of the bluespice/wiki container, you can add an image: entry to the respective services. Example
wiki-installer:
image: bluespice/wiki:dev
...
wiki-web:
image: bluespice/wiki:dev
...
wiki-task:
image: bluespice/wiki:dev
...
or you set
BLUESPICE_WIKI_IMAGE=bluespice/wiki:dev
in your .env-File