TagSpaces VS sovereign

https://github.com/tagspaces/tagspaces

Either way, will definitely be keeping an eye on your app, it seems ducking cool ;)

TagSpaces – Your versatile file organizer (version 50504): organize, tag and browse your files, photos and documents

Take a file. Add [awesome] to the name. There. You've tagged a file, and you can search for it with your desktop search / fzf / etc. Switch system, copy it anywhere, it works. You can do this by hand. Or, if you like clicks and drag-n-drop, use TagSpaces. Or, use tss.

The UNIX filesystem has traditionally been a graph for ever. I haven't looked at details for a couple of decades, but definitely all UNIX/POSIX/Linux filesystems operate on a graph model.

A distinction I used to make when I was teaching this stuff: on your filesystem tree, on Unix names (labels) are on the links (arrows), while on DOS/Windows names are on nodes (boxes).

If you want to explore a tag-based system, take a look at https://www.tagspaces.org/

The quickest workaround – and the most satisfactory one to boot – is to abandon Windows Media Player. Use a digital asset management app like TagSpaces.

TagSpaces: TagSpaces is a cross-platform tagging and organizing tool that can help you tag and manage your files and folders. It supports various file formats and can be used with local and cloud storage providers.

If the naming convention is different, or you'd prefer to go the tagging route, tagspaces may be your best bet. It can use standard tags in the file, or a sidecar file (file with the same name, but different extension next to the original file) to keep tags with the file.

Agreed. Why not use the filesystem as the database that it is? Modern filesystems support tags or extended attributes that could be used to implement tags. Failing that, just encode tags in the filename. Document management tools could then use the filesystem as the source of truth.

I find the fundamental problem with this sort of server setup script/config management is that they inevitably get quite personal. Nobody really wants to use another devs and when you try to allow for a lot of customisation they tend get byzantine and complex.

That said I still think it's worth sharing. If nothing else we can all usually cherry pick nice ideas from each other.

I had an entirely private set of Ansible roles I'd cobbled together that I started to put in a more shareable state a couple of years ago. It has little overlap with what you're putting together, but I do think you might find the way it separates personal Ansible config and the main project roles into separate directories (and thus different git repos) useful.

I really need to dust off my project and get it to a releasable state this year [momod](https://github.com/adrinux/momod).

I assume you've come across the many similar projects like [Sovereign](https://github.com/sovereign/sovereign), [Mistborn](https://gitlab.com/cyber5k/mistborn)

You could also check out the Sovereign project on github which automatically sets up a home server including xmpp serivce.

Shoutout to Sovereign[1] nice ansible project to automate most of this kind of home setup

[1] https://github.com/sovereign/sovereign