• 1 Post
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle






  • bort@feddit.detoEurope@feddit.deSauna dress-code across Europe
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    1
    ·
    10 months ago

    In Germany it’s often framed as a hygiene issue, because that’s easier to sell to randos. The real issue it that it’s uncomfortable to be nude when there are clothed people all around you. And the sauna itself is more comfortable when nude.

    It’s kina like a prisoners delemma, where the pareto solution is when everyone else is nude, and the nash-equlibrium is when everyone is clothed. Because of this, some people will want to defect (i.e. wear clothes), so we need to apply outside pressure to enforce the pareto-efficient solution (i.e. by asking people to remove their clothes).






  • Workflow/Prompt

    I asked chat gpt + dalle

    the topic is “Sustainable Ecumenopolis”. Come up with a novel concept for this.

    The make some award winning high-quality images about it

    then I rejected the first batch of result and said

    vertical farming and solar panels are stale and boring.

    the images should be award winning high quality and atmospheric.

    then it generated some images. The one I selected for the competition was this

    Render: Atmospheric night plaza in Biosphere Nexus. Architectural structures inspired by biomimicry surround the area. Trees with bioluminescent leaves light up the ambiance, with diverse citizens enjoying the scene.

    If I win, the next topic will be “Torment Nexus”




  • I recommend to use relevativ paths in the compose files. e.g.

      - '/home/${USER}/server/configs/heimdall:/config'
    

    becomes

      - './configs/heimdall:/config'
    

    you may want to add “:ro” to configs while you are at it.


    also I like to put my service in /srv/ instead of home.


    also I don’t see anything about https/ssl. I recommend adding a section for letsencrypt.


    when services rely on each other, it’s a good idea to put them into the same compose file. (on 2nd thought: I am not sure if you already do that? To me it is not clear, if you use 1 big compose file for everything or many small ones. I would prefer to have 1 big one)

    you can use “depends_on” to link services together.


    you should be consistent with conventions between configurations. And you should remove config-properties that serve no purpose.:

    • you don’t need to specifiy “container_name”, when it would be same name as the service
    • PUID=1000 and PGID=1000 shouldn’t be needed, I think.
    • sometimes you add explicit “:latest” to the version, and sometimes you don’t

    while you are at it, you may want to consider using an .env file where you could move everything that would differ between different deployment. e.g.

    • PUID
    • TZ
    • exposed ports, maybe

    consider using podman instead of docker. The configuration is pretty much identical to docker-syntax. The main difference is, that it doesn’t require a deamon with root privileges.


    you may want to consider to pin version for the containers.

    pro version pinning:

    • no unexpected changes, when you restart the container (e.g. because you accidentally pulled)

    con version pinning:

    • when you DO want to make an update, you have to spent 2 minutes to go to docker hub to find out which version you want.