Docker Image for Neo4j with APOC and Spatial plugins

100%

Docker Image for Neo4j with APOC and Spatial plugins

✓ Published0🌍 Public

Last edited Aug 27, 2016

Created on Aug 27, 2016

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.

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

56% match

Loading thumbnail…

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

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.

CCliffordAnderson

56% 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

55% match

Loading thumbnail…

Docker nodejs

This example visualizes the build process of a Dockerized Node.js application, using a textual flowchart style. The code defines a Dockerfile that starts from the `node:alpine` base image, sets a working directory, copies `package.json`, runs `npm install`, and copies the rest of the source code before launching via `npm start`. The visualization highlights the sequence of filesystem and dependency operations, showing how the official Node.js API and npm commands construct the container image layer by layer.

HHuyAms

54% 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

52% match

Loading thumbnail…

Neo4j REST example

This example demonstrates a graph visualization of a Neo4j query result, showing how a single person node (e.g., “Stanley Kubrick”) is returned and rendered as a node in a force-directed layout. The code issues a Cypher POST request to the Neo4j REST endpoint, then uses d3.forceSimulation to position the node and draw it with SVG circles and labels. The visualization focuses on the raw response data, displaying only the returned `a` object without additional graph traversal or styling beyond basic node rendering.

CCliffordAnderson

52% match

Loading thumbnail…

Gist fa674a3db25bd721df50e36efa7736b3

This example demonstrates a Dockerized React application configured for development, testing, and production deployment using Dockerfiles and docker-compose. The development setup mounts source code as a volume, enables live reload, and runs tests via a separate service, while the production build uses a multi-stage Dockerfile that compiles the app with `npm run build` and serves static files through Nginx. Travis CI automates the pipeline, building the Docker image, running tests with `npm run test -- --coverage`, and deploying to AWS Elastic Beanstalk. The code leverages React’s development server and Node’s Alpine image for a lightweight containerized workflow, though no external data-viz libraries appear in this configuration.

HHuyAms

50% 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

50% match