sudo service fail2ban restart
tail -f /var/log/fail2ban.log
| #!/bin/bash | |
| # usage: ./duckdb-load.sh data.tsv duckdb tablename | |
| # for example: | |
| # ./duckdb-load.sh ark/hcaf_species_native.tsv duckdb_database hcaf_species_native | |
| # TODO set pragma journal_mode=off or equiv settings | |
| # if using .import and .sep '\t', an error appears: | |
| # Error: multi-character column separators not allowed for import |
I created a crude comparison of the syntax of the various common Markdown extensions to have a better view on what are the most common extensions and what is the most widely accepted syntax for them. The list of Markdown flavors that I looked at was based on the list found on CommonMark's GitHub Wiki.
| Flavor | Superscript | Subscript | Deletion* Strikethrough |
Insertion* | Highlight* | Footnote | Task list | Table | Abbr | Deflist | Smart typo | TOC | Math | Math Block | Mermaid |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GFM |
L`IPFS ou InterPlanetary File System est un protocole pair à pair (p2p) de distribution de contenu adressable par hypermédia. Il permet de "stocker" des fichiers ou des arborescences de fichiers de manière décentralisée et permanente, et d’y accéder via un noeud ipfs ou via un navigateur web. Il permet aussi d’héberger un site web statistique.
Rendez vous sur le site de IPFS et suivez les instructions.
| #!/bin/bash | |
| CLEAR='\033[0m' | |
| RED='\033[0;31m' | |
| function usage() { | |
| if [ -n "$1" ]; then | |
| echo -e "${RED}👉 $1${CLEAR}\n"; | |
| fi | |
| echo "Usage: $0 [-n number-of-people] [-s section-id] [-c cache-file]" |
| # get total requests by status code | |
| awk '{print $9}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | |
| # get top requesters by IP | |
| awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head | awk -v OFS='\t' '{"host " $2 | getline ip; print $0, ip}' | |
| # get top requesters by user agent | |
| awk -F'"' '{print $6}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head | |
| # get top requests by URL |
| # | |
| # CORS header support | |
| # | |
| # One way to use this is by placing it into a file called "cors_support" | |
| # under your Nginx configuration directory and placing the following | |
| # statement inside your **location** block(s): | |
| # | |
| # include cors_support; | |
| # | |
| # As of Nginx 1.7.5, add_header supports an "always" parameter which |
| http { | |
| map $http_user_agent $limit_bots { | |
| default ''; | |
| ~*(google|bing|yandex|msnbot) $binary_remote_addr; | |
| } | |
| limit_req_zone $limit_bots zone=bots:10m rate=1r/m; | |
| server { |