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

Better safe than sorry

Not yelling, but pointing out, to people who also dont math, that if we assume $10 per 10k emails (or $1 per 1k, for simpler math), that’d be $84 for 84000 emails in a month, so you need to add another 0 to the figure (ie 840k emails in a month)

I’ve mainly gotten false positives, myself. When I’ve added another subdomain or something and the certificate gets set up differently, so then you get 2-3 emails saying domain X will expire, but if you connect to the url you see it has 80+ days left. Setting up your own monitoring solution is probably long overdue for myself, and it’s nice I’m getting forced to do it, in a way

I set up uptime kuma to also monitor certs this week when I got the reminder email about them stopping the email warnings, been using it for some time for uptime monitoring (mostly to see if some auto docker image update screws up my services) and the notification parts has worked nicely for that, so I’m also assuming it will work nicely for the certificates

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

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.)

Nah thanks, up arrow hasnt failed me yet

Yeah, or Shelfplayer

I’m holding off on trying Plappa until they add session support, since I like the stats, heh.

Tho I do have a Testflight spot for the ABS app, as well.

I do want to try Plappa, though! I really like the paperless-ngx app (Paperparrot) from the same developer

The ABS app is also still in beta on iOS, so unless you are tech savvy enough to either sideload or try to get in on one of the windows when users are booted from the testflight beta, you are going to have to use one of the 3d party apps.

Prologue just seems to do many things nicely, and user experience seems very important to the developer, so there is a huge crowd that swears by the app.

I know you wrote /s, but this has basically nothing to do with the tech of microservices, and more to do with internal politics.

Switch the ”user microservice” to ”birth date is not indexed in the database and i have to reach out to the database handling team” and you are in the same situation

Tbh mostly microservices solves two issues for me:

1. You can scale resource-heavy operations without an impact of scaling everything else.
2. You kind of ”force” people to keep things contained, instead of making everything interdependant. Which helps containing issues with updates to certain functionality to only have an impact on that functionality.

You could do #2 in a ”monolithic” setup as well (by doing modules or libraries or something), it just never works out that way in practice

Imo they do not add problems, but they do exchange some problems for other problems.

Fix tpyo

https://imgur.com/a/wOgZwpn

Does this sync stats for downloaded books ok?

EDIT: seems like not yet, https://github.com/LeoKlaus/plappa/discussions/15

Trust me, you do not want enthusiastic double gonorrhea.

I second this comment!