Could really use this, especially now that WriteFreely.host is up and running, so I'll get started on it.

Actually, I think this is good for now.

Yep that's perfect, thanks 👍 That way anyone can make changes if needed. I've also changed that default value in the "Create Task" form.

Still need to describe what each setting does, but this is nearly complete.

I updated the task's tag and changed it to be editable by All Users. Is that the right group?

This is done. The relevant commits that resolved it:

Ooh. I look forward to seeing this implemented, since I currently have a Blogger blog.

Thanks @bkoehn! A lot of people have their eyes on the Docker setup right now, but for now @benovermyer has taken the reins on it. What other kinds of build integrations could you help with?

BTW if you can tell me how to do a build I'll include that in a multi-stage Dockerfile that will build the app and yield a compact image.

I have a simple but functional Dockerfile that I use. You can get it on my GitLab. Really it doesn't need much; feel free to use it in the official distro; right now it takes the URI of the current release as a build argument; if you need additional build integration I'd be happy to help out.

A few changes:

Also #25 on GitHub

That latest change still needs schema.sql in the same folder, but adds the option to create tables with writefreely --init-db

Looking at a way to include schema.sql in the binary now. So many libraries to pick from...

Aye, that sounds perfect.

Great point. We can include a FileName field in the config.DatabaseCfg struct, and use something like writefreely.db as the default in the config.New() func.

Probably worth making the filename of the database configurable.

Also tracked on GitHub.

Prioritize based on feedback and user requests. So far, no one has requested this.