![https with bitnami mean stack https with bitnami mean stack](https://www.out48.com/wp-content/uploads/2017/06/170615_003.png)
There won't be any changes to the image itself or to the registries where the image is available.
#Https with bitnami mean stack code
For example, the source code for PostgreSQL at bitnami/bitnami-docker-postgresql will be moved under the containers/postgresql directory in the bitnami/containers repository.Ĭontainer images will be displayed as usual in the Bitnami DockerHub organization. No, the code will be migrated as it is from the different repositories to the monorepo. Will the source code or the container images change? These repositories will be archived in read-only mode so you can continue checking the whole history of the repository changes and existing issues.Ĭurrently, we plan to delete these repositories after one year, but we would be open to community feedback here. The existing bitnami/bitnami-docker-* repositories will not disappear. How Will Containers Code Look After this Change? From that point onwards, repositories will be migrated on a gradual basis. We expect to have a large portion of the data migrated by July 15th. In addition, the internal test and release pipeline will be adapted to pull/push changes from the new repository.
![https with bitnami mean stack https with bitnami mean stack](https://d33np9n32j53g7.cloudfront.net/assets/webinar/thumbnails/webinar-bitnami-mean-stack-azure-11d3f4b68d8286df0885c9a28e83478c.png)
Then, all the bitnami/bitnami-docker-* repositories will be analyzed in order to identify the valuable issues and migrate them to their new bitnami/containers repo.įor existing open PRs, we will engage with contributors to find a better way to move their contributions forward into the new bitnami/containers repository. In the coming weeks, the Bitnami team will transfer all valid open issues to the new repository. The possibility of using VMware Image Builder (VIB), a service that allows developers and contributors to verify their Pull Requests (PRs) and thus provide an early feedback loop.Having a single and updated place for general announcements, changes in the contributing guidelines, and so on.Having all issues located under the same repository makes it easier to find common use cases and avoids duplication which ultimately improves the support workflow.In addition to an easier way to find the code, users will benefit from: Thus, container users will be able to navigate through the code of all Bitnami containers by checking only a single repository. In order to unify both repositories, we have opted to extend the monorepo approach to Bitnami containers as we already did with Helm charts. Moreover, unifying the repositories where their code lives also allows us to unify all the processes involved in the life cycle of their source code. Now, we have adopted a “monorepo approach” to remove the differences in the user experience between Helm charts and containers on GitHub. Over the past few months, the Bitnami content team has been working on unifying the source of truth for the different assets that Bitnami provides to its users.Ĭurrently, users can find the source code for the Bitnami Helm charts in a single repository on Github ( ) while the source code for the Bitnami containers is spread across different repositories for each solution (for example, ).