After months years of procrastinating, I finally built this thing.
While some content is still missing (like the About Page) and parts are falling off here and there, I’m proud to be at least somewhere.
Thanks to the help of Jekyll, Github Pages, Twitter Bootstrap and many helpful people out there I did most of the “work” in just 1 or 2 days.
(Why did I always want to build my own Website with Rails?)
While I work on the small things (like comments and so) feel free to contact me at manuel.hutter at gmail.com or a social network. (see header)
BTW, is it a bad habit to misuse a Issue tracking system as a ToDo-List?
-
Customize HTML for your theme, add this at the end of <head>
<link href="http://google-code-prettify.googlecode.com/svn/trunk/src/prettify.css" type="text/css" rel="stylesheet"/>
<script src="http://google-code-prettify.googlecode.com/svn/trunk/src/prettify.js" type="text/javascript"></script>
-
Add this to your Body-Tag: onload="prettyPrint()"
-
Done. To actually make use of it, you’ll have to use the HTML-Editor. I recommend the following (HTML5) convention:
<pre class="prettyprint"><code class="language-java">...</code></pre>
Recommended Add this to your custom CSS:
.prettyprint {
overflow-x: auto;
}
If you want a transparent background, add this inside the curly braces: background: none;
Optional To use a Theme, download the desired CSS file (or create your own), upload it to Tumblr and replace the default CSS file in step 1 (blabla…prettify.css) with the URL of your uploaded file. DONE!
(distilled from /dev/null’s post on this topic)
I am Dyslexic of Borg. Fusistance is retile. Your ass will be laminated.
Problem
user@host:~ $ npm install coffee-script
npm http GET https://registry.npmjs.org/coffee-script
npm ERR! Error: SSL Error: SELF_SIGNED_CERT_IN_CHAIN
npm ERR! at ClientRequest.<anonymous> (.../lib/node_modules/npm/node_modules/request/main.js:483:26)
npm ERR! at ClientRequest.g (events.js:156:14)
npm ERR! at ClientRequest.emit (events.js:67:17)
npm ERR! at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1256:7)
npm ERR! at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:91:29)
npm ERR! at CleartextStream.socketOnData [as ondata] (http.js:1288:20)
npm ERR! at CleartextStream._push (tls.js:375:27)
npm ERR! at SecurePair.cycle (tls.js:734:20)
npm ERR! at EncryptedStream.write (tls.js:130:13)
npm ERR! at Socket.ondata (stream.js:38:26)
npm ERR! You may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <npm-@googlegroups.com>
npm ERR!
npm ERR! System Linux 2.6.32.29-0.3-default
npm ERR! command "node" ".../bin/npm" "install" "coffee-script"
npm ERR! cwd /home/user
npm ERR! node -v v0.6.18
npm ERR! npm -v 1.1.21
npm ERR! message SSL Error: SELF_SIGNED_CERT_IN_CHAIN
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/user/npm-debug.log
npm not ok
Solution
user@host:~ $ npm config set strict-ssl false
or
user@host:~ $ npm config set registry="http://registry.npmjs.org/"
Tested under Ubuntu 10.04 LTS and SLES 11 SP1 so far
Prequisites
- openssl
- Custom CA-Cert available as DER file (*.cer)
# Step 0: Convert the Certificate to PEM format
$ openssl x509 -inform der -in certificate.cer -out certificate.pem
# Step 0.5: Make sure there is only 1 Certificate in the File
$ grep 'BEGIN.* CERTIFICATE' ProxyCA.pem | wc -l # should output `1`
# Step 1: Verify it's the correct Certificate
$ openssl x509 -noout -fingerprint -in certificate.pem
# Step 2: Copy the File to /etc/ssl/certs
$ # Do I really have to explain that? If you can't do that on your own you probably shouldn't be installing CA-Certificates anyway...
# Step 3: Find out the Hash of your Cert
$ openssl x509 -noout -hash -in certificate.pem
# Step 4: Inside /etc/ssl/certs, link your certificate to "hash.0"
$ ln -s certificate.crt `openssl x509 -hash -noout -in certificate.crt`.0
Because the solutions I googled didn’t work:
for g in `gem list --no-versions`; do
gem uninstall --all --ignore-dependencies --executables $g
done
In case i forget again…
Problem on Ubuntu 10.04 (Lucid Lynx) x64:
$ sudo aptitude update
Hit http://security.ubuntu.com lucid-security Release.gpg
Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-en_US
Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-en_US
...
Hit http://us.archive.ubuntu.com lucid-updates/multiverse Sources
Reading package lists... Done
Segmentation fault
Solution:
$ sudo rm /var/cache/apt/*.bin
$ sudo apt-get update
Aptitude should now work again.
Redirect everything to dratir.ch:
RewriteEngine On
Rewritecond %{HTTP_HOST} !^dratir\.com
RewriteRule (.*) http://dratir.com/$1 [QSA,R=301,L]