[major].[minor].[patch]
versioning mirrors the upstream product version, so it's easy to pull deploy a specific version, should your application require it.&&
to concatenate the two commands which will work under *unix. If you are in windows, replace &&
with ;
in Powershell, replace &&
with &
in Cmd, or run the two commands separatelyhttp://[docker machine ip]:8080
, you will be directed to configure your ContentBox installation using the ContentBox Installer. That easy! Boom!run
command produces an image which is self-contained, and would be destroyed when the container is stopped. If we wanted to run a version in production, we would need to persist, at the very minimum, the database and your custom assets (widgets, modules, themes, and media library). In order to do this, we need to mount those resources into the Docker host file system.express
H2 database is stored at /data/contentbox/db
inside the container. In addition, the custom content module which contains your custom themes, widgets, modules, and media library are stored under /app/modules_app/contentbox-custom
./app/includes/shared/media
and the contentbox-custom module did not exist./data/contentbox/db
/app/modules_app/contentbox-custom
/app/includes/shared/media
INSTALL
in place. The H2 database and uploads will be persisted and the installer will be removed automatically on container start.INSTALL
Setting CaveatsCFCONFIG
environment variable which points to a file containing your engine configuration, including data sources.contentbox
.DB_DRIVER
configuration - which may be used for Adobe Coldfusion serversDB_CLASS
configuration - which configures a datasource by JDBC driver and connection string (Both Adobe and Lucee)run
command, configuring a MySQL database would be executed like so:DB_DRIVER
syntax for Adobe Coldfusion, an example run
command would be:EXPRESS=true
- Uses an H2, in-memory database. Useful for very small sites or for testing the image. See http://www.h2database.com/html/main.html​INSTALL=true
(alias: INSTALLER
) - Adds the installer module at runtime, to assist in configuring your installation. You would omit this from your run
command, once your database has been configuredBE=true
- Uses the bleeding edge snapshot of the ContentBox CMS, else we will defer to the latest stable version of ContentBox.HEALTHCHECK_URI
- Specifies the URI endpoint for container health checks. By default, this is set http://127.0.0.1:${PORT}/
at 30s intervals with 5 retries and a timeout of 60sFWREINIT_PW
- Allows you to specify the reinit password for the ColdBox frameworkSESSION_STORAGE
- Allows the customization of session storage. Allows any valid this.sessionStorage
value, available in Application.cfc. By default, it will use the JDBC connection to store your sessions in your database of choice.DISTRIBUTED_CACHE
- Allows you to specify a CacheBox cache region for distributing ContentBox content, flash messages, cache storage, RSS feeds, sitemaps, and settings. There are only three cache regions defined in this image: default
, template
and jdbc
. jdbc
is the default cache that will distribute your data, default
and template
are in-memory caches. Please see the distributed caching section below to see how to register more caches.H2_DIR
- Allows you to specify a custom directory path for your H2 database. By convention, this is set to /data/contentbox/db
within the containercontentbox_default_*
- All Contentbox "Geek Settings" may be provided as environment variables, allowing granular control of your ContentBox settings.ORM_SECONDARY_CACHE
- If true
it will activate the ORM secondary cash to the ehcache
provider. By default, it is turned off.ORM_DIALECT
- You can choose the specific ORM dialect if needed, if not we will try to auto-detect it for you.HEADLESS=false
- If true
then this image will not publish an Admin module, just the core, REST and UI modules.SESSION_STORAGE
environment variable to switch the connection to any backend you like.jdbc
CacheBox cache region that will be used to distribute settings, sessions, flash data, content, RSS feeds, sitemaps, etc. This means that out-of-the-box, your ContentBox containers can use the database to distribute its content within a swarm or set of services. However, if you would like to use your own CacheBox providers or a more sophisticated distributed cache like Redis or Couchbase, you can.HEALTHCHECK_URI
environment variable. By default, this is set http://127.0.0.1:${PORT}/
at 30s intervals with 5 retries and a timeout of 60s.