lordofthedanse

Install Homebrew and Jupyter Notebook

1. Open your terminal (on Mac, the default terminal is named ... Terminal)
2. Go to Homebrew and paste script at the top into Terminal

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

3. Install jupyter: brew install jupyter
4. Open a new notebook to confirm: jupyter notebook
5. If you don't have the R kernel when you open a new notebook (and you probably shouldn't), then you'll need to install the IRkernel: from the terminal, open R: then install.packages("IRkernel")
6. Create a Jupyter notebook with the R kernel.

lordofthedanse

  if ENV['PROFILE']
    config.cache_classes = true
    config.eager_load = true

    config.logger = ActiveSupport::Logger.new(STDOUT)
    config.log_level = :info

    config.public_file_server.enabled = true
    config.public_file_server.headers = {
      'Cache-Control' => 'max-age=315360000, public',

lordofthedanse

From the command line:
createuser postgres -s -d (s is for superuser privileges, d is for creating DBs; capital S/D are the negations)

lordofthedanse

Manually:
pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log restart

With homebrew:
brew services restart postgresql (if postgres version is pinned (postgresql@10), then sub postgresql@10 for postgresql)

Can also 
brew services stop postgresql
brew services start postgresql

lordofthedanse

Here are a few gotchas:

1. If you were running spring and didn't stop it before you squashed migrations, spring might have it's database config change (it'll look for the squasher database that was created temporarily). If you want to go back to your development database, just spring stop and then setup your database (however you do that) again.
2. You can run into rake db:migrate problems because the new squashed migration version has not been added to the schema_migrations table that tells Rails what migrations have already been run. Thus, your rake db:migrate command will be trying to create tables (via the squasher XXXX_init_schema migration) that already exist. The solution to this is to manually insert the value of your XXXX_init_schema migration into the schema_migration table:

• psql
• insert into schema_migrations (version) values ('99999999999999');, where the 99999999999999 value is actually the timestamp that appears in the XXXX_init_schema migration.

lordofthedanse

Install Homebrew
1. xcode-select --install
2. ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
3. brew doctor

Install Python3 using Homebrew
1. brew install python3

Install packages for Python3
1. pip3 install [package name without brackets]

lordofthedanse

First, check your current config (example output in homebrew.mxcl.postgresql.plist.xml lower down in this gist):

cat ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist

Most importantly, note the -D /usr/local/var/postgres argument.

Second, shut down your current PostgreSQL.

launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist