Initial commit

bitnami/neo4j/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,60 @@
+<!--
+If you are reporting a new issue, make sure that we do not have any duplicates
+already open. You can ensure this by searching the issue list for this
+repository. If there is a duplicate, please close your issue and add a comment
+to the existing issue instead.
+
+If you suspect your issue is a bug, please edit your issue description to
+include the BUG REPORT INFORMATION shown below. If you fail to provide this
+information within 7 days, we cannot debug your issue and we'll close it. We
+will, however, reopen it if you later provide the information.
+-------------------------------
+    BUG REPORT INFORMATION
+-------------------------------
+Use the commands below to provide key information from your environment:
+You do NOT have to include this information if this is a FEATURE REQUEST
+-->
+
+**Description**
+
+<!-- Briefly describe the problem you are having in a few paragraphs. -->
+
+**Steps to reproduce the issue:**
+
+1. [First Step]
+2. [Second Step]
+3. [and so on...]
+
+**Describe the results you received:**
+
+<!-- What actually happens -->
+
+**Describe the results you expected:**
+
+<!-- What you expect to happen -->
+
+**Additional information you deem important (e.g. issue happens only occasionally):**
+
+<!-- Any additional information, configuration or data that might be necessary to reproduce the issue. -->
+
+**Version**
+
+- Output of `docker version`:
+
+```
+(paste your output here)
+```
+
+- Output of `docker info`:
+
+```
+(paste your output here)
+```
+
+- Output of `docker-compose version` (if applicable):
+
+```
+(paste your output here)
+```
+
+**Additional environment details (AWS, VirtualBox, Docker for MAC, physical, etc.):**

