• 5 Posts
  • 318 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle












  • Croquette@sh.itjust.workstoSelfhosted@lemmy.worldMy thoughts on docker
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    4
    ·
    10 days ago

    I hate how docker made it so that a lot of projects only have docker as the official way to install the software.

    This is my tinfoil opinion, but to me, docker seems to enable the “phone-ification” ( for a lack of better term) of softwares. The upside is that it is more accessible to spin services on a home server. The downside is that we are losing the knowledge of how the different parts of the software work together.

    I really like the Turnkey Linux projects. It’s like the best of both worlds. You deploy a container and a script setups the container for you, but after that, you have the full control over the software like when you install the binaries


  • I edited the post. Since it’s all local it’s fine to show the IP. It’s just a reflex to hide my ips.

    I use IP directly as I don’t have a local domain configured properly.

    The outpost ip in my configuration file is the same provided in the outpost on Authentik.

    I am trying to get it to work still, but I am pretty sure that the issue is between Authentik and Firefly.

    I don’t see any of the headers (x-authentik-email more specifically) specified in the caddy file when Authentik is sending the request to Firefly. The only header I see is x-authentik-auth-callback.

    I am not sure how I can specify which headers are sent in Authentik.







  • Unless you are at the edge of the firmware and software, this isn’t something you work with a lot.

    When you transfer files or data to a memory space, you can’t drop the whole file/data to memory directly because the resources are limited on the cpu/mcu. It wouldn’t make sense to have a page as big as your biggest theorical data size.

    Page size determine how much data at a time can be transferred into memory.

    In term of performance, writing the page to memory is usually the bottle neck. So 4k vs 64k means you need to write to memory 16 times more and thus making the performance better on 64k page size.