Understand upcoming changes to Bitnami Stacks
For more than ten years, Bitnami has been providing pre-packaged installers and cloud images for automated setup of popular server software on Windows, macOS and Linux platforms. These installers and images contain all the components needed to to run the software out-of-the-box in a self contained environment. Under this approach, there were no additional libraries, databases, and runtimes to download, and, once installed, the new application or development environment would not interfere with other software on your system.
However, with the growing popularity of containers, Bitnami has been gradually shifting towards building images on Linux for each specific distro, depending on external native system packages on Linux platforms, allowing to reduce the complexity to build each Bitnami image and enabling users to perform advanced modifications. In addition to this, some extra changes involving the file structure and configurations have been made for many components, such as Apache, to make it easier to use and develop on top of.
As part of modernizing the existing Bitnami Open Source Catalog, and unifying common parts with Bitnami container images, we are performing the following major changes to Bitnami Stacks:
- Bitnami Stacks on Linux will start depending on native system packages for Debian 10, dropping the previous approach of providing a complete self-contained environment.
- The location of files and directories may change using the new approach, with respect to the previous self-contained installations.
- Components may be configured differently to improve the performance and maintainability of the application.
These changes are being performed in a gradual way, and it is expected that some time may pass before the entire catalog is updated. This page will be updated when that happens.
To identify whether A) a Bitnami Stack uses native Linux system packages, or B) is a self-contained installation, you can run the command below:
$ test ! -f "/opt/bitnami/common/bin/openssl" && echo "Approach A. Using system packages." || echo "Approach B. Self-contained installation."
The output of the command indicates which approach (A or B) is used by the stack. You can use this information as a guide to identify the appropriate paths, configuration and commands to use in our documentation.
If you have any questions on these changes, contact us in the github repository.