@byronnash, you’re not wrong – the complexity of the Toolkit config is something we talk about internally often – it’s…less than ideal. If it helps, there are a couple legitimate reasons why it’s so complex: one is environment-specific configuration: you can have different apps, different engines or even the same apps/engines but with different settings in different artist environments. It gives you a lot of power for customization, and it looks like Mykhaylo took good advantage of it in his setup.
The other is includes – you can set some set of configurations in a single file, then reference it into other files, so that you only need to make changes in a single place when there’s common data. Efficient on the whole, but does mean that you have to bounce through several files sometimes when you’re first setting something up.
If you’re new to complex modifications like this to your config, I can offer a few resources:
- Adding an app – We don’t have a specific doc for adding an engine, but much of the logic is the same for adding an app. This is a step-by-step guide that should be helpful (in fact, all those Getting Started guides would probably be useful for you).
-
Environment Configuration Reference – This doc goes through all the details of the structure of the environment configuration (
config/env/*), including includes, per-environment configuration, etc. It’s a good resource for understanding how it all fits together.
Hope that helps a bit! Thanks so much for the feedback!