pyFilesystem support for loading and saving data

[jayvdb]

https://github.com/PyFilesystem

moban currently supports custom filesystem 'git'.

To add more it should adopt a generic fs layer, like hyde.

[chfw]

does it mean wherever moban uses file system, use pyFilesystem?

[jayvdb]

possible, but not a good idea imo.

Also pyfs doesnt support git.

this is only for non-local files, so e.g. deployment could be done with moban.

[jayvdb]

A github driver is at https://github.com/merlink01/fs.github . Not particularly useful as it doesnt support GitLab, but may be use in addition to a git driver, if one is created.

[jayvdb]

When we do switch, there is a jinja template loader, https://github.com/althonos/jinja2-fsloader

[jayvdb]

We could take the Hyde approach and have one custom driver for git, and use pyfs for everything else, and transparently wrap the git repo in a pyfs layer.

[jayvdb]

Created merlink01/fs.github#9 to see if they are interested in GitLab/etc support.

If not, we may need to create a fs.IGitt ourselves.

[chfw]

do we want to expose pyfilesystem2 syntax to our users(downstream projects)?

[jayvdb]

Optional, but yes. Maybe even recommended where a value might be ambiguous without a pyfilesystem2 prefix. It allows users to host their config & templates in any filesystem-like provider, and use a pyflesystem2 URL to tell moban where it is. This is a natural way to say "moban supports any data/file host" without adding/maintaining drivers for all of them. And we inherit the naming conventions of pyfilesystem which prevents any conflicts/ambiguity, and means moban users can use pyfilesystem docs for precise semantics of the URLs. Our users get new file hosts each time pyfilesystem core includes a new one.

The most obvious "win" is that if we can get a git driver for pyfilesystem, we dont need to create special code for mercurial and other VCS: anyone who wants those can create their own pyfilesystem driver.

The standardisation inside moban codebase will also be beneficial. It's support of PyPI packages would be a simple wrapper that can be creating using the core pyfilesystem2 drivers.(I expect it would be an internal driver, not a separately pypi published one).