-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
executable file
·1164 lines (773 loc) · 60.1 KB
/
Copy pathindex.html
File metadata and controls
executable file
·1164 lines (773 loc) · 60.1 KB
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
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!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>Atwam</title>
<meta name="author" content="Atwam">
<meta name="description" content="Being a data scientist (yup, that what we are called nowadays, apparently we are all the rage) and looking for my first bike to buy made me think (a …">
<!-- 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://blog.atwam.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="Atwam" 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-29496128-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="/">Atwam</a></h1>
<h2>I do stuff, and write about it</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:blog.atwam.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/2016/02/03/motorbike-prices-part-1/">Motorbike Prices</a></h1>
<p class="meta">
<time datetime="2016-02-03T20:13:00+00:00" pubdate data-updated="true"></time>
</p>
</header>
<div class="entry-content"><p>Being a <em>data scientist</em> (yup, that what we are called nowadays, apparently we are all the rage) and looking for my first bike to buy made me think (a lot) about what ride wanted.</p>
<p>Hundreds of pages on various forums talking about which bike is good, which one is better, reliability, position, torque, sound, etc etc.
Yet in the end, once you have set your mind on one or two models, you still have dozens (if not hundreds) of classifieds for these models, and it is sometime hard to know whether the price is fair, a good deal, or an overpriced deal.</p>
<p>So, having lots of time on my hands at the moment, I started taking a quantitative approach.</p>
<ul>
<li>Step 1 : Get all the data (or as much as I can).</li>
<li>Step 2 : Analysis, model</li>
<li>Step 3 : Profit (now that I have a model, I can know whether any ad is a good deal or not).</li>
</ul>
</div>
<footer>
<a rel="full-article" href="/blog/2016/02/03/motorbike-prices-part-1/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/06/12/adding-an-app-server-to-our-box/">From pow to a deployed rails app using chef, capistrano and vagrant - Part 3</a></h1>
<p class="meta">
<time datetime="2013-06-12T08:47:00+01:00" pubdate data-updated="true"></time>
</p>
</header>
<div class="entry-content"><p>Now that we have a server running our database, we want to make it also able to run our rails app.
As I said in the previous post, I could use the full <code>application</code> cookbook, but I’d have to create my
own cookbook and recipe to use that properly. For now, I’ll just rely on <code>rackbox</code> (and its dependency <code>appbox</code>).</p>
<h2>Managing with <code>appbox</code></h2>
<p>The <code>appbox</code> cookbook does pretty much the stuff that we configured earlier (setting up users etc). Since it’s a dependency of <code>rackbox</code>,
we are pretty much forced to use it (<code>rackbox</code> does call <code>appbox</code> default recipe).</p>
<p>Having added <code>appbox</code> to our <code>Berksfile</code>, I had to modify the <code>roles/base.rb</code> :</p>
<ul>
<li>Let app box know that my admin user name is wam.</li>
<li>Generate a ssh key for to login as the deploy user.</li>
<li>Make sure the app box recipe is run before I run my <code>sudo</code> and <code>users::sysadmins</code> recipe.</li>
</ul>
<p>We’ll start by creating the deploy key :</p>
<figure class='code'><figcaption><span></span></figcaption><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='bash'><span class='line'><span class="nv">$ </span>ssh-keygen -t rsa -C <span class="s2">"wam@scube"</span> -f ~/.ssh/scube_deploy_rsa
</span></code></pre></td></tr></table></div></figure>
<figure class='code'><figcaption><span>roles/base.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">name</span> <span class="s2">"base"</span>
</span><span class='line'><span class="n">description</span> <span class="s2">"Base role applied to all nodes."</span>
</span><span class='line'><span class="n">run_list</span><span class="p">(</span>
</span><span class='line'> <span class="s2">"recipe[apt]"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"recipe[build-essential]"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"recipe[git]"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"appbox"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"recipe[users::sysadmins]"</span><span class="p">,</span> <span class="c1"># Necessary to run after appbox to add our stuff</span>
</span><span class='line'> <span class="s2">"recipe[sudo]"</span> <span class="c1"># Same</span>
</span><span class='line'><span class="p">)</span>
</span><span class='line'><span class="n">override_attributes</span><span class="p">(</span>
</span><span class='line'> <span class="s2">"appbox"</span> <span class="o">=></span> <span class="p">{</span>
</span><span class='line'> <span class="s2">"deploy_keys"</span> <span class="o">=></span> <span class="o">[</span>
</span><span class='line'> <span class="s2">"ssh-rsa [...]"</span> <span class="c1"># content of ~/.ssh/scube_deploy_rsa.pub</span>
</span><span class='line'> <span class="o">]</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"admin_user"</span> <span class="o">=></span> <span class="s2">"wam"</span><span class="p">,</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">)</span>
</span></code></pre></td></tr></table></div></figure>
<h2>Adding a rack server</h2>
<p>I’ve chosen to use passenger + nginx, which is a popular choice among the rails community. I was tempted for a moment by puma on jruby, but I want
my app online faster and will bother changing this kind of thing later (chef makes it easy to test new nodes with new recipes..)</p>
<p>Let’s create a <code>roles/app_server.rb</code> :</p>
<figure class='code'><figcaption><span>roles/app_server.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">name</span> <span class="s2">"app_server"</span>
</span><span class='line'><span class="n">description</span> <span class="s2">"Serving http requests for the app. Main app server"</span>
</span><span class='line'><span class="n">run_list</span><span class="p">(</span>
</span><span class='line'> <span class="s2">"rackbox"</span>
</span><span class='line'><span class="p">)</span>
</span><span class='line'><span class="n">override_attributes</span><span class="p">(</span>
</span><span class='line'> <span class="s2">"rackbox"</span> <span class="o">=></span> <span class="p">{</span>
</span><span class='line'> <span class="s2">"ruby"</span> <span class="o">=></span> <span class="p">{</span>
</span><span class='line'> <span class="s2">"versions"</span><span class="o">=></span> <span class="o">[</span><span class="s2">"1.9.3-p385"</span><span class="o">]</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"global"</span><span class="o">=></span> <span class="s2">"1.9.3-p385"</span>
</span><span class='line'> <span class="p">},</span>
</span><span class='line'> <span class="s2">"apps"</span><span class="o">=></span> <span class="p">{</span>
</span><span class='line'> <span class="s2">"passenger"</span><span class="o">=></span> <span class="o">[</span>
</span><span class='line'> <span class="p">{</span><span class="s2">"appname"</span><span class="o">=></span> <span class="s2">"scube"</span><span class="p">,</span> <span class="s2">"hostname"</span><span class="o">=></span> <span class="s2">"my.hostname.com"</span><span class="p">}</span>
</span><span class='line'> <span class="o">]</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">)</span>
</span></code></pre></td></tr></table></div></figure>
<p>Now to make it work with vagrant, two changes are necessary in our <code>Vagrantfile</code> :</p>
<ul>
<li>We need to make sure that the <code>chef</code> version we are using is 11 or more. By default my vagrant was using chef 10, and the <code>rackbox</code>
(more specifically the <code>runit</code> it uses) was throwing an error (NameError: Cannot find a resource for load_new_resource_state on ubuntu version 12.04).</li>
<li>We add a port mapping to access the http port of our server on <code>localhost:8888</code></li>
</ul>
<figure class='code'><figcaption><span>Vagrantfile</span></figcaption><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>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="c1"># Stuff here</span>
</span><span class='line'><span class="n">config</span><span class="o">.</span><span class="n">vm</span><span class="o">.</span><span class="n">network</span> <span class="ss">:forwarded_port</span><span class="p">,</span> <span class="ss">guest</span><span class="p">:</span> <span class="mi">80</span><span class="p">,</span> <span class="ss">host</span><span class="p">:</span> <span class="mi">8888</span>
</span><span class='line'><span class="c1"># Put this line just before your config.vm.provision :chef_solo line</span>
</span><span class='line'><span class="n">config</span><span class="o">.</span><span class="n">vm</span><span class="o">.</span><span class="n">provision</span> <span class="ss">:shell</span><span class="p">,</span> <span class="ss">:inline</span> <span class="o">=></span> <span class="s2">"gem install chef --version 11.4.2 --no-rdoc --no-ri --conservative"</span>
</span></code></pre></td></tr></table></div></figure>
<p>The <code>:shell</code> provision makes sure that vagrant updates the chef gem before actually running our <code>chef-solo</code> provision.
Now it’s on to <code>vagrant provision</code>, stuff should appear in green and <a href="http://localhost:8888">http://localhost:8888</a> should show a 404 error.
Yes of course, we haven’t deployed our app yet. That’ll be next.</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/06/10/configuring-chef-solo-for-our-servers/">From pow to a deployed rails app using chef, capistrano and vagrant - Part 2</a></h1>
<p class="meta">
<time datetime="2013-06-10T23:03:00+01:00" pubdate data-updated="true"></time>
</p>
</header>
<div class="entry-content"><p>Now that we have our vagrant box working with chef, let’s use chef to configure our services and our app.</p>
<h2>Chef roles</h2>
<p>Assuming that you have read some basics about chef, you’ll know that the cookbooks we have downloaded provide recipes for installing various software.
We could ask vagrant to install a few recipes, but it’s probably better to assemble them in roles.
We’ll then assign the roles to one or several nodes, or use all of them on our box for testing.</p>
<p>For now, we probably want to have one <code>base</code> role (to install common software on all our nodes) and two roles to serve our application :</p>
<ul>
<li><code>database\_master</code> : a simple install of postgres should be fine here.</li>
<li><code>app\_server</code> : this one will serve our RoR app.</li>
</ul>
<p>One could think of other roles (workers, redis etc), but for my purpose and for now these two (and the <code>base</code> role) should be fine.</p>
<h2>Base role</h2>
<p>We want our base role to include the following :</p>
<ul>
<li><em>apt</em>, <em>git</em>, <em>sudo</em> and <em>build-essential</em> should be installed. We’ll use the default cookbooks/recipes for each of these.</li>
<li><em>users setup</em> : Should create the users (with their ssh key), give them sudo rights. We’ll use the <code>users</code> cookbook.</li>
</ul>
<p>We start by editing our <code>Berksfile</code> to make sure all the cookbooks are included (<code>sudo</code>, <code>apt</code>, <code>git</code>, <code>build-essential</code>, <code>users</code>).
Then let’s create a role file.</p>
<figure class='code'><figcaption><span>roles/base.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">name</span> <span class="s2">"base"</span>
</span><span class='line'><span class="n">description</span> <span class="s2">"Base role applied to all nodes."</span>
</span><span class='line'><span class="n">run_list</span><span class="p">(</span>
</span><span class='line'> <span class="s2">"recipe[apt]"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"recipe[build-essential]"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"recipe[git]"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"recipe[users::sysadmins]"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"recipe[sudo]"</span>
</span><span class='line'><span class="p">)</span>
</span></code></pre></td></tr></table></div></figure>
<p><em>The order matters here !</em> <em>apt</em> should appear first (it’s used to handle packages), <em>build-essential</em> is used by pretty much
everything, and especially by <code>ruby-shadow</code> which is a gem dependency of <code>users</code>.</p>
<p>Reading <a href="http://community.opscode.com/cookbooks/users">the documentation of the users cookbook</a>, we see that we should define the users in a data bag
(a way of telling chef about some data, list, including potentially encrypted password and ssh keys).</p>
<p>Chef solo doesn’t work very well with data bags (or the CLI doesn’t work very well), so we’ll just create the file manually.
Also, we see in the users cookbook that it requires <code>chef-solo-search</code> to run with chef-solo.</p>
<p>Adding <code>cookbook 'chef-solo-search', git: "https://github.com/edelight/chef-solo-search.git"</code> to our <code>Berksfile</code> should be good enough.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="nv">$ </span>mkdir data_bags/users
</span><span class='line'><span class="nv">$ </span>vim data_bags/users/wam.json
</span></code></pre></td></tr></table></div></figure>
<figure class='code'><figcaption><span>data_bags/users/wam.json</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
</pre></td><td class='code'><pre><code class='json'><span class='line'><span class="p">{</span>
</span><span class='line'> <span class="nt">"id"</span><span class="p">:</span> <span class="s2">"wam"</span><span class="p">,</span> <span class="err">//or</span> <span class="err">your</span> <span class="err">user</span> <span class="err">name</span>
</span><span class='line'> <span class="err">//</span> <span class="err">The</span> <span class="err">following</span> <span class="err">should</span> <span class="err">be</span> <span class="err">the</span> <span class="err">result</span> <span class="err">of</span> <span class="err">openssl</span> <span class="err">passwd</span> <span class="err">-1</span> <span class="err">plainpasswd</span>
</span><span class='line'> <span class="err">//</span> <span class="err">but</span> <span class="err">that's</span> <span class="err">md5</span> <span class="err">on</span> <span class="err">a</span> <span class="err">mac.</span> <span class="err">Alternatively</span> <span class="err">run</span> <span class="err">mkpasswd</span> <span class="err">-m</span> <span class="err">sha-512</span> <span class="err">-S</span> <span class="err">mySalt</span> <span class="err">on</span> <span class="err">a</span> <span class="err">linux</span> <span class="err">machine</span>
</span><span class='line'> <span class="nt">"password"</span><span class="p">:</span> <span class="s2">"$6$[...]098/"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"ssh_keys"</span><span class="p">:</span> <span class="p">[</span>
</span><span class='line'> <span class="err">//</span> <span class="err">Copy</span> <span class="err">paste</span> <span class="err">from</span> <span class="err">your</span> <span class="err">ssh</span> <span class="err">public</span> <span class="err">key</span>
</span><span class='line'> <span class="s2">"ssh-rsa AAA123...xyz== foo"</span>
</span><span class='line'> <span class="p">],</span>
</span><span class='line'> <span class="nt">"groups"</span><span class="p">:</span> <span class="p">[</span> <span class="s2">"sysadmin"</span> <span class="p">],</span>
</span><span class='line'> <span class="nt">"uid"</span><span class="p">:</span> <span class="mi">2001</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"shell"</span><span class="p">:</span> <span class="s2">"\/bin\/bash"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"comment"</span><span class="p">:</span> <span class="s2">""</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>Now we need to modify our <code>Vagrantfile</code> to use this role (and not the dummy git recipe we were using). An extra bit of precaution is needed here :
the <code>sudo</code> cookbook/recipe will install <code>sudo</code> qnd configure it by default for the sysadmin group (lucky us, our user is a member).
<em>It will override vagrant’s sudo config, breaking vagrant provision using chef-solo</em>. To avoid that, we use vagrant’s <code>chef.json</code> config
to override the <code>sudo</code> configuration attributes for vagrant :</p>
<figure class='code'><figcaption><span></span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'> <span class="n">chef</span><span class="o">.</span><span class="n">add_role</span> <span class="s2">"base"</span>
</span><span class='line'> <span class="n">chef</span><span class="o">.</span><span class="n">json</span> <span class="o">=</span> <span class="p">{</span>
</span><span class='line'> <span class="ss">:authorization</span> <span class="o">=></span> <span class="p">{</span>
</span><span class='line'> <span class="ss">:sudo</span> <span class="o">=></span> <span class="p">{</span>
</span><span class='line'> <span class="ss">:users</span> <span class="o">=></span> <span class="o">[</span><span class="s2">"vagrant"</span><span class="o">]</span><span class="p">,</span>
</span><span class='line'> <span class="ss">:passwordless</span> <span class="o">=></span> <span class="kp">true</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>Then it’s on to <code>vagrant provision</code>, and ssh to whatever port was forwarded to 22 (for me it was <code>ssh localhost -p 2222</code>) to see that you log in
using your ssh key.</p>
<p>If you hit a json parsing exception when chef reads your user json file, make sure you don’t have trailing commas.
You can check your JSON easily in <code>irb</code> using <code>require 'json'; JSON.parse(File.read('data_bags/users/wam.json'))</code>.</p>
<h3>Creating a custom cookbook …</h3>
<p>There’s a big choice to do here. We could either create a whole separate cookbook just for our app, configured with many
default recipes, or for now just use an already created one.</p>
<p>It is very likely that I’ll have to create a cookbook at some point, because it’s the only way to have your own recipes
and reach a high enough level of customization.</p>
<h3>.. or use and existing one</h3>
<p>I originally had a look at the <a href="http://community.opscode.com/cookbooks/database">database cookbook</a> but finally decided
to go the fast way by using two very neat cookbooks, <a href="https://github.com/teohm/rackbox-cookbook">rackbox</a> and <a href="https://github.com/teohm/databox-cookbook">databox</a>.
It will probably make sense to use <code>database</code> and <code>application</code> cookbooks, but they seem to be easier to work with when you are using a proper chef server
and your own cookbook/recipes.</p>
<p><code>rackbox</code> includes <code>appbox</code> by default, which creates its own users for deployment/app running.
I have found that these cookbooks are a bit limited for my taste (for example, they don’t use data_bags, which are a proper way of encrypting
password instead of storing them in your chef repository… Well, next time.</p>
<h2>Setting up our roles</h2>
<p>Let’s start by adding the cookbooks to our <code>Berksfile</code> and run <code>berks install</code></p>
<figure class='code'><figcaption><span>Berksfile</span></figcaption><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='ruby'><span class='line'><span class="n">cookbook</span> <span class="s2">"runit"</span><span class="p">,</span> <span class="s2">">= 1.1.2"</span> <span class="c1"># HACK: force-use this version</span>
</span><span class='line'><span class="n">cookbook</span> <span class="s2">"databox"</span>
</span><span class='line'><span class="n">cookbook</span> <span class="s2">"rackbox"</span>
</span></code></pre></td></tr></table></div></figure>
<p>and create our <code>roles/database_master.rb</code>. We are using non encrypted passwords here, which isn’t very secure.
We should actually use encrypted data bags, but they don’t play very nicely with roles (they are supposed to be used with recipes, which
would mean custom cookbook), nor do they play nicely with <code>knife solo</code> (although a plugin exist, but it didn’t work very well
in my tests). Let’s start this way, we’ll see later to move to a more robust non solo chef.</p>
<figure class='code'><figcaption><span>roles/database_master.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">name</span> <span class="s2">"database_master"</span>
</span><span class='line'><span class="n">description</span> <span class="s2">"Master postgresql node"</span>
</span><span class='line'>
</span><span class='line'><span class="n">run_list</span><span class="p">(</span>
</span><span class='line'> <span class="s2">"databox::postgresql"</span> <span class="c1"># Or "databox" to include mysql as well</span>
</span><span class='line'><span class="p">)</span>
</span><span class='line'><span class="n">default_attributes</span><span class="p">(</span>
</span><span class='line'> <span class="ss">:databox</span> <span class="o">=></span> <span class="p">{</span>
</span><span class='line'> <span class="ss">:db_root_password</span> <span class="o">=></span> <span class="s2">"PASSWORD_HERE"</span><span class="p">,</span>
</span><span class='line'> <span class="ss">:postgresql</span> <span class="o">=></span> <span class="o">[</span>
</span><span class='line'> <span class="p">{</span>
</span><span class='line'> <span class="s2">"database_name"</span> <span class="o">=></span> <span class="s2">"myapp_production"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"username"</span> <span class="o">=></span> <span class="s2">"myapp"</span><span class="p">,</span>
</span><span class='line'> <span class="s2">"password"</span> <span class="o">=></span> <span class="s2">"ANOTHER_PASSWORD_HERE"</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="o">]</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">)</span>
</span></code></pre></td></tr></table></div></figure>
<p>Now running <code>vagrant provision</code> (or <code>vagrant up</code> or <code>vagrant reload</code> depending on whether your current vagrant box is up or not) should run this recipe, adding
the <code>myapp</code> database. We can test that in <code>vagrant ssh</code></p>
<figure class='code'><figcaption><span></span></figcaption><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>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="nv">$ </span>psql -h localhost -d myapp_production -U myapp -W
</span><span class='line'>Password <span class="k">for </span>user myapp:
</span><span class='line'><span class="c">#psql (9.1.9)</span>
</span><span class='line'><span class="c">#[...] Yeepee</span>
</span></code></pre></td></tr></table></div></figure>
<h2>What’s next</h2>
<p>Next post will be about configuring a proper rails box using <code>rackbox</code>, setting up capistrano to deploy … then deploy to a vps and get closer to production.
I’m still not entirely happy with this deployment today. I should move to a proper cookbook, as I said, to get more customization options.
For now, I want my app out, and will probably work a bit more later depending on how successful it is. The beauty of chef, after all, is that it makes
it easy to set up new nodes and new deployments.</p>
<h3>References</h3>
<p><a href="http://teohm.github.io/blog/2013/04/17/chef-cookbooks-for-busy-ruby-developers/">Chef cookbooks for busy ruby developers</a></p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/05/14/using-rspec-with-inherited-resources-helpers-and-inherited-views/">Using Rspec with inherited_resources helpers and inherited views</a></h1>
<p class="meta">
<time datetime="2013-05-14T19:51:00+01:00" pubdate data-updated="true"></time>
</p>
</header>
<div class="entry-content"><p>I have updated a rails app I have been working on recently to a more recent version of rails 3.2, and all my tests where failing.
Finally managed to have that working, figured I’d show how.</p>
<h3>Mocking inherited_resources helpers in views specs.</h3>
<p>I know I shouldn’t be using <a href="https://github.com/josevalim/inherited_resources"><code>inherited_resources</code></a> anymore (<a href="http://stackoverflow.com/questions/9599201/inherited-resources-deperecated-on-rails-3-responders">see here</a> and <a href="http://archives.ryandaigle.com/articles/2009/8/10/what-s-new-in-edge-rails-default-restful-rendering">here</a>) but I want to release my app before I change everything to use responders.</p>
<p>So, my tests where failing because I was using the <code>resource</code>, <code>collection</code> and <code>resource_class</code> helpers from some views I was using. So first my tests are failing because <code>resource_class</code> isn’t available in my views. I would have thought that the controller helpers were available in the views, but they aren’t.
The solution is easy. Let’s add the following to our <code>spec/support</code> directory :</p>
<figure class='code'><figcaption><span>spec/support/view_resource_macros.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
<span class='line-number'>20</span>
<span class='line-number'>21</span>
<span class='line-number'>22</span>
<span class='line-number'>23</span>
<span class='line-number'>24</span>
<span class='line-number'>25</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="k">module</span> <span class="nn">ViewResourceMacros</span>
</span><span class='line'> <span class="k">def</span> <span class="nf">has_resource</span><span class="p">(</span><span class="nb">name</span><span class="p">,</span> <span class="o">&</span><span class="n">block</span><span class="p">)</span>
</span><span class='line'> <span class="n">before</span> <span class="k">do</span>
</span><span class='line'> <span class="c1"># Creates the resource</span>
</span><span class='line'> <span class="vi">@resource</span> <span class="o">||=</span> <span class="k">yield</span>
</span><span class='line'> <span class="c1"># Assign to the symbol we wanted, so it's available in the view</span>
</span><span class='line'> <span class="n">assign</span><span class="p">(</span><span class="nb">name</span><span class="p">,</span> <span class="vi">@resource</span><span class="p">)</span>
</span><span class='line'> <span class="c1"># Assigns to @name so that we can use that in our assertions</span>
</span><span class='line'> <span class="nb">instance_variable_set</span><span class="p">(</span><span class="s2">"@</span><span class="si">#{</span><span class="nb">name</span><span class="si">}</span><span class="s2">"</span><span class="p">,</span> <span class="vi">@resource</span><span class="p">)</span>
</span><span class='line'>
</span><span class='line'> <span class="c1"># If we pass an array, it's for stubing a collection, if not it's for stubbing a single object</span>
</span><span class='line'> <span class="k">if</span> <span class="vi">@resource</span><span class="o">.</span><span class="n">is_a?</span><span class="p">(</span><span class="nb">Array</span><span class="p">)</span>
</span><span class='line'> <span class="n">view</span><span class="o">.</span><span class="n">stub</span><span class="p">(</span><span class="ss">:collection</span><span class="p">)</span> <span class="p">{</span> <span class="vi">@resource</span> <span class="p">}</span>
</span><span class='line'> <span class="n">view</span><span class="o">.</span><span class="n">stub</span><span class="p">(</span><span class="ss">:resource_class</span><span class="p">)</span> <span class="p">{</span><span class="vi">@resource</span><span class="o">.</span><span class="n">first</span><span class="o">.</span><span class="n">class</span><span class="p">}</span>
</span><span class='line'> <span class="k">else</span>
</span><span class='line'> <span class="n">view</span><span class="o">.</span><span class="n">stub</span><span class="p">(</span><span class="ss">:resource</span><span class="p">)</span> <span class="p">{</span><span class="vi">@resource</span><span class="p">}</span>
</span><span class='line'> <span class="n">view</span><span class="o">.</span><span class="n">stub</span><span class="p">(</span><span class="ss">:resource_class</span><span class="p">)</span> <span class="p">{</span><span class="vi">@resource</span><span class="o">.</span><span class="n">class</span><span class="p">}</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'><span class="k">end</span>
</span><span class='line'>
</span><span class='line'><span class="no">RSpec</span><span class="o">.</span><span class="n">configure</span> <span class="k">do</span> <span class="o">|</span><span class="n">config</span><span class="o">|</span>
</span><span class='line'> <span class="n">config</span><span class="o">.</span><span class="n">extend</span> <span class="no">ViewResourceMacros</span><span class="p">,</span> <span class="ss">:type</span> <span class="o">=></span> <span class="ss">:view</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<p>And see how to transform our old (failing) test :</p>
<figure class='code'><figcaption><span>spec/views/cars/edit.html.haml_spec.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">require</span> <span class="s1">'spec_helper'</span>
</span><span class='line'>
</span><span class='line'><span class="n">describe</span> <span class="s2">"cars/edit.html.haml"</span> <span class="k">do</span>
</span><span class='line'> <span class="n">before</span><span class="p">(</span><span class="ss">:each</span><span class="p">)</span> <span class="k">do</span>
</span><span class='line'> <span class="n">assign</span><span class="p">(</span><span class="ss">:car</span><span class="p">,</span> <span class="vi">@car</span> <span class="o">=</span> <span class="no">Factory</span><span class="o">.</span><span class="n">create</span><span class="p">(</span><span class="ss">:car</span><span class="p">))</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'>
</span><span class='line'> <span class="n">it</span> <span class="s2">"renders the edit view"</span> <span class="k">do</span>
</span><span class='line'> <span class="n">render</span>
</span><span class='line'> <span class="n">rendered</span><span class="o">.</span><span class="n">should</span> <span class="n">contain</span><span class="p">(</span><span class="vi">@car</span><span class="o">.</span><span class="n">name</span><span class="p">)</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<p>becomes :</p>
<figure class='code'><figcaption><span>spec/views/cars/edit.html.haml_spec.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">require</span> <span class="s1">'spec_helper'</span>
</span><span class='line'>
</span><span class='line'><span class="n">describe</span> <span class="s2">"cars/edit.html.haml"</span> <span class="k">do</span>
</span><span class='line'> <span class="n">has_resource</span><span class="p">(</span><span class="ss">:car</span><span class="p">)</span> <span class="p">{</span> <span class="no">Factory</span><span class="o">.</span><span class="n">create</span><span class="p">(</span><span class="ss">:car</span><span class="p">)</span> <span class="p">}</span>
</span><span class='line'>
</span><span class='line'> <span class="n">it</span> <span class="s2">"renders the edit view"</span> <span class="k">do</span>
</span><span class='line'> <span class="n">render</span>
</span><span class='line'> <span class="n">rendered</span><span class="o">.</span><span class="n">should</span> <span class="n">contain</span><span class="p">(</span><span class="vi">@car</span><span class="o">.</span><span class="n">name</span><span class="p">)</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<h3>Using shared inherited partial in our views specs</h3>
<p>Rails 3.1+ offers views inheritance, so I changed my code to have the following :</p>
<figure class='code'><figcaption><span></span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="k">class</span> <span class="nc">BaseController</span>
</span><span class='line'>
</span><span class='line'><span class="k">end</span>
</span><span class='line'>
</span><span class='line'><span class="k">class</span> <span class="nc">CarsController</span> <span class="o"><</span> <span class="no">BaseController</span>
</span><span class='line'> <span class="n">inherit_resources</span>
</span><span class='line'><span class="k">end</span>
</span><span class='line'>
</span><span class='line'><span class="k">class</span> <span class="nc">PlanesController</span> <span class="o"><</span> <span class="no">BaseController</span>
</span><span class='line'> <span class="n">inherit_resources</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<p>Then I just created a <code>base/new.html.haml</code> and a <code>base/edit.html.haml</code> views, to use the views inheritance.</p>
<figure class='code'><figcaption><span>base/new.html.haml</span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='haml'><span class='line'><span class="nt">%h1</span> Create <span class="si">#{</span><span class="n">resource_class</span><span class="o">.</span><span class="n">model_name</span><span class="o">.</span><span class="n">human</span><span class="si">}</span>
</span><span class='line'><span class="p">=</span> <span class="n">render</span> <span class="ss">:partial</span> <span class="o">=></span> <span class="s2">"form"</span>
</span></code></pre></td></tr></table></div></figure>
<figure class='code'><figcaption><span>base/edit.html.haml</span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='haml'><span class='line'><span class="nt">%h1</span> Edit <span class="si">#{</span><span class="n">resource</span><span class="si">}</span>
</span><span class='line'><span class="p">=</span> <span class="n">render</span> <span class="ss">:partial</span> <span class="o">=></span> <span class="s2">"form"</span>
</span></code></pre></td></tr></table></div></figure>
<p>And I have two <code>_form.html.haml</code> partials, one for each controller.
Now the next issue is that our edit and new views are shared, but we still want to test the <code>_form.html.haml</code> partial.</p>
<figure class='code'><figcaption><span>spec/views/cars/_form.html.haml_spec.rb</span></figcaption><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>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">require</span> <span class="err">'</span><span class="n">spec_helper</span>
</span><span class='line'>
</span><span class='line'><span class="n">describe</span> <span class="s2">"cars/_form.html.haml"</span> <span class="k">do</span>
</span><span class='line'> <span class="p">{</span>
</span><span class='line'> <span class="kp">new</span><span class="p">:</span> <span class="o">-></span> <span class="p">{</span> <span class="no">Car</span><span class="o">.</span><span class="n">new</span> <span class="p">}</span>
</span><span class='line'> <span class="n">edit</span><span class="p">:</span> <span class="o">-></span> <span class="p">{</span> <span class="no">Factory</span><span class="o">.</span><span class="n">create</span><span class="p">(</span><span class="ss">:car</span><span class="p">)</span> <span class="p">}</span>
</span><span class='line'> <span class="p">}</span><span class="o">.</span><span class="n">each</span> <span class="k">do</span> <span class="o">|</span><span class="nb">name</span><span class="p">,</span> <span class="n">block</span><span class="o">|</span>
</span><span class='line'> <span class="n">context</span> <span class="s2">"when called in #</span><span class="si">#{</span><span class="nb">name</span><span class="si">}</span><span class="s2">"</span> <span class="k">do</span>
</span><span class='line'> <span class="n">has_resource</span><span class="p">(</span><span class="nb">name</span><span class="p">,</span> <span class="n">block</span><span class="p">)</span>
</span><span class='line'>
</span><span class='line'> <span class="n">it</span> <span class="s2">"renders the form"</span> <span class="k">do</span>
</span><span class='line'> <span class="n">render</span>
</span><span class='line'> <span class="n">rendered</span><span class="o">.</span><span class="n">should</span> <span class="n">have_selector</span><span class="p">(</span><span class="s2">"form"</span><span class="p">)</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<h3>Shared partial</h3>
<p>Finally, when testing for example <code>cars/index.html.haml</code> which uses a partial <code>toolbar.html.haml</code> that actually exists in <code>base</code> views, the following lines are necessary :</p>
<figure class='code'><figcaption><span></span></figcaption><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='ruby'><span class='line'><span class="n">before</span> <span class="k">do</span>
</span><span class='line'> <span class="n">views</span><span class="o">.</span><span class="n">lookup_context</span><span class="o">.</span><span class="n">prefixes</span> <span class="o"><<</span> <span class="s2">"base"</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<p>This was <a href="https://github.com/rails/rails/issues/5213">raised as an issue to the rails team</a>, but they commented (rightly I think) that the inheritance
is related to the controller, not the views, so the test case shouldn’t know about it and you’ll have to declare it manually using the lines above.</p>
<p>Now let’s go back and make these tests green again.</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/04/27/preparing-a-rails-app-for-deployment-using-chef-solo/">From pow to a deployed rails app using chef, capistrano and vagrant - Part 1</a></h1>
<p class="meta">
<time datetime="2013-04-27T22:09:00+01:00" pubdate data-updated="true"></time>
</p>
</header>
<div class="entry-content"><p>So, let’s be honest, I’ve been quite lazy here. My latest rails application was deployed with Heroku. Lots of fun, a very pleasant experience.
But now I have this new shinny application that I don’t want to deploy using Heroku :</p>
<ul>
<li>Because I am worried that if I start with Heroku, I’ll be too lazy to switch later.</li>
<li>Because I know that at some point, my application is going to need plugins and binaries that I can’t get on Heroku.</li>
<li>Because I’d rather have a portable application that I can deploy easily on any type of server.</li>
</ul>
</div>
<footer>
<a rel="full-article" href="/blog/2013/04/27/preparing-a-rails-app-for-deployment-using-chef-solo/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/04/25/building-dep-selector-on-mac-os-x/">Building dep_selector on mac os x</a></h1>
<p class="meta">
<time datetime="2013-04-25T23:13:00+01:00" pubdate data-updated="true"></time>
</p>
</header>
<div class="entry-content"><p>Just a quick post, having finally figured out how to install dep_selector on mac os x.
The issue is that having xcode installed which configures <code>clang</code> as the default compiler, some native gems break.</p>
<p>It took me some time, but at long least I can now build a native gem using <code>gcc</code> instead of <code>clang</code> on mac os x.
And you’ll see it’s not very easy to have ruby change its compiler for gems native extensions compilation.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/04/25/building-dep-selector-on-mac-os-x/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/05/11/multiple-persistent-stores-and-seed-data-with-core-data/">Multiple persistent stores and seed data with core data</a></h1>
<p class="meta">
<time datetime="2012-05-11T23:20:00+01:00" pubdate data-updated="true"></time>
</p>
</header>
<div class="entry-content"><p>I haven’t posted anything for a while now, and after hours of trying to find a solution to my problem, I thought I should share. So here we go.</p>
<h3>The problem</h3>
<p>Your nice and shiny iOS app is supposed to have two data components : <strong>User data</strong> and <strong>Seed data</strong>.
For example, you want to have some (seeded) list of postcodes. The size of data is too big to be shipped with your app,
and we assume that the model is too complex to be just filled by your application at runtime from a downloaded csv/txt file.</p>
<p>So, you start thinking that hey, you’ll generate a sqlite database (<em>persistent data store</em> as they say), put it on a server and have your app download and use it.
You can either duplicate the whole stack (<code>NSManagedObjectContext</code>, <code>NSPersistentStoreCoordinator</code> and <code>NSManagedObjectModel</code>) or, according to apple :</p>
<p><em>You typically use configurations if you want to store different entities in
different stores. A persistent store coordinator can only have one managed
object model, so by default each store associated with a given coordinator
must contain the same entities. To work around this restriction, you can
create a model that contains the union of all the entities you want to use.
You then create configurations in the model for each of the subsets of
entities that you want to use. You can then use this model when you create a
coordinator. When you add stores, you specify the different store attributes
by configuration. When you are creating your configurations, though, remember
that you cannot create cross-store relationships.</em></p>
<p>Well, that’s pretty much all the doc you’ll get from apple.
There are a few mentions of this problem <a href="http://stackoverflow.com/questions/9970103/what-is-an-efficient-way-to-merge-two-ios-core-data-persistent-stores">there</a>
<a href="http://stackoverflow.com/questions/10224016/coredata-with-multiple-stores-configuration-woes">or there</a>
but not in a clear enough form for me. So, here’s how it works…</p>
</div>
<footer>
<a rel="full-article" href="/blog/2012/05/11/multiple-persistent-stores-and-seed-data-with-core-data/">Read on →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/02/25/spell-checking-should-be-part-of-your-view-tests/">Spell checking should be part of your view tests</a></h1>
<p class="meta">