Setame

Setame is a configuration management server designed to have a central location to store configuration. Applications can be configured to load their configuration on startup and be changed without requiring an application to be redeployed for a config change.

Features

• Ability to define global deployment environments as well as global settings that all applications can inherit (e.g. you can set a log server for all applications)
• Create variables at the application level that are inherited by each environment
• .NET Configuration Provider
• Audit logs of changes

Getting Started

1. Open the configuration file and set the ConnecitonStrings.DefaultConnection to be to a postgress database.
2. Setup the MailSettings (this is used when a user forgets their password)
3. Open the application and login with "admin@admin.com" and a password of "admin". This will open the setup page
4. On the setup page enter a valid email address and your password
5. Now login and you are ready to start configurating!

Upcoming Feature Possibilities

This is a rough roadmap of features we want to have (but not a guarantee)

• Secret storage
• Order Environments
• Add custom environment to an application in addition of what comes from environment set (this will then require ordering of environments)
• Environment Groups. A set of environment variables tied to an environment set that can be applied to multiple applications. This allows the user to attach commonly re-used variables to an application that may not be used for ALL applications (That is where you would use the environment set method)
• Ability to Duplicate Environment Set
• Ability to Duplicate Application
• Filter/Search applications
• Attach/Detach application from Environment Set
• Case Sensitive/Insensitive Configuration flag (or just detection of case mismatches between sets/groups/applications)
• Per Application Security Access (read/write/secrets/etc)
• Variable version pinning so that you always get the version of config that you want (may help with environment renames as well)
• Live variables changes (May be .NET provider only)
• Tracking of variable usages (may be .NET only)
• Host Based or Percentage Based Config. A certain percentage of clients can get a specific setting (this could be used for A/B testing)
• History screens to have searching/paging
• Visual of applied config and why a given setting is being overriden
• Internationalization
• Rename environment when no apps are associated, should just proceed without the warning dialog

TODO

Items that are still pending before this is considered a Beta:

• Test out the actual client config provider again after all the changes recently

Environment Sets

• Confirm Delete Environment Set (should be same logic as deleting an environment)

Applications

• Regenerate Token

Users

• All of it