To sum up, I think it‘s doable to create a read/write wev frontend for hydrus server, but I don‘t think it‘s worth the trouble right now. Plus, hydrus server certainly isn‘t written in a way it expects another application to write to the same data source, complicating things further. It‘s only intended as a viewer by design, because actually writing to the same database hydrus server uses isn‘t really feasible without a lot of scaffolding around it that ensures data integrity.Įven then, it‘s imho too likely to corrupt something in the process, the nature of SQLite not really benefitting the idea of multiple concurrent accesses to the database. ![]() This is actually a combination of a server and client application, with the server only copying data from a hydrus server instance (temporarily), and serving it to the client. ![]() That said, hydrus network can certainly be used to exchange data with other people by making the server act as a „central hub“ where data from various sources is gathered.Īs for the tools you‘ve mentioned, since the are all written by me, I‘m going to outline some things. The other direction (uploading the the client to the server) is only ever done on demand and can‘t be automatized. The client downloads the latest data from the server in 24h intervals and the user can decide to keep the data or discard it. ![]() To achieve this, one has to either run their own hydrus network server instance (and share the access to it with other users) or connect to an existing server, mainly the one run by the hydrus network developer himself.Įven when it‘s set up like that, it doesn‘t really sync data. Although I‘m not sure if this was coincidence? :Dįirst, let‘s start off by clarifying that the hydrus network does not by default sync files/tags with anything.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |