close

Filter

Blueprint Developer Manual / Version 2104
Table Of Contents

If you do not want to start the whole stack, you can start only the required components.

  1. List all services

    cd global/deployment/docker
    docker-compose config --services
  2. From the list of services make a space separated list of services you want to start and put them in an environment variable, that is, for example:

    export DC_DB="mongodb mysql"
    export DC_MANAGEMWENT_BACKEND="${DC_DB} solr content-management-server \
           workflow-server content-feeder caefeeder-preview user-changes \
           elastic-worker studio-server"
    export DC_PUBLICATION_BACKEND="master-live-server caefeeder-live"
    export DC_PREVIEW="cae-preview studio-client traefik"
    export DC_LIVE="cae-live" export DC_CONTENT=management-tools
  3. Now you can use this to start what you most often need:

    docker-compose up -d ${DC_DB} ${DC_MANAGEMENT_BACKEND} ${DC_CONTENT} overview

    overview is not a docker command, but the overview service with all the links.

A different approach is to freeze the setup and then cut out everything you need.

docker-compose config > docker-compose.yml

You can then remove everything you don’t want. docker-compose.yml is ignored by Git with the default .gitignore file. You only have to make sure, that in your .env file

COMPOSE_FILE=docker-compose.yml

is set, otherwise the file won’t be loaded.

Of course. there are a lot of toggles for your convenience:

  • JAVA_DEBUG - default ports XXX06 for JDWP

  • FORCE_REIMPORT_CONTENT - once imported, the content won’t reimport unless forced

  • SKIP_CONTENT - same as not running the management-tools container

Was this article useful?

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.