feat: support multiple projects/websites

[aosasona]

Chimney is designed to work as a single website in a container together with the chimney binary, but what if we could serve multiple instead.

This will indeed be a breaking change if I go about it the wrong way, but we could add a new tenant-mode (or just mode although it may be more confusing) option that can be set to single or multi and that will be used to decide if the server wants to go with the root_dir or a new sites array of tables.

• [x] support single and multi mode in config
• [x] implement support for single mode
• [ ] Implement support for multi mode
  • [ ] traverse all directories (with some exclusions) and find config files

    Note: prevent infinitely looping through cases like symlinks

  • [ ] load all config files
  • [ ] add a default error page
  • [ ] handle domain names (#20)
  • [ ] sanity checks to prevent silent failures

[aosasona]

While trying to implement #20, I realised it is kind of pointless to do that without this first.

[aosasona]

• [x] support mode in config
• [x] support single mode
• [ ] load all config files in the root directory
• [ ] add a default error page
• [ ] handle domain names
• [ ] sanity checks to prevent silent failures

[aosasona]

Also, we need to an option that allows users to ignore certain dirs

[aosasona]

TODO NEXT TIME: read config files in root