privatize VS api-playground

I partially encrypt/decrypt a file based on the presence of special HEREDOCs (ie <The tool is still a WIP as it isn't portable between machines -- https://github.com/higgins/privatize

more on it here: https://encapsulate.me/writing/Privatize.html

Yes!

I keep a daily log tracked in git. All of it public although some information is encrypted with my privatization tool (https://github.com/higgins/privatize).

The log itself is a simple org file but I parse and render it in html here so that I can share important event dates (eg: my wedding) with my family and friends.

Here is what I did yesterday:

ooo, good call out. thanks!

currently i only have one warning in place if I forget to close there heredoc: https://github.com/higgins/privatize/blob/main/index.js#L168

but could add some more error checking. added to TODOs: https://github.com/higgins/privatize/commit/9696f30576897898...

https://github.com/higgins/privatize

When added to a git repo, it will automatically transparently encrypt/decrypt files you want privatized.

For example if you configured your repo to privatize the file `example.txt`, you could write:

```

GitLab team member here.

Maybe you can re-use the script I shared in this comment [0] to query the GitLab REST API to generate an index. I'm a fan of using the API programmatically, and tend to avoid git checkout/grep/etc. inside CI/CD pipelines (works too, everyone is free to choose their way).

Yet again, I love API challenges, so I've created a new script which parses a defined markdown footer for Tags and Due date, and generates an ordered index by due date. I did not know which format you are using, so I made up my own, see the MR description [1] and docs [2].

The script lives in [3] and is a mix of fetching files, parsing content with regex, and generating the index + creating a commit to upload automatically.

A demo overview is shown in [4] with the generated index.md, ordered by due date and linking the files by parsed heading title, file paths, and tags.

Hope it helps, feel free to repurpose, or ping me for questions on the GitLab community forum [5]. My Python code is a little rusty, I am slowly adopting all the 3.x design patterns after many years with 2.x.

I might follow your idea with notes and custom footer parsing. That's a really nifty idea, and helps solve my own chaos :-)

[0] https://news.ycombinator.com/item?id=32155848

[1] https://gitlab.com/dnsmichi/api-playground/-/merge_requests/...

[2] https://gitlab.com/dnsmichi/api-playground/-/tree/main/pytho...

[3] https://gitlab.com/dnsmichi/api-playground/-/tree/main/pytho...

[4] https://gitlab.com/dnsmichi/api-playground/-/tree/main/demo/...

[5] https://forum.gitlab.com/u/dnsmichi/summary