Julian

i have taken the links directly from the docs: https://docs.nocodb.com/getting-started/installation/  current state is a 404 with that link as it redirects to double `.exe` extention. ``` wget https://nocodb.com/release/win-x64.exe --2022-10-13...

> > > Duplicate of #223 which has been declined still required for an easy transition from composer1 to composer2 ci's break because of this

> Yes, but @hirak said he won't release a new version. one more version is not that difficult or cumbersome. > `composer self-update --2` is the best workaround I guess....

had the same problem on debian9 you have to install `libsodium-dev` `build-essential` `dovecot-dev`. on debian i assume you have to use the sury.org repo, because he ships most current `libsodium`...

@razzbee see also https://github.com/LuckyFellow/dovecot-libsodium-plugin/issues/6#issuecomment-350849536

@Neilpang please reopen. this is really counterintutive and really can lead to downtimes on prod server. the usecase is: - you have a running prod server with a working letsencrypt...

also it takes the power of `--test`, normally a test or a dry run is applied to the exact command i want to test and when i really want to...

:+1: https://github.com/composer/composer/blob/master/src/Composer/Command/SelfUpdateCommand.php

> I talked to Jordi about it a while back, he recommended https://github.com/padraic/phar-updater :) > even better :+1:

this feature would be really important, because escaping all links in a multiline markdown text can't be the right solution. ``` App\Entity\Item: item_1 __construct: visible: true rank: 50 text: >...