guide VS bocker

Either way, you're going to need to follow either this guide: https://discordjs.guide/ to get you started with DiscordJS (which is IMO the easiest language to learn it in, also usually the most up-to-date). If you're not into reading (which is not in the slightest optimal if you wanna learn how to program) then there's probably some DiscordJS tutorials online. Just search DiscordJS tutorials on youtube and you're sure to find one.

https://discordjs.guide is the "official" discord.js guide, you'll find a command handler there. I don't know if it will be more or less complicated than the one youre using.

Also do some debug logging to show that the target it actually being read correctly. But moving to slash commands may work better. There is a really good guide out there. DiscordJS Guide

Well, I recommend you JavaScript, it is good for beginners and there's a lot of content on internet. Once you understand and practice the basics, you can use discord.js to write your bots. They have a guide website if you are interested.

but I use the official discord.js guide cooldown example: https://github.com/discordjs/guide/blob/main/code-samples/additional-features/cooldowns/index.js

https://discordjs.guide has a good tutorial on slash commands

Official guide from the peeps who made DJS: https://discordjs.guide/

Read the discord js guide (https://discordjs.guide/). The answer to your problem is that it takes many hours for global / commands to register. The reason I still recommend the guide is because it gives you an introduction to many of these topics. It's better than a lot of youtube video tutorials and such.

A (joke?) one-liner I came up with while thinking about solutions to centralized container management across multiple SSH hosts. Shame on me.

The name is inspired by bocker [0], albeit this doesn't re-implement docker-compose in bash, I found it to be fitting enough.

I'd love to see someone come up with a smarter and/or shorter way to do this.

[0] https://github.com/p8952/bocker

When I did a talk about docker I also wanted to show a bit of what it does under the hood without going through all the layers and without too much details. This ~120 lines of shell script is really good in providing just an intro into what's needed for containers: https://github.com/p8952/bocker/blob/master/bocker

i tried it and like the concnpt, but until it can be launched via a systemd userspace service (without previously manually booting it) among other problems i will keep using docker (or bocker)

> But you couldn't reimplement podman in a few hundred lines of code.

You don't even need a few hundred: https://github.com/p8952/bocker

And then there's 'dokku' which IIRC, started as a bash version of Heroku.

> Not all ideas have the same quality.

They really do. I've heard all kinds of things in my career, but almost none I would want to dedicate a portion of my life building. Not because they are bad ideas or won't work, but because of the person with the idea or it just didn't interest me. Those people went on to be moderately successful (like hundreds of millions worth) but I'm glad I wasn't on that ride.

Bocker is in this same category...docker clone in bash that's helpful in seeing what's really happening underneath with nsenter, namespaces, network bridging, cgroups, etc.

https://github.com/p8952/bocker

Docker implemented in around 100 lines of bash: https://github.com/p8952/bocker

This is the most mindblowing example for enterprise security teams that think Docker is a new threat on a single tenant Linux host.

No, buddies, all this stuff is already there. If you were fine with your visibility before*, you're still fine. Go find a real problem while we play with our developer dopamine.

* NARRATOR: They shouldn't have been.

Bocker[1] does a reasonably good job of showing the value of Docker was mostly in Docker hub.

[1] https://github.com/p8952/bocker

There is a cool project I've seen called "bocker" (https://github.com/p8952/bocker) which is something of a proof of concept of implementing Docker with bash, which speaks a bit to how Docker is indeed in many ways an amalgam of lower level primitives (such as chroot as you mentioned). Pretty neat!