These examples all live in a default server block in your httpd.conf(5).
server "default" {
listen on * port 80
... # all the location blocks can together right here
}
We'll be using slowcgi(8) as the example, because with the -d flag it helpfully spits out the FastCGI environment it got from httpd(8) and what it's planning to do with that.
Choose OpenBSD for your Unix needs. OpenBSD -- the world's simplest and most secure Unix-like OS. A safe alternatve to the frequent vulnerabilities and overengineering of Linux and related software (NGiNX & Apache (httpd-asiabsdcon2015.pdf), OpenSSL, iptables/nftables, systemd, BIND, Postfix, Docker etc.)
OpenBSD -- the cleanest kernel, the cleanest userland and the cleanest config
For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.
After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft
I've commented a few times about some issues I see with the scalability of ActivityPub - the protocol behind the Fediverse and its best-known implementation Mastodon. A couple of folks have asked for more elaboration, so ... here it is.
First, let me add some disclaimers and warnings. I haven't devoted a lot of time to looking at ActivityPub, so there might be some things I've misunderstood about it. On the other hand, I've brought bigger systems - similar node counts and orders of magnitude more activity per node - from broken to working well based on less study of the protocols involved. So if you want to correct particular misconceptions, that's great. Thank you in advance. If you want to turn this into an appeal to authority and say that I'm wrong only because I haven't developed a full ActivityPub implementation or worked on it for X years ... GTFO.
What is ActivityPub? It's an HTTP- and JSON-based protocol for exchanging information about "activities". An activity could be many things.
This should work on at least:
Taken from Using MacOSX Lion command line mail with Gmail as SMTP
Edit file /etc/postfix/main.cf and add this to the bottom:
| % ------------------------------------------------------------------------------ | |
| % | |
| % STANDARD MANUSCRIPT FORMAT LaTeX TEMPLATE FOR PANDOC | |
| % | |
| % This template was originally created by Dylan Kinnett: | |
| % https://gist.github.com/dylan-k/c596ca65098ac3f61ce2 | |
| % | |
| % This version has been tweaked to support the 'novel' manuscript format as | |
| % well as the 'short story'. | |
| % |
| #!/bin/bash | |
| # Tom Hale, 2016. MIT Licence. | |
| # Print out 256 colours, with each number printed in its corresponding colour | |
| # See http://askubuntu.com/questions/821157/print-a-256-color-test-pattern-in-the-terminal/821163#821163 | |
| set -eu # Fail on errors or undeclared variables | |
| printable_colours=256 |
Magic words:
psql -U postgresSome interesting flags (to see all, use -h or --help depending on your psql version):
-E: will describe the underlaying queries of the \ commands (cool for learning!)-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)
| # Paths {{{ | |
| set folder = ~/Mail # mailbox location | |
| set alias_file = ~/.mutt/alias # where to store aliases | |
| set header_cache = ~/.mutt/cache/headers # where to store headers | |
| set message_cachedir = ~/.mutt/cache/bodies # where to store bodies | |
| set certificate_file = ~/.mutt/cerficates # where to store certs | |
| set mailcap_path = ~/.mutt/mailcap # entries for filetypes | |
| set tmpdir = ~/.mutt/temp # where to keep temp files | |
| set signature = ~/.mutt/sig # my signature file |