• 5ffd57393a85553ab55b
• 5cd28e2a812e5c65c9f7320e0726da18
• b6a6676a84b51c8200d0673a5b4a87c5
The quotes on this page come from this deleted question on Stackoverflow:
The quotes on this page come from this deleted question on Stackoverflow:
In 2019 I moved various web-apps I have created to a VPS (hosted by OVH).
| # These are supported funding model platforms | |
| github: [Potherca] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2] | |
| patreon: Potherca # Replace with a single Patreon username | |
| open_collective: Potherca # Replace with a single Open Collective username | |
| ko_fi: Potherca # Replace with a single Ko-fi username | |
| # tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel | |
| # community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry | |
| liberapay: Potherca # Replace with a single Liberapay username | |
| issuehunt: Potherca # Replace with a single IssueHunt username |
Why
sudo echo "something" > /path/to/protected/file.txtdoesn’t work and what to do instead.
If you are working on the command-line and you want to write output to a file, sooner or later you come up with this command: echo "output" > file.
This is called a “Redirection”. This works wonderfully and you go on your merry way.
Sometime later, you need to do the same thing with a protected file.
"Formal education will make you a living. Self-education will make you a fortune."
For most languages a single standard for documenting functions and methods in block comments (a.k.a. doc-blocks) has emerged.
For BASH, however, there does not seem to be a definitive convention. Several competing conventions exist, which made me think:
Could a list of doc-block tags be distilled from those used across all (or most) languages?
Time to find out!
| <!doctype html> | |
| <meta name="description" content="Het kabinet Schoofs deed er 223 dagen over om zich te formeren, om vervolgens 337 dagen te regeren, waarna het 149 dagen demissionair was."> | |
| <!-- Facebook Meta Tags --> | |
| <meta property="og:url" content="https://gist.pother.ca/a1c14a6758e3bf36768c90f43f4fb13b/"> | |
| <meta property="og:type" content="website"> | |
| <meta property="og:title" content="Kabinet Schoofs I - Formeren vs. Regeren"> | |
| <meta property="og:description" content="Het kabinet Schoofs deed er 223 dagen over om zich te formeren, om vervolgens 337 dagen te regeren, waarna het 149 dagen demissionair was."> | |
| <meta property="og:image" content="https://i.imgur.com/XiT6dE5.png"> |
Starting at a new employer always mean checking out various git repositories.
As the amount of repositories a company has grows, the time needed to clone all of those repositories also grows.
This script automates this task.
In order for this script to work, a personal access token is needed.