[05:17:48]
<patitsas> Hi everybody, I'm having difficulty with reinstalling Iceshrimp. I installed it, hit some snags, uninstalled it, installed Sharkey, hit different snags, and then decided I was better off with Iceshrimp after all. When I do the renistall, there are no errors that show up in the web interface. But then I open iceshrimp in the browser and it's spinning circles and broken divs everywhere. It seems to be connecting to a pre-existing database. I'm not sure what to do to reset it. Any ideas?
[05:50:50]
<Salamandar> Could you please show the install logs and the service logs ? Everything can be found in the web admin :)
[07:40:54]
<lautre> > <@patitsas:matrix.org> Hi everybody, I'm having difficulty with reinstalling Iceshrimp. I installed it, hit some snags, uninstalled it, installed Sharkey, hit different snags, and then decided I was better off with Iceshrimp after all. When I do the renistall, there are no errors that show up in the web interface. But then I open iceshrimp in the browser and it's spinning circles and broken divs everywhere. It seems to be connecting to a pre-existing database. I'm not sure what to do to reset it. Any ideas?
Try to reload the web page with the keys: Control+shift+R
This will purge the cache for the page.
Just in case.
[08:15:25]
<tituspijean> > Does anyone know when yunohost for raspberry pi 5 will be released?
No, but you are most welcome to try it out by Installing Debian 12 then Installing YunoHost 12 by checking out the call for testers on the forum. (BTW, we give no timelines, but your tests and feedback will definitely shorten the wait)
[08:23:42]
<tituspijean> > <amu> I'd like to make sure the script gets backuped by the standard yunohost backup
You have two options:
1. Create a cronjob and use the backup and restore hooks (https://yunohost.org/en/packaging_apps_hooks#backup-restore) to include it in the backups
2. Use a post_upgrade hook (https://yunohost.org/en/packaging_apps_hooks#post-app-upgrade) to hack into the app's cronjob in `/etc/cron.d/$app` and make sure it is customized to your needs upon every upgrade.
[08:32:03]
<tituspijean> > <@chrichri:ween.de> Just installed **GoToSocial** and am a bit confused about **registration**: Found hints that there might be a way to have self-registratoin with confirmation by the admin, but didn't find any information on how to use it...
Per https://docs.gotosocial.org/en/latest/admin/signups/ now all new registrations have to be approved by the admin. The YunoHost package documentation and install question is not up-to-date.
[08:35:22]
<tituspijean> If you can confirm so, you are welcome to help out (https://github.com/YunoHost-Apps/gotosocial_ynh/issues/145) 🙂
[08:45:29]
<chrichri ⚡> > <@titus:pijean.ovh> If you can confirm so, you are welcome to help out (https://github.com/YunoHost-Apps/gotosocial_ynh/issues/145) 🙂
Subscribed. If I find answers I'll help. I guess I'll ask over at their repo...
[09:50:22]
<amu> tituspijean: Looks great. I cannot check it now. I will and very likely will come back with more questions here or in the forum... Thank you!
[11:13:22]
<chrichri ⚡> > <@chrichri:ween.de> Subscribed. If I find answers I'll help. I guess I'll ask over at their repo...
Hm, https://doma.in/signup does show me an error **404: Not Found GoToSocial only serves Public statuses via the web.** even though everything for registration is enabled in yunohost (and in config.yaml).
[14:30:46]
<grahamalamadingdong> From a security perspective, what's the best way to manage SSH / the root account / sudoing, etc?
I just set up an SSH key for my "main" user account. It appears that I'm able to do admin operations by `sudo`ing. Does this mean I can more or less abandon use of the `root` account and rely on this SSH key + sudo for operations / maintenance? Or should I set up a 2nd SSH key for the root account?
Also, there is one other user on my server who I don't want the same "sudo as admin" ability. How can I verify that their sudo ability isn't the same?
[14:34:19]
<selfhoster1312> > Or should I set up a 2nd SSH key for the root account?
Why not use the same key? if you are the same person to access both :)
[14:36:13]
<selfhoster1312> > How can I verify that their sudo ability isn't the same?
maybe login as them and verify they can't sudo...
[14:36:21]
<selfhoster1312> ```
sudo -i -u THATUSER -- sudo -v
```
[14:41:34]
<grahamalamadingdong> Nice, `sudo -i -u THATUSER -- sudo -v` went as expected.
Though, trying this did lead me to one discovery:
from my user account:
```
Sorry, user <my account> is not allowed to execute '/bin/bash' as <other account> on <server>.
```
[14:42:11]
<selfhoster1312> maybe only root can do that? not sure :)