[–] 3 points 2 weeks ago* (2 children)

The only thing I know about modern Grece is how Europe fucked it (in France we even have a "nice billionaire" trying to explain how he helped to "save" the economy) and Krav Boca. Maybe check a live show of them if they play there ^^

  • source
  • [–] 13 points 3 weeks 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
  • oskour (jlai.lu)
    submitted 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 ›