rcackermanCC

def clean_words(text):
	weekdays = {'sunday': {'pattern': r'\b(su.*?(n|y))(\W|\s|\b)',
						   'replacement': r'sunday\3'},
				'monday': {'pattern': r'((mo.*?(n|y)(?:s)*)|m)(\W|\s|\b)',
						   'replacement': r'monday\4'},
				'tuesday': {'pattern': r'\b(t(u|y).*?(e|s|y)(?:s)*|t)(\W|\s|\b)',
						   'replacement': r'tuesday\4'},
				'wednesday': {'pattern': r'\b(w|w.*?d(.*?|s|y|t)(?:s)*)(\W|\s|\b)',
							  'replacement': r'wednesday\3'},
				'thursday': {'pattern': r'\b(th|th[a-z]*?(r|s|y|t)(?:s)*)(\W|\s|\b)',

rcackermanCC

Assuming NewA and OldB:

Prep NewA

cd NewA
mkdir NewA
mv *.* NewA/
gc -m "Prep for new repo"
cd ..

rcackermanCC

To know what you want in a secure way, S3 requires a signature. The signature is created by:

1. assembling a canonical requst
2. putting together some parts of the request together with a hashed version of the full request - this is the string to sign
3. creating a signing key
4. using the signing key to create a signature from the string to sign

Step 1

rcackermanCC

SELECT
  table_name,
  column_name,
  data_type,
  col_description(concat('public.',table_name)::regclass, ordinal_position)
FROM information_schema.columns where table_name like '<stuff>';

rcackermanCC

-- base table has id, start_date, end_date

select * from (
  with
  recursive timeline (id, start_date, end_date) as (
    select
      id,
      start_date,
      end_date 
    from base_table

rcackermanCC

heroku apps:create <new instance name>
git remote add <remote name> <new url>
git push <remote name>
heroku addons:add heroku-postgresql:hobby-dev --app <new instance name>
heroku addons:add pgbackups --app <new instance name>
heroku run rake db:setup --app <new instance name>
heroku pgbackups:capture --app <original instance name>
heroku pgbackups:restore <new instance postgres url> `heroku pgbackups:url <backup id> --app <old instance>` --app <new instance>

Get database info for new and old instances: