Question about your working process
mendax1234 opened this issue · comments
After reading your document about logseq sync . Can l summarize the whole process into pushing your local to a github repo (public or private ? l don't know, l prefer private but l don't know whether it is supported) and clone it on your iPhone (l use iPhone so l only talk about iPhone here) ? Is that right? Besides , it seems that the working copy needs the pro version to do it. That's not user friendly.
Private repo will be just fine, like I mentioned in the readme.
And yes, you need WorkingCopy Pro for it. I'm not sure what you mean by user friendly, but I did give you the reason why you should pay for it.
Btw, If you're a student, I also mentioned that you can apply for github student pack for one year of free WorkingCopy Pro.
I'm not sure what you mean by user friendly
l mean that someone may noy want to pay for it.
Btw, If you're a student, I also mentioned that you can apply for github student pack for one year of free WorkingCopy Pro.
How to do that? Is it in the Github student pack? Can you provide a link?
Thanks.
--Daniel
- I don't think that how user friendly normally means. There's not thing I can do if you don't want to pay for it.
- It's mentioned in the section, please read it thoroughly. Or github student pack.
l can't find the page to log in on my iphone.
What do you mean...?
You have to sign up for it.
Emmm, l am a student now and l already have the pack , but l don't know where to log in on my working copy on iOS
Thanks! l have successfully logged in. And l still have some little questions. Can l use it until l am not a student? Or , it only has one year time?
As long as you're a student, you can apply it again after it's expired.
Thanks , l am still a little confused about its using on Windows.
If l already have a logseq library where my notes are stored, l should use enter the folder and type git init in cmd to create a git? After doing that , l should upload it on my github?
Why not just copy all the notes to the new folder you just cloned? And link the new folder as a new graph in logseq?
Please do some research about git first, I have already provided some simple material in the readme.
l think l can't use git init in my original logseq graph.
You can just edit the file name of a random txt file.
Can logseq push the commit to the repo automatically?
That's why I provided the pre-commit and post-commit files.
Thanks! It seems that after l copy these files to my ./git , l still can't push automatically.
Make sure you follow EVERY steps I wrote in the workflow.
Many have successfully adopt this workflow without much trouble, I can't help you debug everything.
I can only answer specific questions.
l want to make sure that if l want to push the commits automatically, l should copy and paste the two files in your ./git-hooks to the hook folder in my ./git . In that way , l can achieve pushing automatically, is that right?
Ys, if you do everything right than you can push the commits automatically.
l have double checked and find nothing wrong with it. Can you help me see if my all my files in the hook folder are right?
ys, that's the folder you put pre-commit and post-commit.
Have you use git bash to manual push it without errors?
Yes , l can push it successfully.
l think the problem exists now is that l can't push the commits automatically .
Change the main in this line to master.
I have done this but l still can't push the commti automatically. Do l also need to close the logseq or the Github Desktop that l use?
It seems that it works now but l have to wait a long time for it to push the commits automatically to the github. For example , l need to wait about 20 minutes. That's not so good.
What's the interval you set in here or in config.edn?
l think the seconds of the git auto commit is too long , but l don't know which one fits me better since l find that once l close the logseq ,it won't commit automatically. So , l suggest adding a function that auto commit once closing the window of logseq.
You can submit a feature request to logseq team.
Sure l will!
And please close the issue if you got nothing to ask.