Look for a custom config file...

[toniwidmo]

Look for a custom_config.json first and only load the default config.json if it isn't found. That way the config file for a particular site won't be overwritten when upgrading to latest code versions.

[toniwidmo]

Best way to do this is to look for domain.name.config.json files based on current domain name in url. This will allow multiple domain names to be served from the same directory.

[toniwidmo]

Okay, suggested order of preference for loading config for https://example.domain.name

• example.domain.name.config.json
• example.domain.config.json
• example.config.json
• local_config.json
• config.json <--- the default site settings when no user specified settings are defined.

[toniwidmo]

I think only the local_config.json version needs to be working for the beta release, the others are an advanced multi-site capability that can be developed later. The first beta just needs to be an easy to install steem based single user blog. I will create a new issue for multi-site config.

[toniwidmo]

The rest of this task has been added as a new job #27, so this issue can be closed.