My my

It does bring all the boys to the yard

Jokes aside, I do keep some harder to remember stuff written down in a README.md in my repo, but mainly most things are undocumented

Simpsons did it!

Lucky until he wants to sit down!

We’ll surely avoid scurvy if all eat… an orange

Better safe than sorry

It’s between Sigint and Snake via radio (I just removed the sigint parts of the convo) in MGS3

I was just looking at it, and suddenly I got this irresistible urge to get inside. No, not just an urge - more than that. It was my destiny to be here: in the box!

And then, when I put it on, I suddenly got this feeling of inner peace. I can’t put it into words. I feel… safe. Like this is where I was meant to be. Like I’d found the key to true happiness.

You should come inside the box. Then you’ll know what I mean.

Happy 100th!

Your files are now being placed in /opt/wireguard-server/config, not in the folder you have the docker-compose file, can you see them there with ls?

If you want thee files to be created in the directory where your compose file is you should change the path in the volume like so (notice the ./ on the left side of the colon):

- ./config:/config

Volume paths are specified with local-path:container-path, so changing the part before the colon specifies where your files are, and changing the part after the colon specifies where the container sees the files

Hope this makes sense, but I just woke up, so it might not

This specific use case? To make a meme, mainly ¯\(ツ)/¯

As for the components: Parsing comments have been used for stuff like type hints / formatting / linting, tho generally not at run time (afaik).

The tooling for finding out where something is called from can be used to give a better understanding of where things go wrong when an exception happens or similar, to add to logs.

I would say that in general you don’t need either functionality except for certain edge-usecases

The add() function (that is available in the source code) basically uses some built in debugging tools to find out where in the code the function is called, and then parses the comment from the file and uses it for adding stuff.

I’ve never tried (becuse why would you…) but something similar can probably be built in any interpreted language

It’s not something Python does by design

Doo doo doodoo doo doo

That cursor, though…

I’m in the no-bucket, but instead i spend time on issues, helping the community and sometimes code contributions to self hosted projects instead.

This is not taken into the account of the question, however, but should be considered as contributing.

(I also consider donating to be contributing.)

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Nah thanks, up arrow hasnt failed me yet