candidate enhancements, testing interest before submitting PRs

[sfinnie]

I just started using otter as a local, personal notes site. I've identified 3 candidate changes so far and would be happy to submit PRs. Before I do, I'd like to check whether they'd be welcomed. The changes are as follows:

1. Simplify running locally without Docker. I use waitress: pure Python, works across *nix and windows and supported by Flask. This change would add a requirements.txt with all required packages (incl waitress) plus addition of instructions to docs (git pull repo, set up & activate venv, pip install requirements, configure, run).
2. Upgrade to mistune 3.x. There's been a change in the package structure from 2.x which causes an import failure, meaning installation currently has to be constrained to <3.0.0
3. Bulk import. I already have a large number of markdown docs that are currently served using a static site generator. This change would add a new option to otterwiki/cli.py to import a pre-existing tree of files, along the lines of flask import /path/to/source/root /path/to/app-data. path/to/app-data can probaby be read from config by default, haven't looked at that yet.

I'd be happy to open separate issues for each and submit PRs if they're of interest.

Thanks.

[redimp]

Hey @sfinnie, thank you for reaching out.

(1) In #146 you find a request where this was discussed. I think it would be a cool feature to run AN Otter Wiki after a pip install otterwiki via otterwiki ....

(2) The PR #426 is currently under review (and testing) and looks very good.

(3) Importing data via git should be easy enough, but I see that this could be a feature for less console affine people. The feature to upload a .tar.gz or .zip in the admin interface with the option to pick where the uploaded files are put to would be cool.

PRs, feature requests and questions are always welcome.

[sfinnie]

@redimp thanks for converting to discussion and the reply. And apologies - afraid I missed both issue & PR when I looked.

I'll comment on #146 for (1) and investigate import, likely next week or so.

[redimp]

[..] And apologies - afraid I missed both issue & PR when I looked. [..]

No need to apologize!

(1) Awesome, thank you for taking care of this.