FrenchyJiby (u/FrenchyJiby)

FrenchyJiby commented on Podman Desktop celebrates 3M downloads podman-desktop.io/blog/3-... · Posted by u/twelvenmonkeys

sofixa · 6 months ago

All I can think of with this is...

_But why?_

I mean, if you have one container service only and everything else is ran by systemd, then it makes sense to keep it easy. But other than that, why? Systemd's syntax and docs aren't particularly friendly or easy, so it's not like you gain in simplicity vs just running docker/podman-compose, or even a lightweight orchestrator like Nomad.

FrenchyJiby · 6 months ago

I enjoy:

- seamless container logs (journalctl), no weird separate logger

- service start/stop/enable-at-boot no weird separate command

- integration with system/user slices, triggers, cronjobs (timers), exposing containers as first class commands overall!

Basically it's worth seeing container services work with non-container services.

If you don't like systemd, or have no stake in it, sure, have fun without it, but it's definitely added value when you're running services, and want to start containerizing some of them without abandoning all the good tools you are using in favour of docker logs docker run etc.

FrenchyJiby commented on Podman Desktop celebrates 3M downloads podman-desktop.io/blog/3-... · Posted by u/twelvenmonkeys

miroljub · 6 months ago

Does anyone actually use Podman on its own merit?

The only use case I encountered is people who want to run Docker without root or admin permissions and use Podman just as a drop-in replacement.

FrenchyJiby · 6 months ago

Podman has good systemd integration, in the form of quadlets.

It lets you define a systemd job with some custom syntax and run it as a systemd service, and even stretches to allow some form of kubernetes YAML to be run as local (single node, rootless) containers!

Real nice.

See previous presentation on HN: https://news.ycombinator.com/item?id=43456934

FrenchyJiby commented on .gitignore Is Inherently Sisyphean rgbcu.be/blog/gitignore/... · Posted by u/RGBCube

davydm · 8 months ago

Cool post.

I highly suggest using templates from https://github.com/github/gitignore for your project as they tend to include a lot of files commonly found in them - eg .idea folders and so on.

FrenchyJiby · 7 months ago

Yes-anding this to say:

For per-user gitignore, one can set the following config in ~/.gitconfig:

    # System-wide gitignore file
    # To avoid in-repo repetition for system-specifc garbage files
    [core]
        excludesfile = ~/.config/git/gitignore

Then your file at ~/.config/git/gitignore can be a normal format, and not need to be stored in repo. Perfect for system files (.DS_Store...) or editor swap files etc.

FrenchyJiby commented on Musk-Trump dispute includes threats to SpaceX contracts spacenews.com/musk-trump-... · Posted by u/rbanffy

iamleppert · 9 months ago

I was waiting for this comment! What innovations have come about in the last 20 years of the human space program? Everyone always makes this claim but never can name a single one, or brings up unrelated things like the heat tiles on the space shuttle. What kinds of developments could not have been done with autonomous payloads?

FrenchyJiby · 9 months ago

Not an expert, but it seems NASA holds a few magazine publications for just that, it must come up often.

One VERY on topic is "ISS Benefits for Humanity", which shows why the ISS benefits everyone.

See edition 2022: https://www.nasa.gov/wp-content/uploads/2022/09/iss_benefits...

Seems from the table of contents, it breaks down to: earth observation, microbiology in microgravity, human health research, inspiring younglings, new physics, and "growing the low-earth economy".

Then broader there's a yearly one called Spinoff that points to the technology transfers, but that's not just from human flight, but from all NASA-funded work.

See last few years' edition: https://spinoff.nasa.gov/spinoff/archives

FrenchyJiby commented on Aider: Using Uv as an Installer simonwillison.net/2025/Ma... · Posted by u/anotherpaulg

FrenchyJiby · a year ago

I really want to love uv: It's a hair away from being perfect, they just have to find a solution to the "poetry version" (bump) problem = https://github.com/astral-sh/uv/issues/6298 (Work in progress, last I heard!).

