mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#sysops

1 Beitrag1 Beteiligte*r0 Beiträge heute

I finally figured out how to automate a certificate request on #Windows that also requires the csr to be signed by a user certificate. Man alive, it should not be that difficult.

As far as I can tell, certreq has no ability to do this natively, so I ended up using certreq to generate the initial csr, then leveraging the COM object to sign it, then back to certreq again for the actual submission/ acceptance.

If you know of a way to do this easier, please let me know!

Been doing good shit lately - building clustered server stacks for some of the world's greatest corporations.

I've been doing Bash programming for over 20 years, long before Puppet and Ansible came along, so I never really got into those technologies. I gave them a chance, but I prefer having full control, access to sources, and flexibility in my work. That's why I'm not a fan of the previously mentioned tools - or things like Tailwind and Docker. I love building my own tools and frameworks.

#Bash#Servers#SysOps
Fortgeführter Thread

The job of #WebSocial is put squarely in the lap of companies that do #WebDesign and #SysOps - where it always belonged. It's apart of the giant #Web that we all use everyday.

It's more typified, normalized and familiar and can then also be viewed in a utilitarian way, in that #ActivityPub provides a public broadcasting function via the web.

Yes inbox, yes outbox, but no braining. Stahp!

Web Social is a broadcast system for the web, where users could communicate with each other.

Das it.

If it's code or executables, put it in the image. If it's persistent, put it in a volume. If it's configuration, put it in an environment variable or an environment variable file, or bind mount the configuration file if needed.

Don't bind mount Git directories with code or data into the container. It may be convenient during development, but it makes it very messy for whoever needs to deploy it later (they should ideally not even have to clone a repository).

Something in the Managed Cloud hosting has always bugged me as a DIY dedicated hardware sysop guy. However, times change and currently I'm looking for one or setting up one myself for a site that has insane amount of requests per second.

WP Engine, Pressidium, Pressable, Kinsta, WordPress VIP or custom AWS or what? What do you recommend, specifically for Enterprise WordPress?

#WordPress#SysOps#Hosting

A while back I was super tired and had too many command line windows open. I typed in the wrong command on the wrong server. This caused system being partly broken, because I accidentally upgraded a held-back package. Eventually got it fixed by recompiling that certain package, but it contained a module compiled by an external party, so had to wait and not restart any services for 24 hours.

Happens to all of us sometimes.

However, what I learned is I should finally really change the color of each prompt for every single server I have. I have dozens of them. I'm lazy that way, I just customize my local prompt but rarely do it on production servers, despite how easy it is.

For Mastodon my prompt is deep purple, like it should.

```bash
PS1="\[\e[38;5;141m\]\u@\h:\w\$ \[\e[0m\]"
```

Here are my other prompts, feel free to use these colors in your .bashrc:

```bash
PS1="\[\e[38;5;99m\]\u@\h:\w\$ \[\e[0m\]" # Light Purple
PS1="\[\e[38;5;141m\]\u@\h:\w\$ \[\e[0m\]" # Pastel Purple
PS1="\[\e[38;5;183m\]\u@\h:\w\$ \[\e[0m\]" # Lavender
PS1="\[\e[38;5;217m\]\u@\h:\w\$ \[\e[0m\]" # Light Pink
PS1="\[\e[38;5;216m\]\u@\h:\w\$ \[\e[0m\]" # Peach
PS1="\[\e[38;5;117m\]\u@\h:\w\$ \[\e[0m\]" # Sky Blue
PS1="\[\e[38;5;159m\]\u@\h:\w\$ \[\e[0m\]" # Soft Cyan
PS1="\[\e[38;5;121m\]\u@\h:\w\$ \[\e[0m\]" # Mint Green
PS1="\[\e[38;5;229m\]\u@\h:\w\$ \[\e[0m\]" # Soft Yellow
PS1="\[\e[38;5;210m\]\u@\h:\w\$ \[\e[0m\]" # Light Coral
```

#Linux#SysOps#SysAdmin

#lispyGopherClimate
Recorded live #interview with @corwin
communitymedia.video/w/6wYk9SW
January 8 #2025 0UTC Wednesday: Archive backup of the episode.

#FSF #sysops #emacs #pedagogy #gamedev #ttrpg #elisp #lisp #programming #lambdaMOO #dungeon

I was personally out-of-it this episode, but Corwin really shines!

From Corwin:
The FSF link for the fund-raiser is my.fsf.org/join

There's a page about dungeon here: directory.fsf.org/wiki/Dungeon

Here's the project on Savannah: savannah.nongnu.org/p/dungeon

Just spent 6 hours trying find out and solve why my Matrix instance is showing: {"errcode":"M_NOT_FOUND","error":"Not found"} when trying to access images. I did not notice this problem before, because Matrix/Element caches images locally using blobs, but realized this after uploading images to IRC via heisenbridge.

I first thought I had messed up my S3 Object Storage. Then thought I messed up my filesystem. Then I thought I made a mistake in yaml configs. But it was none of that.

It's a while since I installed my Matrix server and completely forgot on how I set up my S3 Object Storage. It seems it is literally not documented. Like at all. Just like the half of Matrix and Synapse.

I ended up debugging literally anything and everything without any solution. After turning all stones I even asked ChatGPT and it started to run in loops in despair. Finally ended up reading synapse changelog here one bit by bit: element-hq.github.io/synapse/l

It seems, I have upgraded in some point. And wow, in between of upgrades the whole thing has broken. I mean it runs without erros, but it's broken. No deprecated warnings in the log, no warnings in release logs. Left a comment here: github.com/element-hq/synapse/

My solution was to add in homeserver.yaml:
enable_authenticated_media: false

What I hate about Matrix is:

- Nothing is documented
- Nothing is explained
- Everything is complicated to set up

Each upgrade and extension is like building and tinkering for hours and hours and hoping for the best.

I don't know why I keep using Matrix. Guess I like being hurt all the time.

element-hq.github.ioUpgrading between Synapse Versions - Synapse
Antwortete im Thread

@jippi Exactly. I'm still in a sysop team and been doing servers for 20 years.

Top 5:
1. Human error, someone restarted an erroneous process or crashed production in some way - deploy fails, workflow fails, etc.
2. Bottlenecks in processes and CPU usage
3. Disk space runs out in root level, thus cannot write to disk
4. DDoS attacks
5. Network issues