Log
Maybe your #mastodon instance is playing tricks while uploading GIF files (dunno why it's not happening with other image formats):
413 Entity too large.
In our case this is a dockerized instance with `jwilder/nginx-proxy` in the middle, the fix is easy:
1. Use a nginx config volume: `./data/conf:/etc/nginx/conf.d`
2. create a `client_max_body_size.conf`file in the volume with "client_max_body_size 100m;" inside.
3. Restart the instance
From time to time I get an error like this trying to execute a #make custom command:
$ make backup
make: 'backup' is up to date
I thought that something was wrong with that backup command but it seems the error is because there is a `backup/` directory sibling to the `Makefile`.
If you change the directory name or the command name, the error is gone. Weird, indeed.
I had a little whim, wanted to import all the toots from #mastodon tagged as #micropost in my web (a static site generated by #hugo #go #golang).
It was a perfect excuse to practice a bit of #rust and enjoy all the little lessons I've learned.
I doubt it will be helpful to anyone but just in case I've published the repo:
https://git.oscarmlage.com/oscarmlage/masto-rss
I know there is quite room for improvement but feel free to give some feedback ;)
🦀
I've read you can use #cicd with #gitea too via #drone (and also #jenkins works). It may probably be worth giving it a try.
https://dev.to/ruanbekker/self-hosted-cicd-with-gitea-and-drone-ci-200l
I think I've said it before, but I'm totally **in love** with #gitlab #cicd procedure, even being a yml-based thing
❤️ #micropost
In software engineering, #rubberduck debugging (or #rubberducking) is a method of debugging code by articulating a problem in spoken or written natural language.
The name is a reference to a story in the book «The Pragmatic Programmer» in which a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it, line-by-line, to the duck.
🔈🦆 #micropost
The #rust solution with buggy / outdated #crates:
Package versions can’t be deleted, they can only be yanked. A yanked package can still be used if it is in your project’s lock file so existing projects will not break.
But new projects can not use a buggy version, #cargo will display an error and advise an upgrade. Backwards compatibility without compromising new features.
