This was actually pretty interesting until I found out that Caddy is not yet supported :(

Thank you anyway!

I already looked into Authelia, and the “problem” I encountered is that it does not support “named policies” (I don’t know the actual name): what I mean is to be able to create “only_admin_policy”, “only_registered_users_policy” etc, and then in Caddy to be able to say something like this

service1.website.com {
    reverse_proxy container1:1234
    apply_policy only_admin_policy
}
service2.website.com {
    reverse_proxy container2:1234
    apply_policy only_registered_users_policy
}
service3.website.com {
    reverse_proxy container3:1234
}

Instead if I understood correctly (and I would gladly be proved wrong) this is not possible with Authelia, as these policies have to be specified inside Authelia, so I would have two different configurations in two different places instead of having everything in the Caddyfile

I hope I explained well what I mean

thanks for the help!

How does programmatic access tie into the desire for a login form?

I would like to keep files with “private” information protected from public access, but I would like to access them from a script. An example: i wrote a karaoke application to use with my friends, they have to go to a webpage and select the songs they like, and then the karaoke app connects to the server to get the updated preference file. I would like that the users had a “nice login form” to select their songs, and then I’d like my karaoke app to easily download the file while still keeping it password-protected

This looks very interesting! I see that it supports users groups, would it be possible to create “named access policies” (like “admin_only_policy”, “group_XXX_policy” ecc) and then assign them to the various services directly in the Caddyfile? thank you very much!

wouldn’t this take a lot of time? but I can see the advantage, being able to just roll back whatever happened

I’ll think about it, thank you very much!

Wow this is amazing! thank you very much for the super detailed answer! exactly what I was looking for!

This is actually very interesting! I’ll gladly look into it, thank you very much!

thanks for the reply! Yes for sure I’m backing up all the /home directory, but I’d like to preserve also important configurations like ssh, cronjob etc, but I don’t really know which directories are important for this and which are not

thanks for the reply!

How do you plan to restore if the whole drive dies?

good point: I guess if the problem is that I messed something up I may just run the backup script in reverse? if the problem is HW then I’d have to reinstall and then restore the backupped directory probably is there a “standard” way?

Yes, it’s like a common “protocol”. Probably huge music apps like youtube and spotify would never adopt such a thing unless it become really really widespread among other platforms, but just being able to share them across FOSS music players would be amazing imo

It’s actually very very cool, the closest to what I imagined. Yeah sadly it doesn’t seem to be FOSS

The main difference with my “idea” is that this one creates a copy of the playlist on each service, so if you want to share it you need to know which player the other person is going to use, or just send him all the links. My idea instead has just a single playlist, accessible with API that can be used by every music player

thanks for sharing this!

Yeah something similar to this, with API to access it from any music player app! The features that would make it really appealing (imo) would be:

• share playlists with friends using different music players
• cooperative playlists: give edit permission to other users (chosen by you), so that you can create playlists with your friends
• search playlist: search “rock music” and get all public playlists that matches your search, perhaps even with tags

How about you make up the structure and we all adopt it?

I would like to have the capabilities and the time to do this XD

I think that the best possiblity for something like this would be that a already popular music player created this alongside the player, and already adopted it, allowing sharing playlists with users on the same app. This way, all other music players would have the possibility to adopt it themselves in order to be able to share the playlists with users on their app and on the original music player, and so on

The problem with services like Funkwhale and Navidrome or similar services is that you need a music library on the server, and the players can only play music from there. What I have in mind instead is a way to sync playlists (without caring from where the song is being streamed, may it be youtube, spotify, Funkwhale, Jellyfin, local library…) between different clients

something like this, yes. It was better if it wasn’t centralized perhaps, but if that wouldn’t be feasible then something like ListenBrainz with the ability to add playlist to your account and sync them with a simple API would work

You could simply export and import playlist with a file that can be shared

This is something that has to be done manually. What I have in mind is a platform where I can have a playlist on my music player app, that I update everyday I discover new music, and I want to be able to send a link to you so that you can listen to my playlist in real time, without having to export and then import manually. Also, I would like to be able to have “cooperative playlists” like Spotify has: everyone I give access to my playlist can add songs to it (I do this with my friends, we use it to discover new music)

I said federated because otherwise it would only work between close friends that can create an account on my server, and it means that I wouldn’t be able to share it with anyone outside my friend group. Otherwise it has to be a centralized service I guess

If I understood correctly these are one-shot services: I have a spotify playlist and want to convert it to a YouTube playlist. Instead what I have in mind is a way to sync a playlist “player agnostic”, so that it can be viewed by any music player supporting the API

I already looked into Navidrome, but as far as I understand you have to keep a music library on the server, and then you can stream from there.

What I was thinking instead was just a playlist sync server: the music player apps will still play music from they were playing before, so some from local files, some from YouTube, some from Navidrome ecc, but the playlists are synced on this served and can be exchanged with other users that use different players

THANK YOU! The grep command you posted showed me that that UUID was still present in /etc/kernel/cmdline as

resume=UUID=8c53812d-ba43-45e4-b219-8d3ded8548a5

I changed it with the new one and run sudo reinstall-kernels, and now it works correctly! thank you very much for your help!

A start job is running for /dev/disk/by-uuid/8c53812d-ba43-45e4-b219-8d3ded8548a5

it’s really strange, I just noticed that it’s the UUID of… the original swap partition (now gone) the entry is still commented in /etc/fstab:

# UUID=8c53812d-ba43-45e4-b219-8d3ded8548a5 swap             swap    defaults   0 0

is there another place other than /etc/fstab where I should remove it?

thanks for the help!

EDIT: this is the whole output of sudo blkid if needed:

/dev/nvme0n1p3: LABEL="swap" UUID="506d48e6-1cc0-4136-ba55-6f2f187bcdb1" TYPE="swap" PARTLABEL="SWAP" PARTUUID="b4543e4e-4623-4317-99aa-086b0e62836e"
/dev/nvme0n1p1: UUID="467B-65A4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="53413c1b-04f0-42cf-bd71-15e2796f002a"
/dev/nvme0n1p2: LABEL="endeavouros" UUID="cf0a3420-51e0-40ba-8b86-ae2cc576e5c1" UUID_SUB="faa47171-fc00-4435-8c8f-0b346682071d" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="endeavouros" PARTUUID="dc12b835-18f9-4937-8a58-07b2600012e9"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="d076884c-6236-4e0a-be36-47df3e28d7a3"
/dev/sda3: LABEL="STORAGE" UUID="6EFB-D6EF" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="381ea0c9-7fdd-4a74-a92e-5b450f2001db"
/dev/sda1: LABEL="WINZOZZ" BLOCK_SIZE="512" UUID="7FC0A0D067B4D0F8" TYPE="ntfs" PARTUUID="e4d431c8-06e8-4fac-93e9-342026cc4ff1"