We're harnessing the constant Swedish summer sun to push the possibilities for how you can use Molnett in more advanced ways. As companies evolve and grow they tend to follow patterns that spread across their applications. In this week's Changelog, we are tackling one of these issues: Configuration!
One of our customers manages 8+ shared environment variables per service in their GitHub workflows. For example, DATABASE_URL is repeated across many of their services. When you need to update your database connection, you'd hunt through every service configuration, hoping you didn't miss one.
They put it perfectly: "We just want our DATABASE_URL to change when we copy environments - our app automatically seeds based on which environment it's running in."
Configure all services in one go
Our new feature Config Sets lets you configure environment variables in one location that all services automatically inherit on their next deployment. This means you can manage shared infrastructure configuration - like database connections or log levels - without touching individual service settings.
Override configuration per service
Sometimes you need one service to be different. Perhaps you're debugging a specific service and need DEBUG logging while keeping everything else at INFO. Service-level variables take precedence over Config Sets, so you can override any environment-level configuration when needed.
Configure new environments on copy
Remember that customer who wanted their DATABASE_URL to change when copying environments? Now it's built right in. When you copy an environment, you can override any Config Set variables for the new environment.
Config Sets are available today for all Molnett users. Your GitHub workflows just got a lot simpler.
Thank you for being with us on this journey. If you want to follow along as we build, apply for early access below.