It seems more clear to me this is an issue with the shlink server not receiving requests routed – whether yunohost api frontend is not properly configured to route them, or the install process did not full set up the shlink-server portion to with all dependencies and to listen and run.
(Docs, on (not) pre-configuring servers or no pre-populating server configurations with secrets in clients.)
(For upstream developer’s recent release announcement and other thoughts, Alejandro Celaya | Blog — Software development, agile methodologies and open source software)
I generated a second api key, I see it in the database, and neither by shlink.fqdn or shlink.fqdn/api endpoints mentioned by yunohost webadmin work as servers for
To make shlink available to cli invocation on yunohost, install this:
in /var/www/shlink,
create bin/shlink with contents
#!/bin/bash
cd /var/www/shlink
sudo $(cat .env) -u shlink php8.2 bin/cli "$@"
then symlink it into /usr/local/bin
/var/www/shlink# ln -s `pwd`/bin/shlink /usr/local/bin
Then it can be called anywhere as $ shlink [args]
listto see commands,api-key:generate,api-key:list, and others.
After all this, my current status is:
- I cannot add server to webclient. Api keys are not accepted, it seems likely the client is not able to reach the server.