Woraus ist diese Wand? (thelemmy.club)
submitted 1 week ago* (last edited 1 week ago) by to c/dach@feddit.org
 

Ein Häufchen des Staubes aus dem Bohrloch auf einem Tisch.

Ich habe bei mir gebohrt und weiß nicht, woraus die Wand ist. Eigentlich hätte ich hier Trockenbau erwartet, aber es scheint doch eine tragende Wand zu sein?

Das Haus ist ein niedriges Mehrfamilienhaus im Großraum Berlin, original aus den 20er/30ern, aber innen saniert.

Beim Bohren mit Akkubohrer bin ich unabhängig vom Bohrkopf nicht weit gekommen. Der Bohrhammer ist mit Betonaufsatz aber durch wie Butter. Beton, in den ich bisher gebohrt habe, war aber nie so fein. Der Staub sieht in Person wirklich aus wie feiner, schwarzer Sand und färbt ab wir Graphit. In der Nähe des Lochs sind die Wände glaube ich aus Klinker.

Zwei Bohrlöcher in einer Raufasertapete. Darin ein wenig schwarz/grauer, sandiger Staub.
I am so excited (thelemmy.club)
 

cross-posted from: https://lemmy.ml/post/51050288

Alt: Tirk @frogkaro.bsky.social

explaining 2 tha homies in the middle of the avi arad produces vg movie where 2 chiseled blond doe-eyed blonde white kids must save western civilization from the king of all evil who's a giant beown man from a tribe of belly dancing orientalist stereotypes that this is extremely important to My Culture

 

Eine lusrige britische Comedy/Drama-Serie über eine Gruppe, die mehr oder weniger freiwillig zusammenarbeitet und sich mit einer lokalen Gang anlegt.

Ich habe es endlich geschafft, die dritte Staffel zu schauen und finde die Serie ist echt herrausragend, qualitativ sehr mit Killing Eve vergleichbar. Ich kann nur empfehlen, die erste Staffel noch schnell herunterzuladen, oder zu bingen!

Sieben Kleinkriminelle werden in Bristol zu Sozialarbeit verdonnert und finden eine Tasche voll Geld – Ärger ist programmiert. Als ein Drogenclan sie bedroht, verbünden sie sich.

 

Fors off: I am a total beginner when it comes to docker. I do have some self hosting experience, but run pretty much everything in its on lxc and treat it like a full linux system.

Recently I installed immich in a container and was surprised to see how well it worked.

This lead my to finally tackle something I have been putting off for way to long; installing nightscout (a self hosten glucose monitoring&reporting utility).

For that I followed their guide. Everything worked well up untill the point where I wanted to connect to the web interface. I started of by entering my domain into the nightscout containers arguments (in the form subdomain.domain.tld). Then I used my reverse proxy (nginx, not inside docker) to forward the subdomain to the docker IP on Ports 443, then 80 and lastly the one displayed at the container when listing them with docker ps. None of those worked (I was not able to get a certificate using letsEncrypt and got a 404 when connecting without tls).

I then entered nighscout.[docker-IP] and tried to access it dkrectly which did not work either.

When googling I only find comparisons on how to set up nginx in Docker, or comparisons between the two.

docker-compose file

  GNU nano 7.2                                                                                                 docker-compose.yml                                                                                                          
version: '3'

x-logging:
  &default-logging
  options:
    max-size: '10m'
    max-file: '5'
  driver: json-file

services:
  mongo:
    image: mongo:4.4
    volumes:
      - ${NS_MONGO_DATA_DIR:-./mongo-data}:/data/db:cached
    logging: *default-logging

  nightscout:
    image: nightscout/cgm-remote-monitor:latest
    container_name: nightscout
    restart: always
    depends_on:
      - mongo
    labels:
      - 'traefik.enable=true'
      # Change the below Host from `localhost` to be the web address where Nightscout is running.
      # Also change the email address in the `traefik` service below.
      - 'traefik.http.routers.nightscout.rule=Host(`localhost`)'
      - 'traefik.http.routers.nightscout.entrypoints=websecure'
      - 'traefik.http.routers.nightscout.tls.certresolver=le'
    logging: *default-logging
    environment:
      ### Variables for the container
      NODE_ENV: production
      TZ: [removed]

      ### Overridden variables for Docker Compose setup
      # The `nightscout` service can use HTTP, because we use `traefik` to serve the HTTPS
      # and manage TLS certificates
      INSECURE_USE_HTTP: 'true'

      # For all other settings, please refer to the Environment section of the README
      ### Required variables
      # MONGO_CONNECTION - The connection string for your Mongo database.
      # Something like mongodb://sally:sallypass@ds099999.mongolab.com:99999/nightscout
      # The default connects to the `mongo` included in this docker-compose file.
      # If you change it, you probably also want to comment out the entire `mongo` service block
      # and `depends_on` block above.
      MONGO_CONNECTION: mongodb://mongo:27017/nightscout

      # API_SECRET - A secret passphrase that must be at least 12 characters long.
      API_SECRET: [removed]

      ### Features
      # ENABLE - Used to enable optional features, expects a space delimited list, such as: careportal rawbg iob
      # See https://github.com/nightscout/cgm-remote-monitor#plugins for details
      ENABLE: careportal rawbg iob

      # AUTH_DEFAULT_ROLES (readable) - possible values readable, denied, or any valid role name.
      # When readable, anyone can view Nightscout without a token. Setting it to denied will require
      # a token from every visit, using status-only will enable api-secret based login.
      AUTH_DEFAULT_ROLES: denied

      # For all other settings, please refer to the Environment section of the README
      # https://github.com/nightscout/cgm-remote-monitor#environment

  traefik:
    image: traefik:latest
    container_name: 'traefik'
    command:
      - '--providers.docker=true'
      - '--providers.docker.exposedbydefault=false'
      - '--entrypoints.web.address=:80'
      - '--entrypoints.web.http.redirections.entrypoint.to=websecure'
      - '--entrypoints.websecure.address=:443'
      - "--certificatesresolvers.le.acme.httpchallenge=true"
      - "--certificatesresolvers.le.acme.httpchallenge.entrypoint=web"
      - '--certificatesresolvers.le.acme.storage=/letsencrypt/acme.json'
      # Change the below to match your email address
      - '--certificatesresolvers.le.acme.email=[removed]'
    ports:
      - '443:443'
      - '80:80'
    volumes:
      - './letsencrypt:/letsencrypt'
      - '/var/run/docker.sock:/var/run/docker.sock:ro'
    logging: *default-logging

 

The sensor is located on the case (not near the exhaust) of the server. With the structure of my appartment this is the only place I can realistically put my Server but sadly also the hottest place in my appartment.

The outside temperature is supposed to reach 36°C today so I expect the ambient temp for the server to rise another 2-3 degrees.

Homessistant plot showing the temperature the last few days. It started at 30.8°C yesterday and has been rising since to now 31.5°C.
view more: next ›