oscarmlage oscarmlage

Microposts

Short notes, mainly with photos, quick thoughts, links, and small updates from my day-to-day.

TIL

Maybe your 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

TIL

From time to time I get an error like this trying to execute a 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.

TIL

The other day a friend of mine asked if I'd noted some problem or high load in our little instance. I said no, but then I took a look at , and it seemed that -definitely- something was occurring in the background.

This instance has been installed on 2022-05-26 in a little server, on 2022-09-09 it was migrated to v.3.5.3 and on 2022-09-24 I've bought a new -bigger- server.

- Media storage: 30Gb.
- Postgres storage: 400Mb.
- Redis storage: 20Mb.

That's the toy.

TIL

This afternoon I had a meeting, my mate prettified a horrible string into a tabulated and perfectly aligned json in his shinny VSCode.

Immediately felt that I needed to get the same using my tools. Literally 4 mins later in my .vimrc:

:command Format :%!jq .
:command Unformat :%!jq -c .

Subscribe: Feedsxmlns="http://www.w3.org/2000/svg"width="24"height="24"viewBox="0 0 24 24"fill="none"stroke="currentColor"stroke-width="2"stroke-linecap="round"stroke-linejoin="round"class="icon icon-tabler icons-tabler-outline icon-tabler-rss"> Microposts