Skip to main content
SimilarExport ZIP
100%

Docker Compose for Omeka-S (forked from https://raw.githubusercontent.com/dodeeric/omeka-s-docker/master/docker-compose.yml) with MySQL

✓ Published0🌍 Public
CCliffordAnderson
Last edited Aug 8, 2019
Created on Aug 8, 2019

This example visualizes a Docker Compose configuration for running Omeka-S, a web publishing platform, alongside MySQL and phpMyAdmin. The code defines three interconnected services—`mysql`, `pma`, and `omeka`—using the `mysql:latest`, `phpmyadmin/phpmyadmin:latest`, and `dodeeric/omeka-s:latest` images respectively. It shows how named volumes (`mysql`, `omeka`) persist data, while a custom network (`network1`) enables service communication. The YAML file explicitly links the database and admin interface to the Omeka-S container, with port mappings (`80:80` and `8080:80`) exposing the web services.

AI-generated description

Similar vizzes

Loading thumbnail…

Omeka-S on Debian w/Docker Compose

This example shows a complete setup for running Omeka-S, a digital-archive platform, on Debian using Docker Compose. The code first installs Docker and Docker Compose, then clones the `omeka-s-docker` repository and launches the containerized application with `sudo docker-compose up -d`. It relies on the Docker command-line interface and the Docker Compose tool, specifically using `docker-compose` to orchestrate the service. The gist does not include a data visualization; instead, it documents a server-deployment workflow, with the visible render being the terminal output from the install script and container startup. No charting or data-rendering libraries appear in this code.

CCliffordAnderson
79% match
Loading thumbnail…

docker compose sample

This example shows a multi-service Docker Compose setup for local development, defining a main application service along with MySQL and Adminer containers. The main service builds from a local context with a development target, mounts the current directory as a volume while preserving the container’s node_modules, exposes port 9229 for debugging, runs `npm run start:dev`, and loads environment variables from a `.env` file. The MySQL service uses the `mysql:latest` image with a native password authentication plugin, sets a root password, and persists data in a named volume. Adminer provides a web-based database client on port 8080, with all services connected via a custom `webnet` network.

66ewis
72% match
Loading thumbnail…

Config to Run nest and mysql

This example shows a Docker Compose configuration that sets up a NestJS application with a MySQL database and an Adminer interface for database management. The `main` service builds a development container with mounted source code and hot-reloading via `npm run start:dev`, while the `mysql` service uses the official MySQL image with a root password and persistent storage through a named volume. Adminer runs on port 8080 and connects to the MySQL container. The configuration uses Docker Compose’s networking and volume APIs to link services and preserve data across container restarts.

66ewis
68% match
Loading thumbnail…

docker compose for timescaledb and postgresql-adaptor

This example shows a Docker Compose setup that runs TimescaleDB and the Timescale Prometheus adapter as two linked services for time-series data storage and querying. The YAML configuration defines a `timescaledb` service using the `timescale/timescaledb:latest-pg12` image with host path mapping to `/data/timescaledb`, and a `prometheus_postgresql_adapter` service using `timescale/timescale-prometheus:latest` that connects to the database via environment variables. Port mappings expose PostgreSQL on 5432 and the adapter's telemetry endpoint on 9201. The adapter is configured with retry logic and debug logging through `TS_PROM_` prefixed environment variables.

JJastor11
58% match
Loading thumbnail…

Gist 3d7ff1d83fb2177cedceded587ff4aca

This example presents a setup guide for a Docker-based Node.js workshop, illustrating how to launch a project from a Bitbucket-hosted configuration. It shows the command sequence, starting with copying a `docker-compose.yml` file from the provided URL and then running `docker compose up --build` to construct and start the container image. The visualization focuses on the workflow steps, highlighting the use of Docker Compose for service orchestration and image building. The interface displays the copied configuration link alongside the terminal command, making the process explicit for users. No additional data or rendering occurs beyond these instructional elements.

MMistyBlunch
58% match
Loading thumbnail…

Docker Image for Neo4j with APOC and Spatial plugins

This example shows a Dockerfile that extends the official Neo4j image to include the APOC procedure library and the Neo4j Spatial plugin. The build process uses `curl` to download the APOC release JAR from GitHub and the spatial plugin from a Maven repository, then moves both into the plugins directory via shell commands. It relies on the `neo4j:latest` base image, configures symbolic links, and exposes ports 7474, 7473, and 7687 for HTTP, HTTPS, and Bolt access. The final `CMD` launches Neo4j directly.

CCliffordAnderson
56% match
Loading thumbnail…

Gist 20b9219bcfa5ee87411a30118d3b6163

This example shows a shell script that automates the deployment of a Dockerized application on a fresh Ubuntu server. The script installs Docker and Docker Compose, creates a project directory, and copies a `docker-compose.yml` file into it. It then sets up a systemd service to run the compose file on boot and starts the application. The code uses `curl` to fetch remote files, `usermod` for user permissions, and `systemctl` to enable the service, with the actual container orchestration handled by `docker-compose` and `docker` commands.

CCliffordAnderson
54% match
Loading thumbnail…

BaseX Docker with BasexWeb file mount

This example demonstrates how to launch a BaseX HTTP server within a Docker container, mounting local directories for both database storage and web application files. The `docker run` command configures the container with the `basex/basexhttp:latest` image, exposing ports 1984 and 8984 for client and HTTP access. It uses volume flags (`--volume`) to bind the host’s `~/BaseXData` and `~/BaseXWeb` directories to `/srv/BaseXData` and `/srv/BaseXWeb` inside the container, enabling persistent data storage and direct serving of web content. The setup runs interactively with the `-ti` flag, linking host filesystem paths to the server’s runtime environment.

CCliffordAnderson
52% match