bitnami/neo4j/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,32 @@
+<!--
+ Before you open the request please review the following guidelines and tips to help it be more easily integrated:
+
+ - Describe the scope of your change - i.e. what the change does.
+ - Describe any known limitations with your change.
+ - Please run any tests or examples that can exercise your modified code.
+
+ Thank you for contributing! We will try to test and integrate the change as soon as we can, but be aware we have many GitHub repositories to manage and can't immediately respond to every request. There is no need to bump or check in on a pull request (it will clutter the discussion of the request).
+
+ Also don't be worried if the request is closed or not integrated sometimes the priorities of Bitnami might not match the priorities of the pull request. Don't fret, the open source community thrives on forks and GitHub makes it easy to keep your changes in a forked repo.
+ -->
+
+**Description of the change**
+
+<!-- Describe the scope of your change - i.e. what the change does. -->
+
+**Benefits**
+
+<!-- What benefits will be realized by the code change? -->
+
+**Possible drawbacks**
+
+<!-- Describe any known limitations with your change -->
+
+**Applicable issues**
+
+<!-- Enter any applicable Issues here (You can reference an issue using #) -->
+
+**Additional information**
+
+<!-- If there's anything else that's important and relevant to your pull
+request, mention that information here.-->

bitnami/neo4j/3/Dockerfile

@@ -0,0 +1,22 @@
+FROM bitnami/minideb-extras:jessie-r24
+LABEL maintainer "Bitnami <containers@bitnami.com>"
+
+# Install required system packages and dependencies
+RUN bitnami-pkg install java-1.8.161-0 --checksum eb289afc43eda33d5920294460dc256f6543318506ca5a540bba9073412cfd06
+RUN bitnami-pkg unpack neo4j-3.3.3-0 --checksum 0ef839567b99a7308aa0b58c6bcaccebf9416af4324dcfde10924ae68dfbc7ce
+
+COPY rootfs /
+
+ENV BITNAMI_APP_NAME="neo4j" \
+    BITNAMI_IMAGE_VERSION="3.3.3-r1" \
+    NEO4J_BOLT_PORT_NUMBER="7687" \
+    NEO4J_HOST="" \
+    NEO4J_HTTPS_PORT_NUMBER="7473" \
+    NEO4J_HTTP_PORT_NUMBER="7474" \
+    NEO4J_PASSWORD="bitnami" \
+    PATH="/opt/bitnami/java/bin:/opt/bitnami/neo4j/bin:$PATH"
+
+EXPOSE 7474
+
+ENTRYPOINT ["/app-entrypoint.sh"]
+CMD ["nami","start","--foreground","neo4j"]

bitnami/neo4j/3/docker-compose.yml

@@ -0,0 +1,13 @@
+version: '2'
+services:
+  neo4j:
+    image: 'bitnami/neo4j:3'
+    ports:
+      - '7474:7474'
+      - '7473:7473'
+      - '7687:7687'
+    volumes:
+      - 'neo4j_data:/bitnami'
+volumes:
+  neo4j_data:
+    driver: local

bitnami/neo4j/3/rootfs/app-entrypoint.sh

@@ -0,0 +1,13 @@
+#!/bin/bash -e
+
+. /opt/bitnami/base/functions
+. /opt/bitnami/base/helpers
+
+print_welcome_page
+
+if [[ "$1" == "nami" && "$2" == "start" ]] || [[ "$1" == "/init.sh" ]]; then
+  nami_initialize neo4j
+  info "Starting neo4j... "
+fi
+
+exec tini -- "$@"

bitnami/neo4j/3/rootfs/neo4j-inputs.json

@@ -0,0 +1,7 @@
+{
+  "boltPort": "{{$global.env.NEO4J_BOLT_PORT_NUMBER}}",
+  "host": "{{$global.env.NEO4J_HOST}}",
+  "httpPort": "{{$global.env.NEO4J_HTTP_PORT_NUMBER}}",
+  "httpsPort": "{{$global.env.NEO4J_HTTPS_PORT_NUMBER}}",
+  "password": "{{$global.env.NEO4J_PASSWORD}}"
+}

bitnami/neo4j/LICENSE

@@ -0,0 +1,13 @@
+Copyright (c) 2018 Bitnami
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

bitnami/neo4j/README.md

@@ -0,0 +1,279 @@
+[![CircleCI](https://circleci.com/gh/bitnami/bitnami-docker-neo4j/tree/master.svg?style=shield)](https://circleci.com/gh/bitnami/bitnami-docker-neo4j/tree/master)
+[![Slack](https://img.shields.io/badge/slack-join%20chat%20%E2%86%92-e01563.svg)](http://slack.oss.bitnami.com)
+
+# What is Neo4j?
+
+> Neo4j is the world’s leading Graph Database. It is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions. The programmer works with a flexible network structure of nodes and relationships rather than static tables — yet enjoys all the benefits of enterprise-quality database. For many applications, Neo4j offers orders of magnitude performance benefits compared to relational DBs.
+
+
+[https://neo4.com](https://neo4.com)
+
+# TL;DR;
+
+```bash
+$ docker run --name neo4j bitnami/neo4j:latest
+```
+
+## Docker Compose
+
+```bash
+$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-neo4j/master/docker-compose.yml > docker-compose.yml
+$ docker-compose up -d
+```
+
+# Why use Bitnami Images?
+
+* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
+* With Bitnami images the latest bug fixes and features are available as soon as possible.
+* Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
+* Bitnami images are built on CircleCI and automatically pushed to the Docker Hub.
+* All our images are based on [minideb](https://github.com/bitnami/minideb) a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
+
+# Get this image
+
+The recommended way to get the Bitnami Neo4j Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/neo4j).
+
+```bash
+$ docker pull bitnami/neo4j:latest
+```
+
+To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/neo4j/tags/) in the Docker Hub Registry.
+
+```bash
+$ docker pull bitnami/neo4j:[TAG]
+```
+
+If you wish, you can also build the image yourself.
+
+```bash
+$ docker build -t bitnami/neo4j:latest https://github.com/bitnami/bitnami-docker-neo4j.git
+```
+
+# Persisting your application
+
+If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
+
+For persistence you should mount a volume at the `/bitnami` path. The above examples define a docker volume namely `neo4j_data`. The Neo4j application state will persist as long as this volume is not removed.
+
+To avoid inadvertent removal of this volume you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.
+
+```bash
+$ docker run -v /path/to/neo4j-persistence:/bitnami bitnami/neo4j:latest
+```
+
+or using Docker Compose:
+
+```yaml
+neo4j:
+  image: bitnami/neo4j:latest
+  volumes:
+    - /path/to/neo4j-persistence:/bitnami
+```
+
+# Connecting to other containers
+
+Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa.
+
+Containers attached to the same network can communicate with each other using the container name as the hostname.
+
+## Using the Command Line
+
+### Step 1: Create a network
+
+```bash
+$ docker network create neo4j-network --driver bridge
+```
+
+### Step 2: Launch the Neo4j container within your network
+
+Use the `--network <NETWORK>` argument to the `docker run` command to attach the container to the `neo4j-network` network.
+
+```bash
+$ docker run --name neo4j-node1 --network neo4j-network bitnami/neo4j:latest
+```
+
+### Step 3: Run another containers
+
+We can launch another containers using the same flag (`--network NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network.
+
+## Using Docker Compose
+
+When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named neo4j-network.
+
+```yaml
+version: '2'
+
+networks:
+  neo4j-network:
+    driver: bridge
+
+services:
+  neo4j:
+    image: bitnami/neo4j:latest
+    networks:
+      - neo4j-network
+    ports:
+      - '7474:7474'
+      - '7473:7473'
+      - '7687:7687'
+```
+
+Then, launch the containers using:
+
+```bash
+$ docker-compose up -d
+```
+
+# Configuration
+
+## Environment variables
+
+When you start the neo4j image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. The following environment values are provided to custom Neo4j:
+
+- `NEO4J_PASSWORD`: Password used by Neo4j server. Default: **bitnami**
+- `NEO4J_HOST`: Hostname used to configure Neo4j advertised address. It can be either an IP or a domain. If left empty, it will be resolved to the machine IP. Default: **empty**
+- `NEO4J_BOLT_PORT_NUMBER`: Port used by Neo4j https. Default: **7687**
+- `NEO4J_HTTP_PORT_NUMBER`: Port used by Neo4j http. Default: **7474**
+- `NEO4J_HTTPS_PORT_NUMBER`: Port used by Neo4j https. Default: **7473**
+
+### Specifying Environment Variables using Docker Compose
+
+```yaml
+neo4j:
+  image: bitnami/neo4j:latest
+  environment:
+    - NEO4J_BOLT_PORT_NUMBER=7777
+```
+
+### Specifying Environment Variables on the Docker command line
+
+```bash
+$ docker run -d -e NEO4J_BOLT_PORT_NUMBER=7777 --name neo4j bitnami/n3o4j:latest
+```
+
+## Using your Neo4j configuration files
+
+In order to load your own configuration files, you will have to make them available to the container. You can do it mounting a [volume](https://docs.docker.com/engine/tutorials/dockervolumes/) in the desired location.
+
+### Using Docker Compose
+
+```yaml
+neo4j:
+  image: bitnami/neo4j:latest
+  volumes:
+    - '/local/path/to/your/confDir:/container/path/to/your/confDir'
+```
+
+# Logging
+
+The Bitnami neo4j Docker image sends the container logs to the `stdout`. To view the logs:
+
+```bash
+$ docker logs neo4j
+```
+
+or using Docker Compose:
+
+```bash
+$ docker-compose logs neo4j
+```
+
+You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
+
+# Maintenance
+
+## Upgrade this image
+
+Bitnami provides up-to-date versions of neo4j, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
+
+### Step 1: Get the updated image
+
+```bash
+$ docker pull bitnami/neo4j:latest
+```
+
+or if you're using Docker Compose, update the value of the image property to
+`bitnami/neo4j:latest`.
+
+### Step 2: Stop and backup the currently running container
+
+Stop the currently running container using the command
+
+```bash
+$ docker stop neo4j
+```
+
+or using Docker Compose:
+
+```bash
+$ docker-compose stop neo4j
+```
+
+Next, take a snapshot of the persistent volume `/path/to/neo4j-persistence` using:
+
+```bash
+$ rsync -a /path/to/neo4j-persistence /path/to/neo4j-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
+```
+
+You can use this snapshot to restore the database state should the upgrade fail.
+
+### Step 3: Remove the currently running container
+
+```bash
+$ docker rm -v neo4j
+```
+
+or using Docker Compose:
+
+```bash
+$ docker-compose rm -v neo4j
+```
+
+### Step 4: Run the new image
+
+Re-create your container from the new image, [restoring your backup](#restoring-a-backup) if necessary.
+
+```bash
+$ docker run --name neo4j bitnami/neo4j:latest
+```
+
+or using Docker Compose:
+
+```bash
+$ docker-compose start neo4j
+```
+
+# Contributing
+
+We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-neo4j/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-neo4j/pulls) with your contribution.
+
+# Issues
+
+If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-neo4j/issues). For us to provide better support, be sure to include the following information in your issue:
+
+- Host OS and version
+- Docker version (`docker version`)
+- Output of `docker info`
+- Version of this container (`echo $BITNAMI_IMAGE_VERSION` inside the container)
+- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
+
+# Community
+
+Most real time communication happens in the `#containers` channel at [bitnami-oss.slack.com](http://bitnami-oss.slack.com); you can sign up at [slack.oss.bitnami.com](http://slack.oss.bitnami.com).
+
+Discussions are archived at [bitnami-oss.slackarchive.io](https://bitnami-oss.slackarchive.io).
+
+# License
+Copyright 2018 Bitnami
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

bitnami/neo4j/circle.yml

@@ -0,0 +1,63 @@
+version: 2
+jobs:
+  build:
+    working_directory: /workdir
+    docker:
+      - image: docker:17.06.0-ce-git
+        environment:
+          RELEASE_SERIES_LIST: "3"
+          LATEST_STABLE: "3"
+          IMAGE_NAME: solr
+          DOCKER_PROJECT: bitnami
+          QUAY_PROJECT: bitnami
+          GCLOUD_PROJECT: bitnami-containers
+
+    steps:
+      - checkout
+      - setup_remote_docker:
+          version: 17.06.0-ce
+      - run:
+          name: Upgrade system packages (workaround - https://github.com/docker-library/docker/issues/72)
+          command: |
+            apk upgrade --no-cache
+      - run:
+          name: Install dependencies
+          command: |
+            apk add --no-cache curl bash coreutils
+      - run:
+          name: Docker info
+          command: |
+            docker version
+            docker info
+      - restore_cache:
+          keys:
+            - cache-{{ .Branch }}
+          paths:
+            - /cache/layers.tar
+      - run:
+          name: Build docker image
+          command: |
+            curl -sL https://raw.githubusercontent.com/bitnami/test-infra/master/circle/docker-image-test.sh | bash -
+      - save_cache:
+          key: cache-{{ .Branch }}-{{ epoch }}
+          paths:
+            - /cache/layers.tar
+      - deploy:
+          name: Publish docker image
+          command: |
+            if [ -n "${CIRCLE_TAG}" ]; then
+              curl -sL https://raw.githubusercontent.com/bitnami/test-infra/master/circle/docker-release-image.sh | bash -
+            elif [ "${CIRCLE_BRANCH}" == "master" ]; then
+              curl -sL https://raw.githubusercontent.com/bitnami/test-infra/master/circle/docker-development-image.sh | bash -
+            fi
+
+workflows:
+  version: 2
+  build-and-deploy:
+    jobs:
+      - build:
+          filters:
+            branches:
+              only: /.*/
+            tags:
+              only: /^[0-9].*-r[0-9]+$/

bitnami/neo4j/docker-compose.yml

@@ -0,0 +1,13 @@
+version: '2'
+services:
+  neo4j:
+    image: 'bitnami/neo4j:latest'
+    ports:
+      - '7474:7474'
+      - '7473:7473'
+      - '7687:7687'
+    volumes:
+      - 'neo4j_data:/bitnami'
+volumes:
+  neo4j_data:
+    driver: local