Once we have a way to get package version bumps, I can finally leave poetry for the speed of uv!

Of particular interest to me, uv has "workspaces", perfect for monorepo-like sub-packages: useful for plugin-based workflows where you may want to keep a few independent plugins in one repo.

FrenchyJiby commented on Terraform Config Root Setups resourcely.io/post/10-ter... · Posted by u/carty7

iliaxj · a year ago

We use a single codebase to deploy to multiple environments. The setup looks like this:

  - root
  -- /envs
  --- / dev.tfvars
  --- / prod.tfvars
  - main.tf

When it gets deployed by the CICD, the right tfvars file is passed in via the -var-file parameter. A standard `env` var is also passed in, and used as a basis for a naming convention. Backend is also set by the pipeline.

The rationale here is that our environments should be almost the same between them, and any variations should be accomplished by parameterization.

Modules are kept either in separate repos, if they need to be shared between many workspaces, or under the `modules` subfolder.

FrenchyJiby · a year ago

Yeah I'm confused why none of the solutions presented deploy the same TF across the environments: Surely if you have dev vs prod, 90% of dev infra is also needed in prod?

Then sure sprinkle a few per-env-toggles `count: 1 if env == dev else 0` (or whatever the latest nicest way to do that is today), but it feels weird to have to set up an artificial TF module around our entire codebase to be able to share the bulk of the code?

FrenchyJiby commented on Ask HN: What commit message conventions do you follow? · Posted by u/rishikeshs

FrenchyJiby · a year ago

I've written mine up as I've noticed I was repeating myself a bit once my opinions stabilized.

See https://jiby.tech/post/my-git-worfklow/

FrenchyJiby commented on Hurl, the Exceptional Language hurl.wtf/... · Posted by u/todsacerdoti

tgv · 2 years ago

Multiple products sharing a name is unavoidable. Github had 90,000 unique repositories in its first year. If each had to have a unique name, it would almost have exhausted the English dictionary. In 2018, it reached 100 million repositories.

FrenchyJiby · 2 years ago

Note that the specific naming of hurl.dev is not random: hurl is a wrapper for curl, where the requests are stored in a plaintext file.

So hurl.dev didn't roll dice and got hurl, but consciously got a close sounding word.

In that sense, that makes one claim over the other a little more valid, in my mind, though you're right that clashes will have to occur.

I did get confused extra hard by the url = hurl.wtf, when hurl.dev is so close yet about different topic.

FrenchyJiby commented on I'm tired of makefiles dmitryfrank.com/blog/2016... · Posted by u/fanf2

willcipriano · 2 years ago

I like makefiles not as a build tool but as a way to put better ui around long difficult to type/remember commands on the repo

make up

make down

make clean

make upgrade

make migrate

Easier than having to think about it

FrenchyJiby · 2 years ago

Totally, I describe it as "shorthand for most used commands + lightweight documentation".

I made an entire presentation about this[1], trying to sell it to work mates.

[1]: https://jiby.tech/presentation/makefiles/makefiles.html

FrenchyJiby commented on Prefer table driven tests (2019) dave.cheney.net/2019/05/0... · Posted by u/PaulHoule

boxed · 2 years ago

In Python land this is called "parameterized tests": https://docs.pytest.org/en/7.1.x/example/parametrize.html

I think the author might want to look into mutation testing or property based testing to get to something closer to fully testing stuff.

FrenchyJiby · 2 years ago

Yes, and going further, I think you'll enjoy the amazing lib Pytest-cases[1] which enables naming the parametrized tests, listing them not as decorators but as separate functions/classes.

See the europython video intro: [2], or as slides[3]

[1] https://smarie.github.io/python-pytest-cases/ [2]: https://www.youtube.com/watch?v=QTyfr2UNR98 [3]: https://ep2021.europython.eu/talks/649sqwq-powerful-tests-an...