A Workflow/Process question around local vs github syncing

I use Safari as my daily browser. For a week or so I’ve been using LogSeq in Safari successfully and syncing to Github.

I’d prefer to use the new local file option, but that is not supported in Safari, so I cloned my repo and opened it locally using Chrome. So far, it’s working fine. And it’s great being able to also edit the files using Emacs locally!

But, I’m still “connected” to the Github repo in Safari. And, I’ve logged into LogSeq via Github in Chrome also.

This means in Chrome I have two graphs/databases, one local, one in Github, but they’re both actually the same repo. I can’t imagine this being a good idea :slight_smile:.

Is there a best way to handle this? For example, I still want to at least read my data in Safari because I have a pinned tab right there while I’m doing other things. But, I’m likely to also edit files in Safari by accident for the same reason.

After all that, I guess my question is: If my goal is to have one, filesystem-based database/graph, should I disconnect completely from Github or is there some reasonable way to have it both ways?

1 Like

After all that, I guess my question is: If my goal is to have one, filesystem-based database/graph, should I disconnect completely from Github or is there some reasonable way to have it both ways?

I don’t think you need to disconnect from GitHub, and it makes sense to have both local file directories and GitHub repos. I guess we can add an option like :repo/local-disabled so that some repos don’t have to loaded for Chrome usage. I need more time to think about it.

Thanks. I’m just trying to get my head around how things are meant to work and hoping I don’t break anything :).

1 Like

Yeah, it’s not good to have multiple tabs to automatically push to the same repo on GitHub, it can easily result in empty commits, conflicts, and even data loss (those are tricky bugs that we’re fixing now).

2 Likes