Bitnami Docker Image for Parse Server
In order to unify the approaches followed for Bitnami containers and Bitnami Helm charts, we are moving the different bitnami/bitnami-docker-<container>
repositories to a single monorepo bitnami/containers
. Please follow bitnami/containers to keep you updated about the latest Bitnami images.
More information here: https://blog.bitnami.com/2022/07/new-source-of-truth-bitnami-containers.html
Parse is a platform that enables users to add a scalable and powerful backend to launch a full-featured app for iOS, Android, JavaScript, Windows, Unity, and more.
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.
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-parse/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.
DOCKER_CONTENT_TRUST=1
to verify the integrity of the images.Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Parse Server Chart GitHub repository.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
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.
Dockerfile
linksLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
5
, 5-debian-11
, 5.2.4
, 5.2.4-debian-11-r11
, latest
(5/debian-11/Dockerfile)
4
, 4-debian-11
, 4.10.13
, 4.10.13-debian-11-r10
(4/debian-11/Dockerfile)
Subscribe to project updates by watching the bitnami/parse GitHub repo.
To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.
Running Parse with a database server is the recommended way. You can either use docker-compose or run the containers manually.
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/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:
$ docker network create parse_network
$ docker run -d --name mongodb --net=parse_network bitnami/mongodb
Note: You need to give the container a name in order to Parse to resolve the host
$ docker run -d -p 1337:1337 --name parse --net=parse_network bitnami/parse
Then you can access your application at http://your-ip/parse
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 persistence of the MongoDB® data.
The above examples define docker volumes namely mongodb_data
and parse_data
. The Parse 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.
NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001
.
This requires a minor change to the docker-compose.yml
file present in this repository:
mongodb:
...
volumes:
- '/path/to/your/local/mongodb_data:/bitnami'
...
parse:
...
volumes:
- '/path/to/parse-persistence:/bitnami'
...
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:
$ docker network create parse-tier
$ docker run -d --name mongodb \
--net parse-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
$ docker run -d --name parse -p 1337:1337 \
--net parse-tier \
--volume /path/to/parse-persistence:/bitnami \
bitnami/parse:latest
Bitnami provides up-to-date versions of Mongodb and Parse, 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 container. For the Mongodb upgrade see https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#upgrade-this-image
$ docker pull bitnami/parse:latest
$ docker-compose stop parse
$ docker stop parse
$ rsync -a /path/to/parse-persistence /path/to/parse-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
Additionally, snapshot the MongoDB® data
You can use these snapshots to restore the application state should the upgrade fail.
$ docker-compose rm parse
$ docker rm parse
$ docker-compose up parse
docker run --name parse bitnami/parse:latest
When you start the parse 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:
docker-compose.yml
file present in this repository:parse:
...
environment:
- PARSE_HOST=my_host
...
-e
option with each variable and value: $ docker run -d -e PARSE_HOST=my_host -p 1337:1337 --name parse -v /your/local/path/bitnami/parse:/bitnami --network=parse_network bitnami/parse
Available environment variables:
PARSE_ENABLE_HTTPS
: Whether to enable HTTPS for Parse by default. Default: no
PARSE_BIND_HOST
: Parse bind host. Default: 127.0.0.1
PARSE_HOST
: Parse server host. Default: 127.0.0.1
PARSE_PORT_NUMBER_NUMBER
: Parse server port. Default: 1337
PARSE_APP_ID
: Parse app ID. Default: myappID
PARSE_MASTER_KEY
: Parse master key: mymasterKey
PARSE_APP_NAME
: Parse app name. Default: myappID
PARSE_MOUNT_PATH
: Parse server mount path. Default: /parse
PARSE_ENABLE_CLOUD_CODE
: Enable Parse cloud code support. Default no
PARSE_DATABASE_HOST
: Hostname for the MongoDB server. Default: mongodb
PARSE_DATABASE_PORT_NUMBER
: Port used by the MongoDB server. Default: 27017
PARSE_DATABASE_NAME
: Database name that Parse will use to connect with the database. Default: bitnami_parse
PARSE_DATABASE_USER
: Database user that Parse will use to connect with the database. Default: bn_parse
PARSE_DATABASE_PASSWORD
: Database password that Parse will use to connect with the database. No default.ALLOW_EMPTY_PASSWORD
: It can be used to allow blank passwords. Default: no
MONGODB_SHELL_DATABASE_HOST
: Hostname for the MongoDB server. Default: mongodb
MONGODB_SHELL_DATABASE_PORT_NUMBER
: Port used by the MongoDB server. Default: 27017
MONGODB_SHELL_DATABASE_ROOT_USER
: Database admin user. Default: root
MONGODB_SHELL_DATABASE_ROOT_PASSWORD
: Database password for the database admin user. No defaults.MONGODB_SHELL_CREATE_DATABASE_NAME
: New database to be created by the mongodb-shell module. No defaults.MONGODB_SHELL_CREATE_DATABASE_USERNAME
: New database user to be created by the mongodb-shell module. No defaults.MONGODB_SHELL_CREATE_DATABASE_PASSWORD
: Database password for the MONGODB_SHELL_CREATE_DATABASE_USERNAME
user. No defaults.MONGODB_SHELL_EXTRA_FLAGS
: Extra flags when using the mongodb-shell during initialization. No defaults.ALLOW_EMPTY_PASSWORD
: It can be used to allow blank passwords. Default: no
You can use Cloud Code to run a piece of code in your Parse Server instead of the user's mobile devices. To run your Cloud functions using this image, follow the steps below:
$ mkdir ~/cloud
$ cat > ~/cloud/main.js <<'EOF'
Parse.Cloud.define("sayHelloWorld", function(request, response) {
return "Hello world!";
});
EOF
/opt/bitnami/parse/cloud
path on your Parse Container and set the environment variable PARSE_ENABLE_CLOUD_CODE
to yes
. You can use the docker-compose.yml
below:NOTE: In the example below, Parse Dashboard is also deployed.
version: '2'
services:
mongodb:
image: 'bitnami/mongodb:latest'
volumes:
- 'mongodb_data:/bitnami'
parse:
image: 'bitnami/parse:latest'
ports:
- '1337:1337'
environment:
- PARSE_ENABLE_CLOUD_CODE=yes
volumes:
- 'parse_data:/bitnami'
- '/path/to/home/directory/cloud:/opt/bitnami/parse/cloud'
depends_on:
- mongodb
parse-dashboard:
image: 'bitnami/parse-dashboard:latest'
ports:
- '80:4040'
volumes:
- 'parse_dashboard_data:/bitnami'
depends_on:
- parse
volumes:
mongodb_data:
driver: local
parse_data:
driver: local
parse_dashboard_data:
driver: local
docker-compose
tool to deploy Parse and Parse Dashboard:$ docker-compose up -d
Find more information about Cloud Code and Cloud functions in the official documentation.
root
user and the Parse daemon was started as the parse
user. From now on, both the container and the Parse 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.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.
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:
docker version
)docker info
Copyright © 2022 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.