Clojurians Log v2

I… might just get one today 😅

Anybody know how to use caddy?

Apr 08 22:39:20 raspberrypi.local caddy[799]: {"level":"warn","ts":1617935960.1684682,"logger":"http","msg":"user server is listening on same interface as automatic HTTP->HTTPS redirects; user-configured routes might override these redirects","server_name":"srv1","interface":"tcp/:80"}

Here's my caddyfile.

<http://domain.name>, <http://www.domain.name> {
    redir <https://www.domain.name>{uri}
}

<https://www.domain.name> {
        # Set this path to your site's directory.
        root * /home/pi/my_website/

        # Enable the static file server.
        file_server

        # Another common task is to set up a reverse proxy:
        # reverse_proxy 127.0.0.1:2019

        # Or serve a PHP site through php-fpm:
        # php_fastcgi localhost:9000

        # Refer to the Caddy docs for more information:
        # <https://caddyserver.com/docs/caddyfile>
}

Caddy will do an automatic redirect

you don't need to explicitly configure that in your Caddfyfile

Couple thoughts here, I've had good experience with AWS support. I've found what seems like bugs (500 exceptions), and support have been able to give technical answers about areas that aren't supported that we're hitting. We've also had performance issues with RDS dbs in prod with AWS, and support were able to diagnose the issue down to the host node the DB was on.

EC2 instances definitely fail, go offline, etc. The AWS argument is that this is perfectly normal in any cloud environment, and you should be using load balancers etc. to cope with that. I'm surprised the rate is as high as 1/200/weekly though. I've not run at that kind of scale before though. I did have a non-HA Datomic DB go down on me once though as a result of an EC2 lock up :)

would it be meta to make a channel called #on-topic ?

what could be more “on topic” than #clojure?

:rolling_on_the_floor_laughing:

They look great, just ordered one!