bottle

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

We should validate if the specification document contains the "openapi" key and that it's value matches the expression ^3\.\d+\.\d+$.

It might be a good idea to use abort(404, <reason>) in some places like

• https://github.com/PyJaipur/PyJudge/blob/e3debe1e15447a6faac9d509e7ad5283731fa2c0/server.py#L89
• https://github.com/PyJaipur/PyJudge/blob/e3debe1e15447a6faac9d509e7ad5283731fa2c0/server.py#L102

some places however don't require the error. For example this

• https://github.com/PyJaipur/PyJudge/blob/e3debe1e15447