xomodo

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 ~31Mbm !?

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

man chattr

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

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

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

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.

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;'

Root-module: contains resources, sub-modules, incl. remote module calls.

Stack: deployable with hardcoded tfstate and tfvars configs.

Use 'terraform destroy' during CI phase. That is your pre-prod.

Have you tried emacs org mode?

Interesting approach. Do you mind sharing link with repos?

How could one selfhost localhost.run setup on own wildcard domaine?

Looks like gitpod to me: https://github.com/gitpod-io/gitpod

Im using this IAM policy on ec2 instance profile: "arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore"

For accessing aws ec2 instances behind nat/fw add this lines ~/.ssh/config:

  Host i-* mi-*
   ProxyCommand sh -c "aws ssm start-session --target %h --document-name AWS-StartSSHSession --parameters 'portNumber=%p'"
   UserKnownHostsFile /dev/null
   StrictHostKeyChecking no
   User ubuntu
   LogLevel ERROR
   DynamicForward 5060

Usage: `ssh -i key.pem i-0xxxxxxxxxx`. Last config line can be used for optional proxy browsing.

Try docker contexts: https://www.docker.com/blog/how-to-deploy-on-remote-docker-h...