pyramid

Right now settings are just passed in through the settings file. This is somewhat limiting if there is a value that will be dynamic with deployments (such as a docker image file, etc.) We should support accepting settings through environment variables, the CLI, the current settings file, and any mix of those.

The order of precedence with mixed should be CLI -> environment -> config file.

If

I like the pyramid_swagger renderer from pyramid_swagger library.

With it, I can remove custom renderers from the realworld example app. And less code is always nice.

We can probably reuse the ide

There is legacy API right now that generally works, but there should be a better versioned API for the server, that utilizes HTTP verbs better, we probably should revamp some configuration keys and response formats too.