💾 Archived View for gemini.mat.services › brief-notes-on-pijul.gmi captured on 2022-04-29 at 12:29:24. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-03-01)
-=-=-=-=-=-=-
i wanted to leave a brief phlog here on my first experiences with the pijul version control system. in my last post, i linked to my gemini-projects repo on the pijul nest. i am very happy with the pijul experience thus far, considering how early the software is in its development. a couple of points:
https://nest.pijul.com/GarettWithOneR/pijul-vscode
given how young pijul is, i will probably start to cross-publish some projects to both git repos and pijul repos, rather than diving all the way in. however, i've been considering self hosting a git server, rather than using gitlab. stay tuned to find out if my laziness wins out again!
i had unknowingly pushed my pijul repo with only top level folders being tracked when this was first published. i was thinking in very `git` terms, hoping that just naming the top level parents during my `pijul add` would recursively add their children. alas, in pijul, unlike in git, folders are treated as valid objects and can exist by themselves without a .gitkeep file. thus, you have to explicitly name the path to each item you want to add to the repository. more of a "my bad" than anything else, but i figured i'd record the experience.