Remote Configs simplify configuration management by moving settings to Candor Studios' website through a clean user interface. As a freelancer, you can create configs with components and different properties (similar to a JSON file) and assign them to clients. Clients can then modify these values directly from their dashboard to control how their software behaves. When your application starts up, it fetches these configuration values from Candor Studios and adjusts its behavior accordingly—just like with a traditional config file.

This approach spares clients from dealing with code, JSON, or complex configuration files, providing them with a more streamlined experience. It also makes for an easier experience as a developer, as you can easily use one of our libraries instead of handling configs manually. For added security, all configuration values are encrypted at rest.

<aside> 🛑

To use a config system in an order, you must discuss it with the client beforehand (before they pay) and gain their approval. If they do not approve and they haven’t paid yet, you may either chose to ask the OM to remove you from the order, or to not include the config system. If they have paid and they don’t agree, you will be required to not include the config system.

</aside>

Creating a Config

To create a config, head to Candor Studios’ website, then to Freelancers > Config Manager. From here, you’ll be able to enter a name for a config and then assign it to a client. Please choose a descriptive name to simplify the experience for the client!

Example of a config

Components

Components are the fundamental building blocks of configs and represent individual fields in the config. Each component has a name (showed to the client and you), a value (set by the client), and a key (used in your code to retrieve the data). The currently supported types are:

• String
• Integer
• Float
• Boolean
• Array (arrays have schemas for children elements - nested arrays are also supported)
• Header (visual and only for UI on the website, doesn’t do anything but provides information to the client)
• Description (also visual)

With more planned in the future. You can add components to the config schema using the add button at the top right. You’ll be asked to enter the following:

• Name - showed to you and the client as a visual reminder of what the component does
• Key - The key that you’ll use in your code to retrieve the current value of the component
• Type - What type of component this is

For arrays, you’ll also need to define the schema of each child. You can do this by clicking the add button next to the array once you’ve created it. Nested arrays are also supported.