Portainer Templates logo

Portainer Templates

Silverstripe Silverstripe

Stack

CMS

Silverstripe CMS is a free and open source Content Management System (CMS) and Framework for creating and maintaining websites and web applications.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

silverstripe

Configuration

Image
brettt89/silverstripe-web:8.1-apache
Volumes
/var/www/html : /portainer/Files/AppData/Config/silverstripe
Env vars
DOCUMENT_ROOT=/var/www/html/publicSS_TRUSTED_PROXY_IPS=*SS_ENVIRONMENT_TYPE=devSS_DATABASE_SERVER=databaseSS_DATABASE_NAME=SS_mysiteSS_DATABASE_USERNAME=rootSS_DATABASE_PASSWORD=SS_DEFAULT_ADMIN_USERNAME=adminSS_DEFAULT_ADMIN_PASSWORD=password

Image details

Pulls: 336k
User: brettt89
Created: Apr 16, 2017
Updated: 6 months ago
Status: active

silverstripe-db

Configuration

Image
mysql:5.7
Volumes
/var/lib/mysql : /portainer/Files/AppData/Config/silverstripe/db-data
Env vars
MYSQL_ALLOW_EMPTY_PASSWORD=yes

Image details

Pulls: 5.1B
User: stackbrew
Created: Jun 05, 2014
Updated: 19 days ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying Silverstripe

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Silverstripe, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  silverstripe:
    image: brettt89/silverstripe-web:8.1-apache
    volumes:
       - /portainer/Files/AppData/Config/silverstripe:/var/www/html
    depends_on:
       - silverstripe-db
    environment:
       - DOCUMENT_ROOT=/var/www/html/public
       - SS_TRUSTED_PROXY_IPS=*
       - SS_ENVIRONMENT_TYPE=dev
       - SS_DATABASE_SERVER=database
       - SS_DATABASE_NAME=SS_mysite
       - SS_DATABASE_USERNAME=root
       - SS_DATABASE_PASSWORD=
       - SS_DEFAULT_ADMIN_USERNAME=admin
       - SS_DEFAULT_ADMIN_PASSWORD=password
  silverstripe-db:
    image: mysql:5.7
    environment:
       - MYSQL_ALLOW_EMPTY_PASSWORD=yes
    volumes:
       - /portainer/Files/AppData/Config/silverstripe/db-data:/var/lib/mysql
volumes:
     db-data:

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/silverstripe.yml up -d

More install options in our documentation.

Container Documentation

silverstripe Documentation

Silverstripe - PHP Docker environments

silverstripe-db Documentation

MySQL is a widely used, open-source relational database management system (RDBMS).

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/silverstripe (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull brettt89/silverstripe-web:8.1-apache

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Required settings are blank

SS_DATABASE_PASSWORD has no default value, and silverstripe may crash or misbehave if left empty.

  • Fill it in on the deploy screen before hitting deploy.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Silverstripe is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • silverstripe runs brettt89/silverstripe-web:8.1-apache, starts after silverstripe-db
  • silverstripe-db runs mysql:5.7

Volumes

A volume is where Silverstripe keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/www/html from /portainer/Files/AppData/Config/silverstripe on the host
  • /var/lib/mysql from /portainer/Files/AppData/Config/silverstripe/db-data on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Silverstripe takes 10 of them, and one needs a value before it'll start properly:

  • DOCUMENT_ROOT, defaults to /var/www/html/public
  • SS_TRUSTED_PROXY_IPS, defaults to *
  • SS_ENVIRONMENT_TYPE, defaults to dev
  • SS_DATABASE_SERVER, defaults to database
  • SS_DATABASE_NAME, defaults to SS_mysite
  • SS_DATABASE_USERNAME, defaults to root
  • SS_DATABASE_PASSWORD, needs a value
  • SS_DEFAULT_ADMIN_USERNAME, defaults to admin
  • SS_DEFAULT_ADMIN_PASSWORD, defaults to password
  • MYSQL_ALLOW_EMPTY_PASSWORD, defaults to yes

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like silverstripe) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Silverstripe up. Add the template list to Portainer once, then deploying Silverstripe is a click rather than a wall of config.