- Fix for pg_without_sudo; Wasn't adding -U to args
- New feature that will ALTER USER/Password with any change to pg_password. Random passwords will cause each cap setup to run the ALTER USER, but that's fine as a user should technically only be using setup initially. It's not that hard to obtain the new password if this happens.
- New redaction for logging of passwords & SSHKIT 1.17.0 in gemspec
- README updates
- Quick fix for fetch(:pg_database) on extension adding
- Code cleanup
- Removal of legacy add hstore method
- Using execute and test properly so we can see what the gem is doing in the STDOUT
- Expanded remove_all task to actually cover everything
- Added deploy config option pg_generate_random_password, instead of using it by default when pg_password is excluded
- issues/53: Bug fixed for updates to the archetype when using random password
- projects/1: Prep for RSPEC testing project
- Added back set :pg_ask_for_password, false and ask_for_or_generate_password
- issues/47: Added new pg_template helper code to handle maintaining the randomly generated password, :pg_ask_for_password, and user set pg_password
- Added the rest of the supported options for the database.yml
- pull/46 (Thanks to Tom Prats / tomprats): Fix for pg_host when localhost is used
- Removed system_user as it's not necessary if server values are defined properly in config/deploy/* files
- General cleanup of notes
- Fixed create database and user tasks to use (:pg_system_db) and psql_on_db
- Removing require 'pry' (silly mistake)
- :pg_without_sudo added (thanks to snake66) so you can run remote psql commands on environments without sudo available.
- Fixed exists? methods, removing the need for arguments
- Printing sudo status to capistrano STDOUT
- Switched back from CREATE ROLE to CREATE USER (so LOGIN rights are granted automatically)
- :remove_yml_files task added to clean up old files on remote server
- Fixed quoting on CREATE USER so we can include integers in usernames & Quoted other values like CREATE DATABASE so they can include integers too
- Changed to createuser convention "CREATE ROLE" instead of USER (v4.4.1 reversed this)
- issues/27: raise on :deploy_to with ~ in it
- Net::SCP.upload! to replace old upload! for using :system_user
- issues/31 : psql -> psql_simple so user can be created regardless of database existence
- General cleanup
- change
on roles(:db, primary: true)
to the correcton primary :db
- add
pg_extensions
option andadd_extensions
orremove_extensions
methods, to handle various extensions as needed (@twetzel)
- automatically set
pg_host
option to the IP address of primarydb
host when there are multiple release nodes (@bruno-)
- enable setting DB environment with
rails_env
option. Ifrails_env
is not set,stage
option is used as until now. (@bruno-) - create a task that helps with the upgrade to gem version 4 (@bruno-)
- optionally create a hstore extension on the server (@rhomeister)
database.yml
is now copied to all release_roles (@rhomeister)- introduce archetype
database.yml
that is stored on primarydb
node and is copied to allrelease
nodes onsetup
task (@rhomeister)
- all the work is moved to the
setup
task
- shorten variable names: postgresql -> pg
- better helpers module separation
- lots of code styling updates
- lots of code improvements
- less layered and simpler code
- readme updates
- all the v1.0.0 features