Elvith Ma'for

Former Reddfugee, found a new home on feddit.de. Server errors made me switch to discuss.tchncs.de. Now finally @ home on feddit.org.

Likes music, tech, programming, board games and video games. Oh… and coffee, lots of coffee!

I � Unicode!

  • 0 Posts
  • 86 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2024

help-circle









  • ##############################
    # ALL YE WHO ENTER HERE BE WARNED  
    # THIS ISN'T MY FAULT, BUT $TOOL ONLY 
    # ALLOWS THIS DIRTY WORKAROUND
    #
    # DO NOT CHANGE OR REFACTOR
    # ANYTHING.
    # 
    # IF YOU NEED TO TOUCH THIS CODE
    # INCREMENT THIS COUNTER AS A
    # WARNING FOR THE NEXT POOR FUCK
    # 
    # TOTAL HOURS WASTED DEBUGGING
    # 15
    # TOTAL HOURS WASTED REFACTORING
    # 8
    # SUCCESSFUL CHANGES
    # 0
    ##############################
    




  • For me it was usually that the config that I need to serve a site with TLS is quite short, there are sensible defaults and many things (e.g. websockets) just work without further declaration. That’s especially important if you want to host a container that has some lacking documentation about usage of reverse proxies, as most things “just work fine” for me.

    And using a simple include directive, you can even replicate ‘sites-available’ and ‘sites-enabled’ behaviour. My standard Caddyfile just sets up the log file format and location and basic Let Encrypt values. Then it includes /foo/bar/sites-available/*. Every deployment/container now has its own Caddyfile that just gets linked there.