[–] 13 points 6 days ago

I've been considering to cut me quiete severly recently, little sister. I was lucky to have people care me. Let us care for you. We can't help you phisically, but we are all with you. And you told me you'd watch someone for me 👉👈 and I wish we can bond more. I use arch btw

  • source
  • [–] 5 points 2 weeks ago

    My target is terraform to provide VMs on my miniPC and ansible to configure them. For my nas, probably a basic distro then some ansible stuff to setup stomate.

  • source
  •  

    I had an asthma attack this night, and without my brother-in-law's ventolin, I should have gone to the ER. At least, I got motivated to send a mail to a lung specialist (I let it rest since I moved more than a year ago).

    Please, don't be like me, take your appointments if you materialisticaly can. Fight the execution difficulty.

    oskour (jlai.lu)
    submitted 10 months ago* (last edited 10 months ago) by to c/forumlibre@jlai.lu
     

    Faut que je termine un tp avec injector pour 14h, mais j'ai pas de concentration (d'ailleurs, le temps de ce post aurait pu être l'occasion d'avancer). Alaid 😅

    Edit: ça s'est pas trop mal passé, sachant que c'était dans un contexte relativement informel, et que j'ai craqué, je me suis fait aider pas un llm (oups)

     

    Cross-posted from "Dedicated service user or not ?" by @mat@jlai.lu in !selfhosted@lemmy.world


    Hi all !

    As of today, I am running my services with rootless podman pods and containers. Each functional stack gets its dedicated user (user cloud runs a pod with nextcloud-fpm, nginx, postgresql...) with user mapping. Now, my thought were that if an attack can escape a container, it should be contained to a specific user.

    Is it really meaningful ? With service users' home setup in /var/lib, it makes a lot of small stuff annoying and I wonder if the current setup is really worth it ?

     

    Cross-posted from "Dedicated service user or not ?" by @mat@jlai.lu in !selfhosted@lemmy.world


    Hi all !

    As of today, I am running my services with rootless podman pods and containers. Each functional stack gets its dedicated user (user cloud runs a pod with nextcloud-fpm, nginx, postgresql...) with user mapping. Now, my thought were that if an attack can escape a container, it should be contained to a specific user.

    Is it really meaningful ? With service users' home setup in /var/lib, it makes a lot of small stuff annoying and I wonder if the current setup is really worth it ?

     

    Cross-posted from "Dedicated service user or not ?" by @mat@jlai.lu in !selfhosted@lemmy.world


    Hi all !

    As of today, I am running my services with rootless podman pods and containers. Each functional stack gets its dedicated user (user cloud runs a pod with nextcloud-fpm, nginx, postgresql...) with user mapping. Now, my thought were that if an attack can escape a container, it should be contained to a specific user.

    Is it really meaningful ? With service users' home setup in /var/lib, it makes a lot of small stuff annoying and I wonder if the current setup is really worth it ?

     

    Hi all !

    As of today, I am running my services with rootless podman pods and containers. Each functional stack gets its dedicated user (user cloud runs a pod with nextcloud-fpm, nginx, postgresql...) with user mapping. Now, my thought were that if an attack can escape a container, it should be contained to a specific user.

    Is it really meaningful ? With service users' home setup in /var/lib, it makes a lot of small stuff annoying and I wonder if the current setup is really worth it ?

    view more: next ›