Anna Anks Nowak matisnape

#Getting Started

##Webpage:

<html>
<head>
    <title>Testing with Ruby and Selenium WebDriver</title>
</head>
 
<body bgcolor="antiquewhite">

Exporting (iCloud) Keychain and Safari credentials to a CSV file

Update (October 2021)

Exporting password + one-time code data from iCloud Keychain is now officially supported in macOS Monterey and Safari 15 (for Monterey, Big Sur, and Catalina). You can access it in the Password Manager’s “gear” icon (System Preferences > Passwords on Monterey, and Safari > Passwords everywhere else), or via the File > Export > Passwords... menu item). You shouldn't need to hack up your own exporter anymore.

Original, Obsolete Content (2014)

After my dad died, I wanted to be able to have access any of his online accounts going forward. My dad was a Safari user and used iCloud Keychain to sync his credentials across his devices. I don’t want to have to keep an OS X user account around just to access his accounts, so I wanted to export his credentials to a portable file.

The Imposter's Handbook

This a collection of interesting links found in The Imposter's Handbook by Rob Conery.

Content:

Introduction
A Little History
The Tools
Customizing The Terminal

Free O'Reilly books and convenient script to just download them.

Thanks /u/FallenAege/ and /u/ShPavel/ from this Reddit post

How to use:

Take the download.sh file and put it into a directory where you want the files to be saved.
cd into the directory and make sure that it has executable permissions (chmod +x download.sh should do it)
Run ./download.sh and wee there it goes. Also if you do not want all the files, just simply comment the ones you do not want.

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

Clone some repo (you've probably already done this step)
```
git clone [email protected]
```

Setting up flask app in heroku with a database

The below article will cover the intricacies of setting up databases and heroku in respect to a flask app. This is more like a memo and will have out of sequence instructions or solutions to errors so read thoroughly.

Setting up a database

You'll need the packages

	=Navigating=
	visit('/projects')
	visit(post_comments_path(post))

	=Clicking links and buttons=
	click_link('id-of-link')
	click_link('Link Text')
	click_button('Save')
	click('Link Text') # Click either a link or a button
	click('Button Value')

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
	Version 2, December 2004

	Copyright (C) 2013 Yannick Albert <http://yckart.com>

	Everyone is permitted to copy and distribute verbatim or modified
	copies of this license document, and changing it is allowed as long
	as the name is changed.

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE

	feature 'Enrolment' do
	scenario 'Enrolling in a course' do
	given_there_is_a_course
	and_i_am_logged_in_as_a_learner
	when_i_enrol_on_a_course
	then_the_course_should_appear_in_my_courses
	end

	def given_there_is_a_course
	@course = FactoryGirl.create(:course)

	This builds off the excellent work of @lmarkus.

	The scripts below can be used in conjunction with the Slack Emoji Tools Google Chrome extension to export emojis from
	one Slack team and import into another team.

	Original work here: https://gist.github.com/lmarkus/8722f56baf8c47045621