zufallsheld

It it's text data, yes absolutely inside the docs folder, (maybe an assets subfolder). I didn't have the need yet to put binary data in the docs, but depending on the size it could be in the repo itself or a separate artifact store.

Can't give you any specific help since you didn't specify your problems. However it worked for me in the steamdeck with Proton out of the box.

Without open-source, there'd be no macOS.. So good thing, it exists.

> that is so vague it need to be described as a appearing to imply a call for deportation

This is just bad journalism. Here's what DHH wrote:

> When gypsies take over public spaces, you deport them. This isn't hard, it isn't cruel. It's the basic logic of self-preservation.

https://world.hey.com/dhh/wolves-sheep-and-gypsies-ba44af6a

Probably next generation.

There's a difference between relying on Ai and having any llm generated content in your repos.

This only works if all you care about is the code, like the author mentioned. But if you want to understand what and why the llm did something, or you want it to explain it to you, you're again stuck with the output.

Well, if your cert-manager distributes its own CA, you'd still need the clients to trust the CA, even in k8s.

Because they'll just paste your remarks in their llm, let it correct the text and send it back to you.

> Do you have particular scenarios you’d like the Dockerfiles for or is it just for transparency/ trust (which is a totally valid reason of course)?

The latter. You or an attacker could tamper with the images - however even with the Dockerfiles I can't be sure that the provided images are built from the Dockerfiles, so in the end I'd have to trust you anyway. Also I'd be curious how you build the images.

Thanks for your answer!

Where are these built? Can I see the Dockerfiles? How are they licensed? I get that they are free as in beer, but not libre/FLOSS?

There's a huge difference. With a smartphone I can almost always see that people are filming.

You'd presumely managed that customization with Ansible...

That's the problem.

It's not a new name. Proton is Valve's fork of wine. They also contribute patches to wine.

In corporate most people connect their gitlab to ldap or active directory and thus accounts get created automatically.

> You can't. They can execute arbitrary code. They can download another bash file via Curl and execute that.

Presumably you'd check the code of the action before you include it (and then don't use an action with non-pinned versions). This way you know the action won't execute arbitrary code for this version and won't get any other code because of version pinning.

The docker action you linked is ironic in this regard since every other version in the code seems to be pinned except the one you linked to.

I'm curious: where exactly does it abolish VP roles? I don't see it.

You could use translation tools instead of llms.

Do you know https://annas-archive.gl/isbn-visualization/? And https://search.worldcat.org/? They could probably help you with your dataset.

> I'm cleaning up the code right now and will upload it later today or maybe tomorrow here

Hetzner does not charge any money for their dns service and they have an api.

Presumably a CR can be validated by k8s against a schema and will fail at an early step. I admit I like the operator-pattern.

Same thing for allowing specific sudo-commands. Many tools (like vim or the tools mentioned in the article) would have the same problem when allowing them to be run with root privileges.

With this project (https://github.com/spantaleev/matrix-docker-ansible-deploy/), setting up the bridges gets a lot easier. After the initial setup, upgrading the bridges is painless.

Um, no? It does a tail.

Yeah, and then it probably isn't the developers job to fix that but rather the DevOps engineer's one.

Also saying "the developer has to fix this" is something we tried to abolish when talking about DevOps. What about shared responsibility? Bridging the knowledge gap.

That's the good thing with open source. You can theoretically fork it and remove what prevents you from using Kate as root.

AFAIK because "act", the tool to run github actions locally, was there and there was no need to create something else. Also makes it easier for people to switch from github.

Also see https://docs.gitea.com/usage/actions/design

Well, yes. In this project where I needed to do this, we thought about removing the pipeline completely and replace it with something custom made. But as always: gitlab worked and there was no immediate need to replace it.