Remote server saving and cyncing

[Hyppothalamus]

An online service where you can store and organize your notes in the cloud (or self host the service)

A cloud service to store you markdown notes like onenote or onedrive. edit on the fly and store them somewhere so you can access those files on other devices. this can be handy so you don't have to worry about file conflicts/merge conflicts when using something like git.

Also you can use onedrive for this and marktext but onedrive is not available on Linux.

This can be hosted by the marktext team and be payed for or you can install the service on your own server (this would be free)

What problem does this feature solve?

cloud storing of notes so you can access those everywhere and dont have to mess with git repos and merging remotes in locals.

[mitchcapper]

This is a pretty massive scope increase for the project, especially when you are talking about an inhouse hosting platform. A few items of note:

• Onedrive can be used on nearly every platform including linux, although you may need to use a 3rd party client
• There are many other cloud storage providers that are also crossplatform (drop box, etc) many of these give the option of having the files show up in a local folder, allowing you to achieve most of what you describe without any changes to marktext
• Using a cloud provider or "remote saving/syncing" does not avoid conflicts. In fact the term "syncing" is handling exactly that (as otherwise if you just assume last save is correct there is no need to sync ). While it can minimize this the faster it saves to the cloud, it cannot avoid conflicts. There is always the chance you start editing a file, and someone else does as well, you save and then they save. The only true avoidance is file locks (ie what perforce, etc offered).
• Assuming you would want to use this with things like github it would technically still be making git commits behind the scene so not really avoiding git (even the online github editor does exactly this)
• Your best option to if you desire to avoid conflicts / merging is to commit often and push those commits to the server (while encouraging any collaborators to do the same)
• The only other possibility is if you are expecting the new cloud service product to silently resolve conflicts/merging behind the scene. These things are generally bad ideas and do worse than humans at the same job (along with potentially leading to data corruption or loss).

[cliffr39]

Please add this feature