This is a collection of information on PostgreSQL and PostGIS for what I tend to use most often.
| Backup: | |
| docker exec -t -u postgres your-db-container pg_dumpall -c > dump_`date +%d-%m-%Y"_"%H_%M_%S`.sql | |
| Restore: | |
| cat your_dump.sql | docker exec -i your-db-container psql -Upostgres |
| CURRENT_DIRECTORY := $(shell pwd) | |
| TESTSCOPE = apps | |
| TESTFLAGS = --with-timer --timer-top-n 10 --keepdb | |
| help: | |
| @echo "Docker Compose Help" | |
| @echo "-----------------------" | |
| @echo "" | |
| @echo "Run tests to ensure current state is good:" |
| # | |
| # Nginx SSL Proxy | |
| # @link https://gist.github.com/lidio601/aa97397f8cdb5f405ce770dde2fe3c2b | |
| # @link https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-with-ssl-as-a-reverse-proxy-for-jenkins | |
| # | |
| # Redirect all HTTP requests to SSL | |
| server { |
| """ | |
| Sometimes in your Django model you want to raise a ``ValidationError`` in the ``save`` method, for | |
| some reason. | |
| This exception is not managed by Django Rest Framework because it occurs after its validation | |
| process. So at the end, you'll have a 500. | |
| Correcting this is as simple as overriding the exception handler, by converting the Django | |
| ``ValidationError`` to a DRF one. | |
| """ | |
| from django.core.exceptions import ValidationError as DjangoValidationError |
Side note: The latest edge build of KeeAgent plugin offers an option for creating a WSL compatible socket. This would be very handy. I already tried to use that socket, but the socket file is currently empty and ssh inside WSL 2 is unable to use it. This appears to be a very new, unreleased and unstable feature. I will follow the development of it and when it finally works (well, for me) I will update this HOWTO. But until then, please use the proven wsl-ssh-agent/npiperelay.exe approach below.
Thanks to the instructions for WSL 2 of the wsl-ssh-agent project, KeeAgent works great in WSL 2 now:
https://github.com/rupor-github/wsl-ssh-agent#wsl-2-compatibility
The approach uses minimal and well-maintained tools.
- 14.08.2025: Improve: Improve title of this gist.
WSL 2 uses a Hyper-V Virtual Network adapter. Network connectivity works without any issue when a VPN is not in use. However when a Cisco AnyConnect VPN session is established Firewall Rules and Routes are added which breaks connectivity within the WSL 2 VM. This issue is tracked WSL/issues/4277
Below outline steps to automatically configure the Interface metric on VPN connect and update DNS settings (/etc/resolv.conf) on connect/disconnect.