This forum has moved to a new location and is in read-only mode. Please visit talk.octobercms.com to access the new location.

Josh
Josh

I just wanted to post here to let folks know that I've been working on a docker container for October. It supports either linked databases (both MySQL/MariaDB and Postgres) or SQLite for standalone. I've also set it up so that you can configure most of the rest of October through environment variables.

For a quickstart dev container, you can just run:

docker run -p 8080:80 -d dragontek/octobercms

And visit the site at http://localhost:8080 (for Windows or Mac, with Docker Toolbox, it's more likely http://192.168.99.100:8080)

For more details, you can check it out here: https://hub.docker.com/r/dragontek/octobercms/

My original goal was to be able to support scalability and high availability by using AWS for uploads and media in filesystems, but went ahead and continued on with the rest of the configuration files to make it more flexible. The idea, though, is that you'd put HAProxy (or NGINX) in front of one or more October containers and one of the supported databases behind.

Thanks to the October team for a great CMS!

Last updated

one800higgins
one800higgins

I'm trying to wrap my head around using this so I can automate a deployment with Elastic Beanstalk. You can easily spin up October with this, but what about managing it? Installing plugins, adding private plugins, etc? Do you have thoughts on that? It may just be that I'm missing something obvious here.

Josh
Josh

This has been one of my major hurdles that I've yet to cross. This image currently works well on a single node where all theme and plugin development are done from within the backend itself (or imported from a local dev environment), but when it comes to more than one node, it gets more difficult.

As mentioned above, the first step was getting media and uploads to use S3, but automating the installation of themes and plugins on each node is still problematic. One thought that I had was to use a shared data volume container across multiple nodes, but that seems like it would still be a bottleneck. Another would be to use an environment variable to link the containers to an October project ID, but as far as I know you can only use public themes and plugins. A final thought would be to use git to pull these things from a repo, but then I'd need to be able to authenticate to private repos.

I'm open to ideas, and you definitely haven't missed anything obvious here :) (Or we both have)

Thank you, Josh

Josh
Josh

Updated image now supports ONBUILD tag as well as plugin and theme installation (from the Marketplace).

This should solve the deployment issue, but does change the workflow a bit. Essentially, you'd clone the October repo, and add a Dockerfile with just a single line:

FROM dragontek/octobercms:onbuild

Then you can do development locally, and when you're ready to deploy, run:

docker build -t my-october-image .

Also, if you need to install themes or plugins from the Marketplace, you can add an environment variable:

docker run -e OCTOBER_PLUGINS="RainLab.Blog;RainLab.GoogleAnalytics" -p 8080:80 -d my-october-image

I hope this helps, please let me know.

Thank you, Josh

Last updated

Josh
Josh

Updated image for latest Stable release.

Thank you, Josh

Josh
Josh

Update image for PHP 7.0 support.

Thank you, Josh

web.konception34745
web.konception34745

Hi all, I'm looking for docker image working on Ubuntu last version (18.04) with :

  • Nginx
  • PHP last version (7.1 / 7.2) PHP-FPM
  • Mariadb
  • Octobercms (last release)

typically a docker image with this :

or with this :

or with this :

Thx

Last updated

1-7 of 7

You cannot edit posts or make replies: the forum has moved to talk.octobercms.com.