-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
718 lines (332 loc) · 23.5 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
<!DOCTYPE html>
<!--[if IEMobile 7 ]><html class="no-js iem7"><![endif]-->
<!--[if lt IE 9]><html class="no-js lte-ie8"><![endif]-->
<!--[if (gt IE 8)|(gt IEMobile 7)|!(IEMobile)|!(IE)]><!--><html class="no-js" lang="en"><!--<![endif]-->
<head>
<meta charset="utf-8">
<title>Himanshu Gilani</title>
<meta name="author" content="Himanshu Gilani">
<meta name="description" content="In this part we would configure chef workstation that we created in Part 1 to provision nodes on the Rackspace cloud provider. Chef Terminology …">
<!-- http://t.co/dKP3o1e -->
<meta name="HandheldFriendly" content="True">
<meta name="MobileOptimized" content="320">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="canonical" href="http://hgilani.github.com/">
<link href="/favicon.png" rel="icon">
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet" type="text/css">
<script src="/javascripts/modernizr-2.0.js"></script>
<script src="/javascripts/ender.js"></script>
<script src="/javascripts/octopress.js" type="text/javascript"></script>
<link href="/atom.xml" rel="alternate" title="Himanshu Gilani" type="application/atom+xml">
<!--Fonts from Google"s Web font directory at http://google.com/webfonts -->
<link href="http://fonts.googleapis.com/css?family=PT+Serif:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<link href="http://fonts.googleapis.com/css?family=PT+Sans:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-34055934-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</head>
<body >
<header role="banner"><hgroup>
<h1><a href="/">Himanshu Gilani</a></h1>
<h2>Web Developer and Entrepreneur. Founder of mementodb.com</h2>
</hgroup>
</header>
<nav role="navigation"><ul class="subscription" data-subscription="rss">
<li><a href="/atom.xml" rel="subscribe-rss" title="subscribe via RSS">RSS</a></li>
</ul>
<form action="http://google.com/search" method="get">
<fieldset role="search">
<input type="hidden" name="q" value="site:hgilani.github.com" />
<input class="search" type="text" name="q" results="0" placeholder="Search"/>
</fieldset>
</form>
<ul class="main-navigation">
<li><a href="/">Blog</a></li>
<li><a href="/blog/archives">Archives</a></li>
</ul>
</nav>
<div id="main">
<div id="content">
<div class="blog-index">
<article>
<header>
<h1 class="entry-title"><a href="/blog/2014/04/12/configuring-a-vagrant-vm-as-chef-workstation-part-2/">Configuring a Vagrant VM as Chef Workstation: Part 2</a></h1>
<p class="meta">
<time datetime="2014-04-12T08:19:00+00:00" pubdate data-updated="true">Apr 12<span>th</span>, 2014</time>
| <a href="/blog/2014/04/12/configuring-a-vagrant-vm-as-chef-workstation-part-2/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>In this part we would configure chef workstation that we created in <a href="http://himanshu.gilani.info/blog/2013/11/12/configuring-a-vagrant-vm-as-chef-workstation-part-1/">Part 1</a> to provision nodes on the Rackspace cloud provider.</p>
<h2>Chef Terminology</h2>
<p>Before we go over details of how to provision a Rackspace VM, lets review the chef terminology so that we have some common vocabulary</p>
<ul>
<li><strong>Nodes</strong>: Servers, VMs or physical machines or cloud instances.</li>
<li><strong>Cookbook</strong>: A cookbook is a collection of recipes, attributes, and templates that Chef uses to package, distribute, and share configuration details. A chef repository can have many cookbooks and typically a cookbook configures only one service.</li>
<li><strong>Roles</strong>: Roles are a way to group nodes by the function. Each role is associated with a run_list i.e. a set of cookbook/recipies that need to execute in given sequence for configuring the node. Nodes can have multiple roles.</li>
<li><strong>Environments</strong>: In chef different nodes could belong to different environments like dev, stage, prod, etc. Like roles environments also have a run_list.</li>
<li><strong>Data Bags</strong>: Data bags are like cookbook attributes but are used to store sensitive information like passwords, api keys, secrets, etc.</li>
</ul>
</div>
<footer>
<a rel="full-article" href="/blog/2014/04/12/configuring-a-vagrant-vm-as-chef-workstation-part-2/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/11/12/configuring-a-vagrant-vm-as-chef-workstation-part-1/">Configuring a Vagrant Vm as Chef Workstation Part 1</a></h1>
<p class="meta">
<time datetime="2013-11-12T00:00:00+00:00" pubdate data-updated="true">Nov 12<span>th</span>, 2013</time>
| <a href="/blog/2013/11/12/configuring-a-vagrant-vm-as-chef-workstation-part-1/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p><a href="http://vagrantup.com">Vagrant</a> is a powerful tool as it allows us to create “lightweight, reproducible, and portable” Virtual Machines (VM) on the developer machine using provisioning tools like chef and puppet. If you are using chef as the provisioning tool then you would already know that vagrant VM already has <code>chef-client</code> tool installed along with the version of ruby. Since the vagrant VM already has <code>chef-client</code> and <code>ruby</code> it should be straightforward to use any vagrant VM as a workstation for working the Hosted Chef server for provisioning and maintaining VMs in cloud services like AWS and Rackspace. However, I found this not to be the case and I realized that the process of configuring a chef workstation is rather convoluted as both the version of chef-client and its pre-requisite ruby are really old versions of the software that result in all sorts of errors on trying to use the latest chef plug-ins and services. In the end after a lot of trial and error I came to realize that before you can Vagrant VM as chef workstation you need to configure latest version of chef and ruby.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/11/12/configuring-a-vagrant-vm-as-chef-workstation-part-1/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/03/03/scripting-google-analytics-part-2-logging-custom-variables-and-tracking-traffic-sources/">Scripting Google Analytics: Part 2 - Logging, Custom Variables & Traffic Sources</a></h1>
<p class="meta">
<time datetime="2013-03-03T21:19:00+00:00" pubdate data-updated="true">Mar 3<span>rd</span>, 2013</time>
| <a href="/blog/2013/03/03/scripting-google-analytics-part-2-logging-custom-variables-and-tracking-traffic-sources/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>In <a href="http://himanshu.gilani.info/blog/2013/01/16/scripting-google-analytics-part-1-tracking-pages-and-events/">part 1</a> of this post I explained how to track page views and events in <a href="http://www.google.com/analytics/">Google Analytics</a>. In this post I will explain</p>
<ol>
<li>How to use Google Analytics for logging data and javascript errors.</li>
<li>Custom Variables in Google Analytics.</li>
<li>How to use Google Analytics for track traffic sources.</li>
</ol>
</div>
<footer>
<a rel="full-article" href="/blog/2013/03/03/scripting-google-analytics-part-2-logging-custom-variables-and-tracking-traffic-sources/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/01/16/scripting-google-analytics-part-1-tracking-pages-and-events/">Scripting Google Analytics: Part 1 - Tracking Pages and Events</a></h1>
<p class="meta">
<time datetime="2013-01-16T11:31:00+00:00" pubdate data-updated="true">Jan 16<span>th</span>, 2013</time>
| <a href="/blog/2013/01/16/scripting-google-analytics-part-1-tracking-pages-and-events/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p><a href="http://www.google.com/analytics">Google Analytics</a> is a free web analytics tool from Google that you can use for tracking website statistics like page views, traffic sources, audience information, goals, funnels, etc. While a lot of the stuff is tracked automatically, it becomes overwhelming pretty quickly if you want to track customize analytics or want to track or create custom metrics. In this post, I will detail things I learned by experimenting with Google Analytics.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/01/16/scripting-google-analytics-part-1-tracking-pages-and-events/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/01/12/introduction-to-ldap/">Introduction to LDAP</a></h1>
<p class="meta">
<time datetime="2013-01-12T01:53:00+00:00" pubdate data-updated="true">Jan 12<span>th</span>, 2013</time>
| <a href="/blog/2013/01/12/introduction-to-ldap/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>LDAP is definitely not a buzz word technology these days, however a lot of organizations are still using LDAP. So, at some point in time you may be required to develop or maintain projects using LDAP. But since LDAP is an archaic technology, it is tough to discover right information about it on the web. Whenever I searched for it on the web, I found the right information filled with technical jargon and scattered across various articles. This post is my attempt at explaining everything you need to know to understand how LDAP protocol works.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/01/12/introduction-to-ldap/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/12/10/why-i-love-git/">Why I Love Git</a></h1>
<p class="meta">
<time datetime="2012-12-10T11:05:00+00:00" pubdate data-updated="true">Dec 10<span>th</span>, 2012</time>
| <a href="/blog/2012/12/10/why-i-love-git/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Recently I was in a discussion with couple of friends who still have to migrate on to the Git version control system. My friends had a lot of questions and showed hesitation in moving from SVN to Git. This post articulates my thoughts on why you should use Git and contains links to some excellent resources on Git that you can use to understand Git quickly.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2012/12/10/why-i-love-git/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/10/17/npm-features-and-options-demystified/">NPM Features and Options Demystified</a></h1>
<p class="meta">
<time datetime="2012-10-17T16:58:00+00:00" pubdate data-updated="true">Oct 17<span>th</span>, 2012</time>
| <a href="/blog/2012/10/17/npm-features-and-options-demystified/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>In the previous post, <a href="http://himanshu.gilani.info/blog/2012/07/29/npm-and-package-dot-json/">NPM and package.json</a>, I discussed how NPM and package.json could be used for managing the project and its dependencies. In this post I will discuss some of the overlooked features of NPM that help you in achieving more out of this tool</p>
<h2>npm install and package versions</h2>
<p><code>npm install {package}</code> by default installs the package version tagged as “latest” in the npm registry. If you do not want the latest version of the package then you have few options. You can execute commands in the following way to control which package should be installed and from where to fetch the package.</p>
<p><strong>Package with Specific Version:</strong> <code>npm install {package}@{version}</code></p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>npm install [email protected]</span></code></pre></td></tr></table></div></figure>
<p>This command will install version 3.0.0 of express package form npm registry.</p>
<p><strong>Package in a Version Range:</strong> <code>npm install {package}@"{version range}"</code></p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>npm install sax@">=0.1.0 <0.2.0"</span></code></pre></td></tr></table></div></figure>
<p>This command will install sax package between version range 0.1.0 and 0.2.0</p>
</div>
<footer>
<a rel="full-article" href="/blog/2012/10/17/npm-features-and-options-demystified/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/09/27/why-memento-moved-from-java-to-couchapps-to-node-dot-js-technology-stack/">Why Memento Moved From Java to CouchApps to Node.js Technology Stack</a></h1>
<p class="meta">
<time datetime="2012-09-27T19:53:00+00:00" pubdate data-updated="true">Sep 27<span>th</span>, 2012</time>
| <a href="/blog/2012/09/27/why-memento-moved-from-java-to-couchapps-to-node-dot-js-technology-stack/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p><a href="http://mementodb.com">Memento</a>, the app that I launched recently has already seen three technology stack changes. I started working on memento to be able to keep what I find on web with me as a personal memento. Being a Java architect I kicked off memento using Java. Since I was a solo developer on this project I wanted to keep everything lean in order to iterate quickly. This meant having an automatic code generation for the boilerplate code, using simple and powerful frameworks, following best practices, and tons of unit tests for making changes quickly and verifying the health of the app.</p>
<h2>Spring Roo</h2>
<p>With my lean strategy in mind I quickly used <a href="http://www.springsource.org/spring-roo"><strong>Spring Roo</strong></a>, a rapid application development tool for Java developers to generate the complete app with front-end, back-end, authentication, persistence, logging, and unit tests within couple of hours. So far I was happy.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2012/09/27/why-memento-moved-from-java-to-couchapps-to-node-dot-js-technology-stack/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/09/26/bootstraping-a-node-dot-js-app-for-dev-slash-prod-environment/">Bootstraping a Node.js App for Dev/Prod Environment</a></h1>
<p class="meta">
<time datetime="2012-09-26T19:30:00+00:00" pubdate data-updated="true">Sep 26<span>th</span>, 2012</time>
| <a href="/blog/2012/09/26/bootstraping-a-node-dot-js-app-for-dev-slash-prod-environment/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Setting up a web server in node is really simple. A <a href="http://nodeguide.com/beginner.html#a-hello-world-http-server">basic hello world http server</a> can be written in under 10 lines. However, if you want to write a production grade app then you are better of by using any framework that provides foundation and structure to your logic. When choosing frameworks there are no right or wrong answers. Important thing is to select a framework that is being actively developed, has community support and most of important of all you love the way it works.</p>
<h2>Bootstrap a Node.js App with Express Application</h2>
<p><a href="http://expressjs.com">Express</a> is a web application framework for Node.js. It is simple to use and can be configured to work with popular technologies. To understand how Express works you can follow the <a href="http://expressjs.com/guide.html">Getting Started</a> page on the express web site. This guide also explains <a href="http://expressjs.com/guide.html#executable">how to use the express global executable</a> for generating a skeleton web app.</p>
<p>Once you have generated a skeleton web application. You need to understand how to structure the skeleton app for the Dev/Prod parity as well as making few changes to the app for making your app modular.</p>
<h3>Dev/Prod parity</h3>
<p>You will notice following snippet in the skeleton app</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>app.configure('development', function(){
</span><span class='line'> app.use(express.errorHandler());
</span><span class='line'>});</span></code></pre></td></tr></table></div></figure>
</div>
<footer>
<a rel="full-article" href="/blog/2012/09/26/bootstraping-a-node-dot-js-app-for-dev-slash-prod-environment/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/09/17/introducing-memento/">Introducing Memento</a></h1>
<p class="meta">
<time datetime="2012-09-17T06:19:00+00:00" pubdate data-updated="true">Sep 17<span>th</span>, 2012</time>
| <a href="/blog/2012/09/17/introducing-memento/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Here is a wonderful application that allows you to save any web page that you like. It is your personal space with all that you like on the web. Some space that you can access whenver you like. You can create an account at <a href="http://www.mementodb.com">www.mementodb.com</a></p>
<h2>What are mementos?</h2>
<p>Mementos are anything that you save using this application. You can think of a memento as a copy of the entire web page saved into your account for you to <strong>“use”</strong> later. When we say <strong>“use”</strong> we really mean you should be able to read, edit or print the mementos. For creating mementos we convert web pages that you want to collect into a text format that any one can edit without understanding the techonolgies of the web.</p>
<h2>Why Use Memento?</h2>
<p>Web is constantly changing, pages that you bookmark today may vanish tomorrow. But what if you found something on web that you want to keep as a personal memento. With Memento you can <strong>Save</strong>, <strong>Collect</strong> and <strong>Use</strong> your web.</p>
<h2>How it Works?</h2>
<p>Memento provides a bookmarklet that converts the web page you want to keep into Markdown and saves it to your account.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2012/09/17/introducing-memento/">Read on →</a>
</footer>
</article>
<div class="pagination">
<a class="prev" href="/blog/page/2/">← Older</a>
<a href="/blog/archives">Blog Archives</a>
</div>
</div>
<aside class="sidebar">
<section>
<h1>Recent Posts</h1>
<ul id="recent_posts">
<li class="post">
<a href="/blog/2014/04/12/configuring-a-vagrant-vm-as-chef-workstation-part-2/">Configuring a Vagrant VM as Chef Workstation: Part 2</a>
</li>
<li class="post">
<a href="/blog/2013/11/12/configuring-a-vagrant-vm-as-chef-workstation-part-1/">Configuring A Vagrant Vm As Chef Workstation Part 1</a>
</li>
<li class="post">
<a href="/blog/2013/03/03/scripting-google-analytics-part-2-logging-custom-variables-and-tracking-traffic-sources/">Scripting Google Analytics: Part 2 - Logging, Custom Variables & Traffic Sources</a>
</li>
<li class="post">
<a href="/blog/2013/01/16/scripting-google-analytics-part-1-tracking-pages-and-events/">Scripting Google Analytics: Part 1 - Tracking Pages and Events</a>
</li>
<li class="post">
<a href="/blog/2013/01/12/introduction-to-ldap/">Introduction to LDAP</a>
</li>
</ul>
</section>
<section>
<h1>GitHub Repos</h1>
<ul id="gh_repos">
<li class="loading">Status updating…</li>
</ul>
<a href="https://github.com/hgilani">@hgilani</a> on GitHub
<script type="text/javascript">
$.domReady(function(){
if (!window.jXHR){
var jxhr = document.createElement('script');
jxhr.type = 'text/javascript';
jxhr.src = '/javascripts/libs/jXHR.js';
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(jxhr, s);
}
github.showRepos({
user: 'hgilani',
count: 5,
skip_forks: false,
target: '#gh_repos'
});
});
</script>
<script src="/javascripts/github.js" type="text/javascript"> </script>
</section>
<section>
<h1>Latest Tweets</h1>
<ul id="tweets">
<li class="loading">Status updating…</li>
</ul>
<script type="text/javascript">
$.domReady(function(){
getTwitterFeed("hgilani", 5, false);
});
</script>
<script src="/javascripts/twitter.js" type="text/javascript"> </script>
<a href="http://twitter.com/hgilani" class="twitter-follow-button" data-show-count="false">Follow @hgilani</a>
</section>
</aside>
</div>
</div>
<footer role="contentinfo"><p>
Copyright © 2014 - Himanshu Gilani -
<span class="credit">Powered by <a href="http://octopress.org">Octopress</a></span>
</p>
</footer>
<script type="text/javascript">
var disqus_shortname = 'hgilani';
var disqus_script = 'count.js';
(function () {
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = 'http://' + disqus_shortname + '.disqus.com/' + disqus_script;
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
}());
</script>
<script type="text/javascript">
(function(){
var twitterWidgets = document.createElement('script');
twitterWidgets.type = 'text/javascript';
twitterWidgets.async = true;
twitterWidgets.src = 'http://platform.twitter.com/widgets.js';
document.getElementsByTagName('head')[0].appendChild(twitterWidgets);
})();
</script>
</body>
</html>