| """ | |
| This script was used to create the figures for http://jrsmith3.github.io/sample-logs-the-secret-to-managing-multi-person-projects.html from a PDF file containing some old CMU sample logs. | |
| """ | |
| import PyPDF2 | |
| from wand.image import Image | |
| import io | |
| import os |
Let's say alice is a github.com user, with 2 or more private repositories repoN.
For this example we'll work with just two repositories named repo1 and repo2
https://github.com/alice/repo1
https://github.com/alice/repo2
You need to be to pull from these repositories without entering a passwords probably on a server, or on multiple servers.
You want to perform git pull origin master for example, and you want this to happen without asking for a password.
| [ | |
| { | |
| "event": "send", | |
| "msg": { | |
| "ts": 1365109999, | |
| "subject": "This an example webhook message", | |
| "email": "example.webhook@mandrillapp.com", | |
| "sender": "example.sender@mandrillapp.com", | |
| "tags": [ | |
| "webhook-example" |
If you import live data into Google Docs spreadsheets using the importdata function and you want to force a refresh at a certain interval, but you also want to ensure that some cache-busting goes on, append a querystring that's the epoch time value that the refresh occurs, so for a sheet that should grab new data every hour you could force an update like this:
importData("http://example.com/data.csv?" & hour(googleclock()) & ")")
But the url requested looks like this: http://example.com/data.csv?11 if the refresh happened at 11am. The next day at 11, the url will be the same, so there's a chance you may get cached data. To get around this, use an epoch time-based refresh. The formula:
=((date(year(googleclock()),month(googleclock()),day(googleclock())) & " " & time(hour(googleclock()), 0, 0)) - DATE( 1970;1;1))*86400
gives you the epoch timestamp for the time at the current hour. If you wanted the timest
| # When using a CI server, like Jenkins, in conjunction with github, you may wish to use | |
| # multiple deploy keys (github-speak for an rsa key pair that has been assigned to a single | |
| # repo, rather than a user) to allow Jenkins to pull code from the github repositories | |
| # In the example here, where three repos are used, the idea is to take advantage of ssh's config mechanism | |
| # For use with Jenkins, do the following: | |
| # login to your CI Server | |
| sudo su jenkins | |
| cd ~/.ssh/ |
| web: node app.js | |
| worker: node consumer.js |