gelldur

• Template name: telegram.message
• Content:

  {{- /* Telegram message to use: {{ template "telegram.message2" . }} */ -}}
  {{ define "__alerts_list" -}}
  {{ range . }}
  {{if ne (index .Labels "alertname") "" -}}
  {{ if eq .Status "firing" }}🔴{{ else }}🟢{{ end }}
      {{- if ne (index .Labels "severity") "" -}}
          <u><b>P{{ index .Labels "severity" }}</b></u> {{ end -}}

axelbdt

Django and PostgreSQL 15, the rules have changed

Postgres 15 is just out, and while there is a lot to love about this new release, you're in for a surprise if you try to set it up with Django following tutorials like this one.

The reason is stated in the release announcement:

Remove PUBLIC creation permission on the public schema (Noah Misch) The new default is one of the secure schema usage patterns that Section 5.9.6 has recommended...

Provided your web app doesn't access your database as a superuser (it shouldn't) and uses a dedicated user, it is not allowed to use the public schema anymore. You have to create one for this specific user, and the next section will

wllmsash

Assigning Static IP Addresses in WSL2

WSL2 uses Hyper-V for networking. The WSL2 network settings are ephemeral and configured on demand when any WSL2 instance is first started in a Windows session. The configuration is reset on each Windows restart and the IP addresses change each time. The Windows host creates a hidden switch named "WSL" and a network adapter named "WSL" (appears as "vEthernet (WSL)" in the "Network Connections" panel). The Ubuntu instance creates a corresponding network interface named "eth0".

Assigning static IP addresses to the network interfaces on the Windows host or the WSL2 Ubuntu instance enables support for the following scenarios: