| ## Example using https://pre-commit.com/ | |
| repos: | |
| - repo: local | |
| hooks: | |
| - id: dontship | |
| name: DONTSHIP check - Block words | |
| entry: '\bdie\b' | |
| language: pygrep # https://pre-commit.com/#pygrep | |
| types: [php] |
| #!/bin/sh | |
| # Run as user `ubuntu` from the Ubuntu Desktop installer's live environment. | |
| sudo apt-add-repository universe | |
| sudo apt update | |
| passwd ubuntu | |
| sudo apt install --yes openssh-server screen vim | |
| ip addr show scope global | grep inet |
Sometimes it seems like the first (and sometimes only) advice you get offered for almost any problem with a Raspberry Pi is "check your power supply". You think something like:
"hey, I'm using an official power supply sold as being matched with my Pi so how can there be any problem?"
You look up the specs then stick a controlled load across your supply and confirm that it can deliver the required number of Watts.
Yet your problems persist…