Homebrew makes it easy to install and keep installed software up to date on your Mac - as part of my backup routine for my Mac I want to be able to run a single command to reinstall all packages.
If you're searching on how to backup & restore Homebrew, then I assume you're here for the commands.
Brewfiles are files generated with definitions that Homebrew reads and processes, a generated
| #!python3 | |
| """ | |
| Convert a requirements.txt file to a Poetry project. | |
| Just place in the root of your working directory and run! | |
| """ | |
| sourceFile = "./requirements.txt" | |
| import re | |
| import os |
| #!/usr/bin/env bash | |
| # To fix the " gpg: WARNING: unsafe permissions on homedir '/home/path/to/user/.gnupg' " error | |
| # Make sure that the .gnupg directory and its contents is accessibile by your user. | |
| chown -R $(whoami) ~/.gnupg/ | |
| # Also correct the permissions and access rights on the directory | |
| chmod 600 ~/.gnupg/* | |
| chmod 700 ~/.gnupg |
| {"lastUpload":"2020-09-04T18:49:47.910Z","extensionVersion":"v3.4.3"} |
| "workbench.colorCustomizations": { | |
| // Contrast Colors - The contrast colors are typically only set for high contrast themes. If set, they add an additional border around items across the UI to increase the contrast. | |
| "contrastActiveBorder": "", | |
| "contrastBorder": "", | |
| // Base Colors | |
| "focusBorder": "", | |
| "foreground": "", | |
| "widget.shadow": "", | |
| "selection.background": "", | |
| "descriptionForeground": "", |
| # -*- coding: utf-8 -*- | |
| """Example Google style docstrings. | |
| This module demonstrates documentation as specified by the `Google Python | |
| Style Guide`_. Docstrings may extend over multiple lines. Sections are created | |
| with a section header and a colon followed by a block of indented text. | |
| Example: | |
| Examples can be given using either the ``Example`` or ``Examples`` | |
| sections. Sections support any reStructuredText formatting, including |
In many cases, we need to use secret information in our Ruby; most commonly, API keys and email account passwords.
You should never paste these strings directly into your Ruby code. There are bots that can and will steal your API keys the instant you push your code to a public GitHub repository. Even if you pay for private repositories, it's a good idea to not store secrets in your repo -- you may not want all of your collaborators (interns?) to know, for example, the API keys to your payment processor.
(If you have already pushed an API key to a public repository, you should sign into your API dashboard now and invalidate that old key, and get a new one. Assume that the old one has already been stolen. Reverting your commit will do no good.)
But if our Ruby needs to use these secrets, but we can't keep them in our code, what's the solution? Environment variables. We're going to use a gem called Figaro to make this easy.
#Oh My Zsh - Git Cheat Sheet
g – git
gst – git status
gl – git pull
gup – git pull --rebase