I think I found some repos here: https://github.com/search?q=in:description+Sha1-Hulud&type=r...

> How would you package this inside a Git repo?

There are many ways to do that. Start with a simple repo and spin up a VM instance from the cloud provider of your choice. Then integrate the commands from this article into a cloud-init configuration. Hope you get the idea.

Thx. The only problem I have with litestream binary is ~31Mb !?

This why I prefer to take backup stuff in a side container, eg: https://github.com/atrakic/gin-sqlite/blob/main/compose.yml

As a side note, you might consider revisiting your dockerfiles and skip litestream build steps, eg. in your final stage just add line like this:

COPY --from=litestream/litestream /usr/local/bin/litestream /bin/litestream

>Thx. The only problem I have with litestream binary is ~31Mb !?

Where are you seeing a 31 MB binary? Latest releases are 10-11 MB.[0]

>This why I prefer to take backup stuff in a side container, eg: https://github.com/atrakic/gin-sqlite/blob/main/compose.yml

Yeah, I agree that's cleaner, but once you're dealing with multiple containers, it's a big step up in complexity, and you can't do the simple install on places like Fly.io and Lightsail.

>As a side note, you might consider revisiting your dockerfiles and skip litestream build steps, eg. in your final stage just add line like this:

>COPY --from=litestream/litestream /usr/local/bin/litestream /bin/litestream

Ah, thanks! The litestream Docker image is new as of 0.5.0.

[0] https://github.com/benbjohnson/litestream/releases

man chattr

I don't mind json outputs, but pls keep cli options as low letters, eg.: 'kubectl get pods -o json'.

.

    --json

it's one character shorter than

    -o json

Why is that important?

> The file systems of Unix machines all have the same general structure. [...] Note the obsessive use of abbreviations and avoidance of capital letters; this is a system invented by people to whom repetitive stress disorder is what black lung is to miners. Long names get worn down to three-letter nubbins, like stones smoothed by a river.

-- Neal Stephenson, In the Beginning Was the Command Line (Ch. 14), 1999

https://steve-parker.org/articles/others/stephenson/oral.sht...

Mixing case in a case sensitive environment is unnecessarily confusing and annoying.

Xunit offers several methods: https://xunit.net/docs/shared-context

Sounds complicated. What object storage you use? If on aws, 's3 sync' might help.

S3, yes. Litestream doesn't store the backup as a single DB file - rather, as snapshots and WAL segments that are streaming in, so it's unfortunately not so simple.

Thx. Timeline shows attack begun by adding ignore entry in .gitignore file. That is hard to detect nowadays.

So true. Even small children are having same attitude. This is why many of us had to move abroad.

Can't blame the children. They only learn from their parents. If people like you decide to leave, the majority of people with that attitude only grows. In my experience, people don't leave because of political discourse. People leave because of economic situation and lack of opportunities.

Thx. I have extended a bit as a script:

    # !/bin/bash
    ARG1=${1:-'select Date from stdin order by USD asc limit 1;'}
    curl -o - -Ls https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.zip \
  | funzip | sqlite3 -csv ':memory:' '.import /dev/stdin stdin' "${ARG1}"

    # Usage:
    $ ./run.sh 'select * from stdin limit 1;'