|After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work.|
|The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0."|
|Database files have to be updated before starting the server, here are the steps that had to be followed:|
|# need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default|
|brew unlink postgresql|
|brew install email@example.com|
|brew unlink firstname.lastname@example.org|
|brew link postgresql|
|<F1>||Causes Netrw to issue help|
|<cr>||Netrw will enter the directory or read the file|
|<del>||Netrw will attempt to remove the file/directory|
|-||Makes Netrw go up one directory|
|a||Toggles between normal display, hiding (suppress display of files matching g:netrw_list_hide) showing (display only files which match g:netrw_list_hide)|
|c||Make browsing directory the current directory|
|C||Setting the editing window|
|d||Make a directory|
Install Apache with Homebrew
# Start by stopping the built-in Apache, if it's running, and prevent it from starting on boot. # This is one of very few times you'll need to use sudo: sudo launchctl unload /System/Library/LaunchDaemons/org.apache.httpd.plist 2>/dev/null # We need to tap homebrew-dupes because "homebrew-apache/httpd22" relies on "homebrew-dupes/zlib" # and install Apache 2.2 with the event MPM, and we'll use Homebrew's OpenSSL library
I’m a web app that wants to allow other web apps access to my users’ information, but I want to ensure that the user says it’s ok.
I can’t trust the other web apps, so I must interact with my users directly. I’ll let them know that the other app is trying to get their info, and ask whether they want to grant that permission. Oauth defines a way to initiate that permission verification from the other app’s site so that the user experience is smooth. If the user grants permission, I issue an AuthToken to the other app which it can use to make requests for that user's info.
Note on encryption
Oauth2 has nothing to do with encryption -- it relies upon SSL to keep things (like the client app’s shared_secret) secure.