Open Content
Docs homeNaviga web
  • Introduction
  • Overview
  • Key features
  • Meta data standards
  • Architecture
  • Open Content API
  • Headless and end-to-end CMS workflows
  • Use and explore
    • How does it work
    • Open Content Docker
    • OC REST API
    • Event logs
    • Replication
    • Open Content Notifier
    • New JSON API:s - CCA and Duppy
    • Terminology: Other backend services
    • Lab: upload
      • Curl for object upload
      • Environment
      • Lab 0: Configuration
      • Lab 1: Concept upload
      • Lab 2: Image upload
      • Lab 3: Article Upload
      • Lab 4: Search
      • Lab 5: Delete objects
      • Lab 6: Event sourcing using event log
  • Releases
    • Release documentation and admin guides
      • Open Content 2.3
    • New in OC 3.0 (draft)
      • Removed features in OC 3.0
  • XLibris Archive
    • Archive everything you ever created or published
    • Import content to XLibris
Powered by GitBook
On this page
Export as PDF
  1. Use and explore

Open Content Docker

How to run Open Content in Docker on my own computer.

The Docker images for Open Content are primarily for development purposes, not production. So if you are a developer looking for how to start Open Content locally for integration testing or trying things out, then this is for you.

# create a directory where to work, in home oc-lab 
cd 
mkdir oc-lab
cd oc-lab
# Download the zip file from S3 
curl -s https://s3-eu-west-1.amazonaws.com/open-content-artifacts/opencontent-docker-configs.zip  \  
--output opencontent-docker-configs.zip
# Unzip 
unzip opencontent-docker-configs.zip
# Go to directory
cd opencontent-docker-lab

Start Open Content

docker-compose -f docker-compose-lab.yml up --detach

Wait until all containers are downloaded and started. Now there is an empty Open Content without configuration or content.

Logging

docker-compose -f docker-compose-lab.yml logs -f wildfly

Open Content UI

Below is the menu for the Open Content admin UI.

Configure Open Content

curl -u admin:admin -d name=OpenContent -d path=/tmp http://localhost:8080/opencontent/admin/storage​

Open Content configuration in this setup is done using a local copy of our Bitbucket repository for configuration. Use the Open Content admin UI to inspect the detailed settings for the different configuration options.

Go to the opencontent-configuration directory where the configure.sh script is

cd ../opencontent-configs/scripts

Configure Open Content for public use

./configure.sh \
http://admin:admin@localhost:8080/opencontent \
public

Configure Open Content for public and app use

./configure.sh \
http://admin:admin@localhost:8080/opencontent \
public-app

Configure Open Content for editorial use

./configure.sh \
http://admin:admin@localhost:8080/opencontent \
editorial

Activation of the configuration

curl -u admin:admin \
-X POST "http://localhost:8080/opencontent/admin/configuration/activate" \
-H "accept: */*" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "reason=configured from script&name=$(whoami)"
PreviousHow does it workNextOC REST API

Last updated 5 years ago

Configuration is done using the admin UI or the admin API. The UI can be found here .

Open Content admin UI menu

The first thing that has to be configured is storage. This can either be done in the UI at or with this curl command:

http://localhost/admin
http://localhost/admin