git-from-the-bottom-up VS ledger

Very tangential:

Gerrit also stores some of its configs in a git repo. I was setting up a new instance, but couldn't get Admin permissions because the way my auth front-end didn't play well with the docker image's assumptions.

Gerrit already does a lot of its work via non-standard references. For example, you don't push to a branch, `refs/branches/foo`, you push to a separate `refs/for/foo` namespace that creates the review.

Similarly, Group config is stored in the All-Users git repo [1], but in references created after a UUID, in `refs/groups/UU/UUID`.

I ended up having a to exercise the plumbiest of plumbing commands [2] to create a new commit from scratch (from a tree, from the index, from blobs), to update the group ref to add myself to the Administrators group (this, of course, requires a local shell and permissions on the Gerrit host). It was a great way to exercise what I had learned in Git from the Bottom Up [3]

[1] https://gerrit-review.googlesource.com/Documentation/config-...

[2] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects

[3] https://jwiegley.github.io/git-from-the-bottom-up/

You won't have to put your entire life on break in order to understand the fundamentals of git and why it works the way it works. Going through https://jwiegley.github.io/git-from-the-bottom-up/ and really understanding the material will take you a couple of hours at max, but will save you a lot of time in the future.

Wanting to understand things before using them is hardly elitism, not sure why you would think that.

Just like you probably don't want to fix bugs without understand the cause, it's hard to use a tool correctly unless you know how the tool works.

If that's too dense, read https://jwiegley.github.io/git-from-the-bottom-up/, which is basically the same as chapter 10 at a slower pace.

Git From The Bottom Up : https://jwiegley.github.io/git-from-the-bottom-up/

here's one tutorial https://jwiegley.github.io/git-from-the-bottom-up/ from bottom to top, it explains the building blocks then the operations, it might help (again, depending on your brain)

I can recommend https://jwiegley.github.io/git-from-the-bottom-up/ and of course https://git-scm.com/docs/gittutorial (also gittutorial-2).

It's not a single digit minute read, but to me "Git from the Bottom Up" was what really made me understand git a long time ago.

https://jwiegley.github.io/git-from-the-bottom-up/

git's the kind of tool where understanding how your commands operate on the underlying data structures will probably make it a lot easier to use efficiently. (And they're beautifully simple despite how powerful and flexible they are)

As a tool you might be using for hours per week for a few more decades, it's worth the investment going beyond the "in x minutes". I tend to provide both to juniors.

Obligatory: https://xkcd.com/1597/

I thought this was about https://github.com/ledger/ledger and was so confused why they'd be on NPM.

Pretty shitty of them to pick the name LedgerHQ after Ledger has already been used for years.

as far as the ledger-cli google groups [1] go, they seem to think it is a proper journal file. It has been fairly tested with OFX imports (https://github.com/ledger/ledger/wiki/OFX-Import) as well bank autosync (https://github.com/egh/ledger-autosync).

In fact, someone also wrote a book on this - https://leanpub.com/personal-accounting-in-ledger/

I will defer if you are indeed building your own competing tool in this space which is better, but holding to the original point of my request - maybe it will be incremental to support your format if ledger-cli format is supported today. versus not supporting any disk format (or inventing a new one).

[1] https://groups.google.com/g/ledger-cli/search?q=double%20ent...

If there are BigCapital devs here, could you please maintain compatibility with https://github.com/ledger/ledger

The best I found is a file from 13 years ago here https://github.com/ledger/ledger/blob/master/doc/grammar.y

Very happy to see this release. On macOS Ventura installed via brew, 3.3.0-20230208 is acting like it was built without support for encrypted ledgers. A later commit that gives more info when passed the -v flag would answer the question, but of course I am on 3.3.0 without this commit! So does anyone know? thanks

There is also ledger and ledger-import, together with other tools like >, ledger-autosync and emacs.

Finally... I'm in the early stages of building some budgeting / finance software that uses Ledger-compliant files to store the financial information.