Bitnami package for Appsmith

What is Appsmith?

Appsmith is an open source platform for building and maintaining internal tools, such as custom dashboards, admin panels or CRUD apps.

Overview of Appsmith 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 run -it --name appsmith bitnami/appsmith:latest

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 that gives you a small base container image and the familiarity of a leading Linux distribution- or scratch -an explicitly empty image-.
• All Bitnami images available in Docker Hub are signed with Notation. Check this post to know how to verify the integrity of the images.
• Bitnami container images are released on a regular basis with the latest distribution packages available.

Looking to use Appsmith in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.

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.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the bitnami/containers GitHub repo.

Get this image

The recommended way to get the Bitnami Appsmith Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/appsmith:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/appsmith:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .

Maintenance

Upgrade this image

Bitnami provides up-to-date versions of Appsmith, 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

docker pull bitnami/appsmith:latest

or if you're using Docker Compose, update the value of the image property to bitnami/appsmith:latest.

Step 2: Remove the currently running container

docker rm -v appsmith

or using Docker Compose:

docker-compose rm -v appsmith

Step 3: Run the new image

Re-create your container from the new image.

docker run --name appsmith bitnami/appsmith:latest

or using Docker Compose:

docker-compose up appsmith

Configuration

Environment variables

Customizable environment variables

Read-only environment variables

When you start the Appsmith 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. Please note that some variables are only considered when the container is started for the first time. 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:

  appsmith-api:
    ...
    environment:
      - APPSMITH_PASSWORD=my_password
    ...
  

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

  $ docker run -d --name appsmith-api -p 80:8080 -p 443:8443 \
    --env APPSMITH_PASSWORD=my_password \
    --env APPSMITH_MODE=backend \
    --network appsmith-tier \
    --volume /path/to/appsmith-persistence:/bitnami \
    bitnami/appsmith:latest
  

Available environment variables:

Run mode

Appsmith supports three running modes:

• Backend: The Appsmith API. It is the essential functional element of Appsmith.
• RTS: Necessary for performing real-time editing of the applications created by Appsmith.
• Client: Contains the UI of Appsmith. This is the main entrypoint for users.

The running mode is defined via the APPSMITH_MODE environment variable. The possible values are backend, rts and client.

Connect Appsmith container to an existing database

The Bitnami Appsmith container supports connecting the Appsmith application to an external database. This would be an example of using an external database for Appsmith.

• Modify the docker-compose.yml file present in this repository:

     appsmith:
       ...
       environment:
  -      - APPSMITH_DATABASE_HOST=mongodb
  +      - APPSMITH_DATABASE_HOST=mongodb_host
         - APPSMITH_DATABASE_PORT_NUMBER=27017
         - APPSMITH_DATABASE_NAME=appsmith_db
         - APPSMITH_DATABASE_USER=appsmith_user
  -      - ALLOW_EMPTY_PASSWORD=yes
  +      - APPSMITH_DATABASE_PASSWORD=appsmith_password
       ...
  

• For manual execution:

  $ docker run -d --name appsmith\
    -p 8080:8080 -p 8443:8443 \
    --network appsmith-network \
    --env APPSMITH_DATABASE_HOST=mongodb_host \
    --env APPSMITH_DATABASE_PORT_NUMBER=27017 \
    --env APPSMITH_DATABASE_NAME=appsmith_db \
    --env APPSMITH_DATABASE_USER=appsmith_user \
    --env APPSMITH_DATABASE_PASSWORD=appsmith_password \
    --volume appsmith_data:/bitnami/appsmith \
    bitnami/appsmith:latest
  

Logging

The Bitnami Appsmith Docker image sends the container logs to stdout. To view the logs:

docker logs wordpress

Or using Docker Compose:

docker-compose logs wordpress

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Using docker-compose.yaml

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated Bitnami Helm chart.

If you detect any issue in the docker-compose.yaml file, feel free to report it or contribute with a fix by following our Contributing Guidelines.

Contributing

We'd love for you to contribute to this Docker image. You can request new features by creating an issue or submitting 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 fill the issue template.

License

Copyright © 2024 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

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.