Distr v1.1 is Here!
All the details about the inaugural release of Distr v1.0
The inaugural release of Distr v1.0 shipped just a little over a week ago, and we’re already back with a minor update that packs some major features. These updates expand what Distr can do for your software distribution needs.
1. Feature: GitHub Release Action
This action creates a new version of a Distr application, fully automating the software release lifecycle.
-
Why it matters: No more manual steps. With this action, you can ship new Docker and Helm based application versions automatically from end to end, so they’re instantly available on Distr for deployment. It ties up the loose ends of your CI/CD workflow and saves you time.
-
How to use it: Check out the action documentation to get started.
This example shows how to create a new version of a Docker based application.
2. Feature: Docker environment variable Management
This feature simplifies managing environment variables in your Docker Compose setup for a smoother, more secure deployment.
-
Why it matters: Managing environment variables can be tricky, especially in complex applications. With this feature, you can centralize and simplify env management, reducing errors and making it easier to maintain consistency across different environments.
-
How to get started: Check out the guide on how to manage environment variables in Docker Compose files.
Have questions or feedback? Join the discussion or request a demo call!
Upgrading to v1.1
Our hosted version of Distr was already upgraded to the latest v1.1 release.
To take advantage of all new features in Distr v1.1, here’s what you need to do if you’re using the previous version of the agents:
- If you’re running an older agent version, click update agent via the deployment web UI to ensure compatibility with the latest improvements.
If you are self-hosting Distr make sure to check out our changelog.
What’s Coming Next
Based on user feedback and feature requests, we are currently working on licensing and private repository support. Here’s how it will look:
- Each license is uniquely named within its organization and can optionally include an expiration date (agent can revoke access to software is if there is now renewal)
- Licenses are tied to a specific application and can apply either to all versions or only to selected ones.
- Deployments can be linked to a license. If the license is activated, customers see only applications and versions they have a license for
- For organizations using private container registries, licenses can also include Docker login credentials (such as a registry URL, username, and password) so the agent can authenticate and pull images securely.
Would love to get your thoughts on the licensing feature and hear what else you would like us to ship next.
Join the Conversation
We’d love to hear your thoughts on this release. Share your feedback, ideas, or questions:
- Join the discussion
- Book a demo call
- Reach out on LinkedIn or Twitter
Thank You!
Thank you for being part of the Distr community. We’re excited to keep building the best open source software distribution platform together.
