confidentmachine / bitnami-docker-parse-dashboard

Bitnami Parse Dashboard Docker Image http://bitnami.com/docker

Parse Dashboard packaged by Bitnami

What is Parse Dashboard?

Parse Dashboard is a standalone dashboard for managing your Parse apps. You can use it to manage your Parse Server apps.

Overview of Parse Dashboard

Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

Docker Compose

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-parse-dashboard/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

You can find the default credentials and available configuration options in the Environment Variables section.

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.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
• All Bitnami images available in Docker Hub are signed with Docker Content Trust (DCT). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
• Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

Supported tags and respective Dockerfile links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 3, 3-debian-10, 3.3.0, 3.3.0-debian-10-r6, latest (3/debian-10/Dockerfile)

Subscribe to project updates by watching the bitnami/parse-dashboard GitHub repo.

Prerequisites

To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.

How to use this image

Run the application using Docker Compose

The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-parse-dashboard/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

Run the application manually

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

1. Create a network for the application, Parse Server and the database:

$ docker network create parse_dashboard-tier

2. Start a MongoDB® database in the network generated:

$ docker run -d --name mongodb --net=parse_dashboard-tier bitnami/mongodb

Note: You need to give the container a name in order to Parse to resolve the host.

3. Start a Parse Server container:

$ docker run -d -p 1337:1337 --name parse --net=parse_dashboard-tier bitnami/parse

4. Run the Parse Dashboard container:

$ docker run -d -p 80:4040 --name parse-dashboard --net=parse_dashboard-tier bitnami/parse-dashboard

Then you can access your application at http://your-ip/

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. Additionally you should mount a volume for the persistence of MongoDB® and Parse data.

The above examples define docker volumes namely mongodb_data, parse_data and parse_dashboard_data. The application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Mount host directories as data volumes with Docker Compose

This requires a minor change to the docker-compose.yml file present in this repository:

services:
  mongodb:
  ...
    volumes:
      - '/path/to/mongodb-persistence:/bitnami'
  ...
  parse:
  ...
    volumes:
      - '/path/to/parse-persistence:/bitnami'
  ...
  parse-dashboard:
  ...
    volumes:
      - '/path/to/parse_dashboard-persistence:/bitnami'
  ...

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Mount host directories as data volumes using the Docker command line

In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:

1. Create a network (if it does not exist):

$ docker network create parse_dashboard-tier

2. Create a MongoDB® container with host volume:

$ docker run -d --name mongodb \
  --net parse-dashboard-tier \
  --volume /path/to/mongodb-persistence:/bitnami \
  bitnami/mongodb:latest

Note: You need to give the container a name in order to Parse to resolve the host.

3. Start a Parse Server container:

$ docker run -d -name parse -p 1337:1337 \
  --net parse-dashboard-tier
  --volume /path/to/parse-persistence:/bitnami \
  bitnami/parse:latest

4. Run the Parse Dashboard container:

$ docker run -d --name parse-dashboard -p 80:4040 \
--volume /path/to/parse_dashboard-persistence:/bitnami \
bitnami/parse-dashboard:latest

Upgrade this application

Bitnami provides up-to-date versions of Parse Dashboard, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Parse Dashboard container.

1. Get the updated images:

$ docker pull bitnami/parse-dashboard:latest

2. Stop your container

• For docker-compose: $ docker-compose stop parse-dashboard
• For manual execution: $ docker stop parse-dashboard

3. Take a snapshot of the application state

$ rsync -a /path/to/parse-persistence /path/to/parse-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the MongoDB® and Parse server data.

You can use these snapshots to restore the application state should the upgrade fail.

4. Remove the currently running container

• For docker-compose: $ docker-compose rm parse-dashboard
• For manual execution: $ docker rm parse-dashboard

5. Run the new image

• For docker-compose: $ docker-compose up parse-dashboard
• For manual execution (mount the directories if needed): docker run --name parse-dashboard bitnami/parse-dashboard:latest

Configuration

Environment variables

When you start the parse-dashboard 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. If you want to add a new environment variable:

• For docker-compose add the variable name and value under the application section in the docker-compose.yml file present in this repository:

parse-dashboard:
  ...
  environment:
    - PARSE_DASHBOARD_PASSWORD=my_password
  ...

• For manual execution add a -e option with each variable and value:

 $ docker run -d -e PARSE_DASHBOARD_PASSWORD=my_password -p 80:4040 --name parse-dashboard -v /your/local/path/bitnami/parse_dashboard:/bitnami --network=parse_dashboard-tier bitnami/parse-dashboard

Available environment variables:

User and Site configuration

• PARSE_DASHBOARD_ENABLE_HTTPS: Whether to enable HTTPS for Parse Dashboard by default. Default: no
• PARSE_DASHBOARD_EXTERNAL_HTTP_PORT_NUMBER: External HTTP port for Parse Dashboard. Default: 80
• PARSE_DASHBOARD_EXTERNAL_HTTPS_PORT_NUMBER: External HTTPS port for Parse Dashboard. Default: 80
• PARSE_DASHBOARD_PARSE_HOST: Parse server host. Default: parse
• PARSE_DASHBOARD_PORT_NUMBER: Port number in which Parse Dashboard will run. Default: 4040
• PARSE_DASHBOARD_PARSE_PORT_NUMBER: Parse server port number. Default: 1337
• PARSE_DASHBOARD_PARSE_APP_ID: Parse app ID. Default: myappID
• PARSE_DASHBOARD_PARSE_APP_NAME: Parse app name. Default: myappID
• PARSE_DASHBOARD_PARSE_MASTER_KEY: Parse master key: mymasterKey
• PARSE_DASHBOARD_PARSE_MOUNT_PATH: Parse server mount path. Default: /parse
• PARSE_DASHBOARD_PARSE_PROTOCOL: Parse server protocol. Default: https
• PARSE_DASHBOARD_USERNAME: Parse Dashboard user name. Default: user
• PARSE_DASHBOARD_PASSWORD: Parse Dashboard password. Default: bitnami

Notable Changes

2.1.0-debian-10-r328

• The size of the container image has been decreased.
• The configuration logic is now based on Bash scripts in the rootfs/ folder.

1.2.0-r69

• The Parse Dashboard container has been migrated to a non-root user approach. Previously the container ran as the root user and the Parse Dashboard daemon was started as the parsedashboard user. From now on, both the container and the Parse Dashboard daemon run as user 1001. As a consequence, the data directory must be writable by that user. You can revert this behavior by changing USER 1001 to USER root in the Dockerfile.

Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

Issues

If you encountered a problem running this container, you can file an issue. 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_APP_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

License

Copyright © 2022 Bitnamii

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.