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

Alternative Solution to Sparkleshare #2005

Open
macedd opened this issue Feb 5, 2024 · 3 comments
Open

Alternative Solution to Sparkleshare #2005

macedd opened this issue Feb 5, 2024 · 3 comments

Comments

@macedd
Copy link

macedd commented Feb 5, 2024

I've been struggling to make the app work for the whole day. I was able to build it for Linux, but MacOS version I could not. The whole app is outdated, unfortunately.

After giving up my options, I decided to look for alternatives. @hbons mentions dvcs-autosync but it is too outdated at the moment.

The best solution so far might be to integrate git-sync with fswatch for the automated updates.

In my environment, I'm testing the following setup

# Set git config relevant to git-sync
git config --bool branch.master.sync true
git config --bool branch.master.syncNewFiles true

# Start fswatch and pass changes to git-sync
fswatch --exclude=.git -o ~/Sparkleshare/github.com/repository | xargs -n1 -I{} git-sync
@uenz
Copy link
Contributor

uenz commented Feb 8, 2024

I did a few updates a while ago. Unfortunately they were not merged. I’ve a working windows and Mac version, no Linux at the moment.
You can give it a try: Builds on GitHub

@mbg-unsw
Copy link

Have you looked at git-annex and git-annex-assistant? https://git-annex.branchable.com/assistant/

In my experience on Linux it works but can be a memory hog. Web pages says it works on OS X.

@kjyv
Copy link
Contributor

kjyv commented Mar 24, 2024

@macedd It builds just fine for me on macOS on the command line as described in the documentation, although opening the solution with the current Visual Studio Mac does not seem to work (that should be fixed).
But maybe you could rename the ticket to something like "issues when building on macOS" and describe them in more detail? That would at least be relevant for this issue tracker, instead of asking for replacement projects. This is an open source project after all and anyone can take up bugs from here to fix them, maybe fork the whole thing etc.

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

No branches or pull requests

4 participants