GitHub Security Scanning is a feature that helps you identify and fix security vulnerabilities in your code. It scans your code for known security vulnerabilities and provides recommendations for how to fix them. It scans also for credentials and secrets.
In one of my posts is a Docker Swarm Join Token (which is no longer in use), but I've just want to show how the GitHub Security Scanning works.
I've updated my blog (again). Now I am using Material for MkDocs. With my old setup, I had a misconfiguration that caused the URL to be set to /blog/posts/<article>. The new URL is just /blog/<article>.
I want to fix that by using NGINX rewrite rules. Here's how I did it:
See the announcement
- Updated Pull Rate Limits for Free & Unauthenticated Users – To ensure a reliable and seamless experience for all users, we are updating authenticated and free pull limits:
- Unauthenticated users: Limited to 10 pulls per hour (as announced previously)
- Free authenticated users: Increased to 100 pulls per hour (up from 40 pulls / hour)
I use the Proxmox Backup Server to create backups of my VMs. The Proxmox Backup Server runs as a VM on a different (TrueNAS) server. The server is connected to a PDU. Therefore the PDU Outlets must be switched on and off...
For some VMs you want to have access to the physical harddrive or SSD. For example if you want to virtualise TrueNAS.
There is a good article from Proxmox here
One piece is missing and that is how you add the serial number of the HDD/SSD to that device.