Below is a sample default DMARC digest report. This is why services such as DMARC Digests are so useful, because they translate the default XML into something more human-friendly.
Using fetch
in Lume v2.4.2 (a Deno Typescript static site generator app) on Deno 2.1.2, I get this error when fetching to our ops db REST API:
fetch TypeError: "client error connection reset by peer"
I see a lot of people have had this same problem, in various GH issues, and it appears that it is because of the underlying Rust library being used. For example:
A Pen by Rick Cogley on CodePen.
/* Language supports hyphenation ハイフン対応可能な言語 */ | |
html[lang="en"] { | |
text-align: left; | |
-webkit-hyphens: auto; | |
-webkit-hyphenate-limit-before: 3; | |
-webkit-hyphenate-limit-after: 3; | |
-webkit-hyphenate-limit-chars: 6 3 3; | |
-webkit-hyphenate-limit-lines: 2; | |
-webkit-hyphenate-limit-last: always; | |
-webkit-hyphenate-limit-zone: 8%; |
#!/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 |
I have a situation where I have scripts pushing changes to a github repository on feature branches. What settings should I use to make the process as smooth as possible?
To ensure a smooth process for scripts pushing changes to a GitHub repository on feature branches, consider the following settings and best practices:
-
Branch Protection Rules:
- Enable branch protection rules to prevent direct pushes to the main branch. This ensures that all changes go through a pull request (PR) process.
- Require status checks to pass before merging. This can include automated tests or other CI/CD checks.
-
Commit Messages:
- Use meaningful and descriptive commit messages. This helps in understanding the changes and tracking the history of the project¹(https://dev.to/keshav___dev/best-practices-while-pushing-code-to-github-5a7e).
Markdown とは、元々John Gruber氏のこちらのブログで仕様説明が発表されてから色んなシステムが使っています。
検索すれば様々な情報が出ますが、基礎の基礎として:
テキストにボルド体にするには:
**ボルド体**
日本語では珍しいかもしれないけど イタリック体 もあり:
I call a dictionary file from my nupass.nu password generator command, which is simply a file with one Japanese word or phrase per line. I wanted to be able to easily add words to the dictionary file, followed by a quick git commit, hence this nushell
script.
In this case, it's easy to just add those commands to nushell
's env.nu
instead of having them as a separate script file. Once added, I just reloaded nushell
, and then it was just a matter of doing the following to add the words to the file:
> dict add onepiece golgo13 dragonball naruto doraemon
See the screenshot below for what the output looks like.
This nushell command randomly retrieves a specified number of words from a dictionary file (English with Japanese words added by @rickcogley) less than or equal to a given parameter's length, formats the words randomly with capitalization, then separates the words with some random symbols and numbers to return a password.
To use:
- Get the dictionary file to your system using nushell's
http
:
http get https://raw.githubusercontent.com/RickCogley/jpassgen/master/genpass-dict-jp.txt | save genpass-dict-jp