4 ms·

What about git makes you uncomfortable? I saw that you didn’t want to use a 3rd party provider, but why not stick a git repo on your VPS (which you are trustin

by e28eta 1y ago

What about git makes you uncomfortable? I saw that you didn’t want to use a 3rd party provider, but why not stick a git repo on your VPS (which you are trusting with your data today) and use that to coordinate syncs between your client devices?

williamsss 1y ago
Made a comment in the thread explaining this https://news.ycombinator.com/item?id=44023090 https://news.ycombinator.com/item?id=44023090 I expect my PKMS to evolve and wouldn't rule out a self-hosted Git server if I find it's a better option long term.
- tasuki 1y ago
  > wouldn't rule out a self-hosted Git server I don't think you really get it. Git is distributed. There's no need for "a git server". You already have a machine on which you host the SQL database, you can just use that as yet another git remote.
- e28eta 1y ago
  Thanks for the reply. I do agree with sibling comment from tasuki that I think you’re missing the simpler solution of plain git repos to solve “owning your own data in a future-proof manner”. If you’re not trying to coordinate work among multiple people, and aren’t trying to enforce a single source of truth with code, you don’t _need_ “git server” software. You just need a git repository (folder & file structure) in a location that you consider to be your source of truth. I’m not trying to convince you to change it now, especially if you’re happy with what you have, but I would suggest reading some (or all) of https://git-scm.com/book/en/v2 https://git-scm.com/book/en/v2 I think the first ~4 subsections of chapter 4 cover what I & tasuki were suggesting could be sufficient for you. If you’re the type of engineer to read through the code of your data storage layer, I think you’d find Chapter 10 (Git Internals) interesting, because it can demystify git. I enjoyed the whole book. As with any engineering project, I see lots of questions about your choices, and I applaud you for sticking around. I would make very different decisions than you, based on your stated priorities, but that’s okay.
- hashhar 1y ago
  You only really need SSH access on a box to use it as a git remote - no server needed. I learnt this quite late and was not obvious to me so hope it's helpful for you too.

by e28eta 1y ago

williamsss 1y ago

Made a comment in the thread explaining this https://news.ycombinator.com/item?id=44023090 https://news.ycombinator.com/item?id=44023090 I expect my PKMS to evolve and wouldn't rule out a self-hosted Git server if I find it's a better option long term.

tasuki 1y ago
> wouldn't rule out a self-hosted Git server I don't think you really get it. Git is distributed. There's no need for "a git server". You already have a machine on which you host the SQL database, you can just use that as yet another git remote.
e28eta 1y ago
Thanks for the reply. I do agree with sibling comment from tasuki that I think you’re missing the simpler solution of plain git repos to solve “owning your own data in a future-proof manner”. If you’re not trying to coordinate work among multiple people, and aren’t trying to enforce a single source of truth with code, you don’t _need_ “git server” software. You just need a git repository (folder & file structure) in a location that you consider to be your source of truth. I’m not trying to convince you to change it now, especially if you’re happy with what you have, but I would suggest reading some (or all) of https://git-scm.com/book/en/v2 https://git-scm.com/book/en/v2 I think the first ~4 subsections of chapter 4 cover what I & tasuki were suggesting could be sufficient for you. If you’re the type of engineer to read through the code of your data storage layer, I think you’d find Chapter 10 (Git Internals) interesting, because it can demystify git. I enjoyed the whole book. As with any engineering project, I see lots of questions about your choices, and I applaud you for sticking around. I would make very different decisions than you, based on your stated priorities, but that’s okay.
hashhar 1y ago
You only really need SSH access on a box to use it as a git remote - no server needed. I learnt this quite late and was not obvious to me so hope it's helpful for you too.