This comment has been minimized.

I’m now recalling this happening to me to. It seems that in SQLite it creates user in that step where as MySQL it doesn’t. Maybe easiest is to not create user automatically in this step and keep it the same for both SQLite and MySQL?

This comment has been minimized.

@MasterGroosha Moving account creation to --init-db is a good thought, but I think that command should remain non-interactive, so doing it there probably wouldn't be a good fit.

I guess we have to decide what the --config step should be. Should that command stay as a utility you can repeatedly run? Or should it be more of an install step that guides the user as much as possible? I'm thinking the latter (in which case we'd include the init-db step), but I'm open to suggestions.

This comment has been minimized.

@thebaer Maybe you should first ask which backend to use - MySQL or SQLite and if the answer is SQLite, then stop config utility with message "Please run writefreely --init-db first and restart this config"

This comment has been minimized.

That user-creation step doesn't depend on the database type -- it only happens if you're setting up a single-user instance, like @geekgonecrazy mentioned. If it is single-user, you have to create that first user while setting things up (there's no way to do it via the web). So I think we should make that as easy as possible and automatically include the init-db step during single-user configuration.

We'll keep the init-db command available; I just think it'll be best to reduce the number of steps for people during install.