Log
En nuestra instancia #BOFHers de #Mastodon (https://mastodon.bofhers.es) buscamos soluciones para mantener la actividad. Con 80 usuarios y 300+ GB de disco, en una VM de 8 GB RAM y 8 vCPUs, las actualizaciones son cada vez más complicadas, requiriendo casi el doble de espacio en disco, a pesar de nuestras tareas programadas para reducir cachés, assets y previews.
Agradecemos boost y/o cualquier consejo, sugerencia o aportación para que #BOFHers siga siendo un espacio activo para todos.
Desde que agregamos el clean diario va algo mejor:
Filesystem Size Used Avail Use% Mounted on
/dev/xxx 492G 146G 323G 32% /xxx/mastodon
Habría que quitarle 30Gb de los dumps diarios, que también están ahí
load average: 2.61, 2.07, 2.32
El cleanmedia diario:
# tail -n 100 cleanmedia.log
3155/3155 |=========| Time: 00:02:08
Removed 3155 media attachments (approx. 3.71 GB)
1807/1807 |=========| Time: 00:01:09
Removed 1807 preview cards (approx. 343 MB)
No quiero entrar en comparaciones ni tampoco digo que no sea necesario todo esto, pero me parecen unos requisitos - de entrada - demasiado exagerados para interactuar con #activitypub .
#TIL that with #Obsidian and the #Templater plugin, it’s possible to automatically create a new note and a related issue in #Gitea or #Forgejo at the same time. Made my day.
You can define a custom function that makes a curl request as tp.user.curl()
:
const { exec } = require('child_process');
module.exports = async (args) => {
return new Promise((resolve, reject) => {
exec(args.command, (error, stdout, stderr) => {
if (error) {
console.error(`Error: ${error.message}`);
reject(error);
} else if (stderr) {
console.error(`Stderr: ${stderr}`);
reject(stderr);
} else {
console.log(`Result: ${stdout}`);
resolve(stdout);
}
});
});
};
Then the function call:
<%*
const curlCommand = `curl -s -X POST -H "Content-Type: application/json" -H "Authorization: token ${token}" -d "{\\"title\\": \\"${title}\\", \\"body\\": \\"${content}\\"}" ${url}`;
const exec = await tp.user.curl({ command: curlCommand });
%>
When you execute this template, the curl request will be triggered, creating the issue as specified.
One of my kids wanted to dress up as a mortgage because it’s the most terrifying thing for an adult.
However, he finally decided to go as one of the guards from Squid Game. The other wants to go as a ‘monster bear,’ but I have a feeling it’s just an excuse to wear the mask because it looked like something from Minecraft.
…unlike me, who’s dressing up as a certified Terraform expert but still in plan mode.
And here they go
I just realized that @things, my favorite task management software, has a Mastodon account!
It’s a pity they’re not as active here as on other social networks… but it’s worth following them, just in case.
- Update: @things Oh, they’re just as active as on other platforms—it was my instance playing tricks on me.
Mastodon / Bluesky: After a few days of using both apps in parallel, I see strengths and weaknesses in each; I can’t choose one over the other, so what I didn’t want to happen is probably going to happen: I’ll end up using both. I don’t think this will double my social media time, but I don’t think it’s ideal either.
And… another grey day in front of the keyboard. Interestingly, in the real world, it’s a beautiful day. Let’s see if I can take advantage of it and change the mood.
[later]
Indeed, the mood changed for the better. Lately, it feels like the computer brings out the worst in me. I think I need to make some changes.
[and later]
To be honest, one of the things that distracts me the most is context switching. Considering the house renovations aren’t finished yet, I’m constantly moving between my parents’ place and mine, and that’s definitely not helping.
Did a bit of #woodworking this afternoon. I had a wheel chock for the van to prevent the wheel from rubbing against the curb, but it broke, so I had to patch it up.
It’s not the best or cleanest job… but it works.
Today is #legday, not just a normal leg day, but the first one in the last two months. Tomorrow will be fun.