Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate Customisation Sync into a dedicated plug-in. #536

Open
vrtmrz opened this issue Nov 11, 2024 · 2 comments
Open

Separate Customisation Sync into a dedicated plug-in. #536

vrtmrz opened this issue Nov 11, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@vrtmrz
Copy link
Owner

vrtmrz commented Nov 11, 2024

I have decided to separate Customisation Sync into a separate plugin!

This way, Self-hosted LiveSync will be more lightweight with Overriding config folger settings and Hidden file sync.

Besides, the ConfigPicker can be dedicated to comparing and selecting files from local config folders.

I realised that it is better to keep it a simple function so that there is less room for suffering.

And there are some bonuses! Non-LiveSync User also be able to use the feature.

Only we have to do is try to keep usability to realise it.

@vrtmrz vrtmrz added the enhancement New feature or request label Nov 11, 2024
@vrtmrz vrtmrz self-assigned this Nov 11, 2024
@vrtmrz
Copy link
Owner Author

vrtmrz commented Nov 14, 2024

First of all, I made it. Indeed, it was almost a complete rework, but seems to be working well.
I hope you will give it a try!
If it works well, Customisation Sync will be approaching its sunset, leaving behind its legacy of knowledge and dedication. At least I have a good feeling about it.

(Besides: I have realised and gradually become concerned about the instability of Hidden file sync. We are supposed to be dependent on it, but I am confident it will improve soon).

Usher

@vrtmrz
Copy link
Owner Author

vrtmrz commented Nov 14, 2024

I have found that Self-hosted LiveSync will miss files that have been deleted and immediately created on the same timestamp! This bug make the Usher unusable! I will fix it later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant