/
index.html
645 lines (604 loc) · 37.4 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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>DavidJB.com</title>
<link rel="stylesheet" href="http://davidjb.com/theme/css/main.css" />
<link href="http://davidjb.com/feeds/all.atom.xml" type="application/atom+xml" rel="alternate" title="DavidJB.com Atom Feed" />
<!--[if IE]>
<script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body id="index" class="home">
<header id="banner" class="body">
<h1><a href="http://davidjb.com/">DavidJB.com <strong>Ramblings about Plone, Pyramid, Python, the web, Linux, and more, by David Beitey.</strong></a></h1>
<nav><ul>
<li><a href="http://davidjb.com/about.html">About me</a></li>
<li><a href="http://davidjb.com/blog/index.html">Blog</a></li>
<li><a href="http://davidjb.com/projects.html">Projects</a></li>
</ul></nav>
</header><!-- /#banner -->
<aside id="featured" class="body">
<article>
<h1 class="entry-title"><a href="http://davidjb.com/blog/2014/07/project-green-house-1-led-replacement-lighting-for-round-cfls/">Project ‘Green’ House #1: <span class="caps">LED</span> replacement lighting for round CFLs</a></h1>
<footer class="post-info">
<abbr class="published" title="2014-07-21T00:00:00">
Published: Mon 21 July 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/environmental.html">Environmental</a>. </p>
<p>tags: <a href="http://davidjb.com/tag/green-house.html">Green House</a> <a href="http://davidjb.com/tag/green.html">Green</a> <a href="http://davidjb.com/tag/energy.html">Energy</a> <a href="http://davidjb.com/tag/environment.html">Environment</a> </p>
</footer><!-- /.post-info --><p>This is the first in a series of ways I’m looking to reduce my environmental
impact at home, and save a significant amount of money at the same time. Over
the course of my <em>Project ‘Green’ House</em> posts, I aim to look at extremely
cost-effective ways of reducing your carbon footprint, improving your power
bill, and generally making life easier at home. Feel free to adopt any of my
ideas for your own uses - I’d love to hear if this has helped you.</p>
<p>This first post is about my aim to replace all the lights in my house with
energy and cost efficient alternatives to standard fluorescent tubes, or
"compact fluorescent lamps" (CFLs). Whilst CFLs are more efficient than
standard filament light bulbs and <em>far</em> more efficient than any halogen bulbs
(such as downlights), they still require mercury, take a while to start up,
and aren’t as energy efficient as LEDs.</p>
<img alt="Before - CFL tube present" src="http://davidjb.com/images/led-lights/IMG_3545.JPG" style="width: 300px;" />
<img alt="After - LED board replacement" src="http://davidjb.com/images/led-lights/IMG_3546.JPG" style="width: 300px;" />
<p>So far, I’ve had success with changing over the most frequently-used lights in
my house — the round CFLs. In my house, these lights are attached to the
ceiling (rather than recessed), have an off-white dome cover over them as a
diffuser, and aren’t the easiest of things to the replace. This is especially
true for many of my lights, which sit at least 3.6 metres off the level, due
to the height of my ceiling in the stairway and bedroom. This is <strong>not</strong>
something I really want to have to change!</p>
<p>Add into the mix that a replacement 32 watt round <span class="caps">CFL</span> is $10 <span class="caps">AUD</span>, a
fluorescent starter is around $1.50 each, plus the time, fuel and energy
required to get these, and making the switch to LEDs, which should hopefully
never need replacing, becomes a sensible solution.</p>
<div class="section" id="materials">
<h2>Materials</h2>
<p>Things I needed to get started were:</p>
<ul class="simple">
<li><span class="caps">LED</span> replacement lights, drivers, magnets for fitting (see below)</li>
<li>Tools for removing old <span class="caps">CFL</span> equipment (screwdrivers, spanners)</li>
<li>Qualified electrician friend to do wiring for you (in Australia, anyway)</li>
<li>Ladder</li>
<li>Multimeter</li>
<li>Velcro (if ceiling plates are not steel)</li>
</ul>
</div>
<div class="section" id="replacement-lights">
<h2>Replacement lights</h2>
<img alt="LED lights delivered" src="http://davidjb.com/images/led-lights/IMG_3532.JPG" style="width: 400px;" />
<ul class="simple">
<li>8 x 15w round <span class="caps">LED</span> ceiling panel (replaces 32w <span class="caps">CFL</span> tube):<ul>
<li>Cost $4.25 <span class="caps">US</span> each on
<a class="reference external" href="http://www.aliexpress.com/snapshot/6110525222.html">AliExpress</a></li>
</ul>
</li>
<li>6 x 12w round <span class="caps">LED</span> ceiling panel (replaces 22w <span class="caps">CFL</span> tube):<ul>
<li>Cost $3.75 <span class="caps">US</span> each on
<a class="reference external" href="http://www.aliexpress.com/snapshot/6110525220.html">AliExpress</a></li>
</ul>
</li>
</ul>
<p>Both of the above replacement <span class="caps">LED</span> panels come with <span class="caps">LED</span> driver transformers for
connecting mains power to the lights and these will fit essentially any mains
power source in the world. The <span class="caps">LED</span> boards operate at a voltage around 51V,
which is provided by a switch-mode regulator (or "<span class="caps">LED</span> driver"). Given the
range of voltages the driver supports (<span class="caps">AC</span> 85V to 277V), the lights will
function essentially anywhere in the world. Here, with a supply around 250V,
the lights will continue to work perfectly during a brown-out. Not that we
have many of them here in this part of Australia, but it has happened twice in
recent memory.</p>
<p>As for colour, I selected cold white (being 6000-6500K in temperature) as my
existing lights were "cool white" (being around 5700K). Buying <span class="caps">LED</span> lights
from overseas is incredibly hit-and-miss and in the past, I’ve found that
lights usually end up being a little warmer/yellower than expected. In this
case, I was somewhat surprised to find the colour temperature accurate - the
replacement lights are a little colder than my original tubes. The price is
right though, and I can always "colour in" my LEDs with a little felt-tip
marker if required! Here’s a comparison of the LEDs on the left and the
original <span class="caps">CFL</span> on the right:</p>
<img alt="LED light colour compared to CFL" src="http://davidjb.com/images/led-lights/IMG_3539.JPG" style="width: 400px;" />
<p>They also come with screw-on magnetic fittings for attaching both the <span class="caps">LED</span>
panel and driver to any iron or steel-based surfaces — particularly, the
round plates already on the ceiling.</p>
<p>The builders for my house helpfully decided to change from a steel-based plate
to an aluminium-based plate for around 40% of the lights. I didn’t discover
this until about half-way through the install work. Thankfully, I have
industrial-quality Velcro on hand to affix the <span class="caps">LED</span> boards to the ceiling.
Check all of your light fittings before starting and avoid the surprise, and
if using Velcro, make sure it can withstand a little warmth as the LEDs will
produce some heat (though not huge amounts).</p>
<p>The size of the replacement boards are notably smaller in diameter than the
original tubes. However, after much thinking and reading some web resources,
I decided that the given wattage (and lumen rating) of these <span class="caps">LED</span> boards would
roughly match the original CFLs. Turns out my approximations were close
enough; the LEDs are actually slightly brighter.</p>
</div>
<div class="section" id="how-to">
<h2>How to</h2>
<div class="section" id="preparation">
<h3>Preparation</h3>
<p>First comes the preparation. Gather your materials and order your lights.
Since they’re coming from China, I had to wait a good 3 weeks for mine to
arrive but they made it. Since I’m in Australia, and electrical work should
only be carried out by a qualified tradesperson, make sure you’re friends with
someone fitting that description.</p>
<p>Be sure to check what the mounting plate on your ceiling - the one that
currently holds your <span class="caps">CFL</span> tube and electronics - is made of. Most of mine are
some steel-based metal, meaning that the magnetic clips provided with the
boards will work. Some of my other lights are mounted on aluminium-based
(non-ferrous) plates, meaning the magnets won’t work. I got a rude awakening
to this fact about half way through the installation and had to organise a
solution. Industrial Velcro saved the day in this instance.</p>
</div>
<div class="section" id="step-by-step">
<h3>Step by step</h3>
<p>Your experience will likely be different, so adapt the instructions to suit
your own light fittings.</p>
<ol class="arabic">
<li><p class="first">Fit the magnetic mounts to the <span class="caps">LED</span> boards, or for non-ferrous ceiling
panels, fit Velcro.</p>
</li>
<li><p class="first">Ensure all power is disconnected from the light fitting prior to beginning.
Isolate the circuit the light is connected to, and use a multimeter to
double-check the voltage before starting.</p>
</li>
<li><p class="first">Remove the round diffuser dome from the light.</p>
<img alt="Before - CFL tube present" src="http://davidjb.com/images/led-lights/IMG_3545.JPG" style="width: 400px;" />
</li>
<li><p class="first">Remove the connector on the side of the tube, and remove the tube itself.
Store the tube safely to prevent it getting broken.</p>
</li>
<li><p class="first">Unscrew the relevant wires in the terminal block to remove the large
capacitor at the bottom, the ballast at the top, and the fluorescent tube
connector at the left.</p>
</li>
<li><p class="first">Unscrew and remove all electrical components from the panel. All that
should be left are the mains cable entering the terminal block.</p>
<img alt="Removed CFL electrical components" src="http://davidjb.com/images/led-lights/IMG_3543.JPG" style="width: 400px;" />
<img alt="Close up of removed CFL electrical components" src="http://davidjb.com/images/led-lights/IMG_3541.JPG" style="width: 400px;" />
</li>
<li><p class="first">Fit the <span class="caps">LED</span> board and <span class="caps">LED</span> driver onto the ceiling panel. Position things
according to how the existing cables and terminal block are located. Some
of my lights required some crafty positioning.</p>
<p>Take extra care with positioning if using Velcro. Once it’s stuck, it’s
stuck. Magnets are easily repositionable, if required.</p>
</li>
<li><p class="first">Wire the active and neutral wires into the correct part of the terminal
block, and ensure all screws are secure.</p>
</li>
<li><p class="first">The end result looks like this:</p>
<img alt="After - LED board replacement" src="http://davidjb.com/images/led-lights/IMG_3546.JPG" style="width: 400px;" />
</li>
<li><p class="first">Turn the power back on, and turn on the light switch.</p>
<img alt="After - light on and installed" src="http://davidjb.com/images/led-lights/IMG_3557.JPG" style="width: 400px;" />
</li>
<li><p class="first">Rinse and repeat for all the remaining lights in the house!</p>
</li>
</ol>
</div>
</div>
<div class="section" id="power-comparison">
<h2>Power comparison</h2>
<p>Prior to installation, the power consumption was measured for the <span class="caps">LED</span> lights,
and was measured for the CFLs as well after their removal. Here’s the grand break-down:</p>
<table border="1" class="docutils">
<colgroup>
<col width="7%" />
<col width="22%" />
<col width="28%" />
<col width="13%" />
<col width="22%" />
<col width="7%" />
</colgroup>
<thead valign="bottom">
<tr><th class="head">Type</th>
<th class="head">Power rating</th>
<th class="head">Brand</th>
<th class="head">Watts</th>
<th class="head">Power Factor</th>
<th class="head">Amps</th>
</tr>
</thead>
<tbody valign="top">
<tr><td><span class="caps">CFL</span></td>
<td>32w</td>
<td>Philips Lifemax</td>
<td>44.90</td>
<td>0.76-0.82</td>
<td>0.22</td>
</tr>
<tr><td><span class="caps">CFL</span></td>
<td>32w</td>
<td>Hitachi</td>
<td>40.79</td>
<td>0.78</td>
<td>0.21</td>
</tr>
<tr><td><span class="caps">CFL</span></td>
<td>32w</td>
<td>Lucci</td>
<td>36.00</td>
<td>0.33</td>
<td>0.44</td>
</tr>
<tr><td><span class="caps">CFL</span></td>
<td>22w</td>
<td>Philips Lifemax</td>
<td>17.46</td>
<td>0.30-0.34</td>
<td>0.22</td>
</tr>
<tr><td><span class="caps">CFL</span></td>
<td>22w</td>
<td>Hitachi</td>
<td>18.55</td>
<td>0.34</td>
<td>0.22</td>
</tr>
<tr><td><span class="caps">CFL</span></td>
<td>22w</td>
<td>Lucci</td>
<td>17.86</td>
<td>0.30</td>
<td>0.24</td>
</tr>
<tr><td><span class="caps">CFL</span></td>
<td>22w</td>
<td>Sylvannia</td>
<td>18.00</td>
<td>0.33</td>
<td>0.22</td>
</tr>
<tr><td><span class="caps">LED</span></td>
<td>15w</td>
<td>Generic</td>
<td>5.63</td>
<td>0.38</td>
<td>0.06</td>
</tr>
<tr><td><span class="caps">LED</span></td>
<td>12w</td>
<td>Generic</td>
<td>4.08</td>
<td>0.33</td>
<td>0.05</td>
</tr>
</tbody>
</table>
<p>The figures above aren’t entirely accurate as the power meter I’m using is
only monitoring amps to 2 decimal places, and watts to whole numbers. From
some of the calculations I’ve done, these figures aren’t even rounded, they’re
just truncated. I’ve worked backwards using the voltage, amperage, and power
factor to get a truer indication as to the wattage. The input power I’m
working with is slightly variable as well, being between 246 and 250V <span class="caps">AC</span>.</p>
<p>Note that the power rating is only what’s written on either the <span class="caps">CFL</span> or the <span class="caps">LED</span>
board and doesn’t factor everything in. For CFLs, the power consumption goes
up because of the ballast, and the wattage on the LEDs goes "down" because of
the low power factor (so a "15w" board ends up being only 5w of ‘real’ power).</p>
<p>In any case, it’s clear to see just how little power the <span class="caps">LED</span> boards use. In
terms of real power (watts), the 15w <span class="caps">LED</span> boards use around 87.5% less, and for
total power (current in amps) use 72.7% less. When compared to the worst
performing 32w <span class="caps">CFL</span>, the usage is 83% lower in watts, and 86.4% lower in terms
of total power in amps. Yes, the power factor is lower than most CFLs I had,
but the current draw is significantly smaller — compare 0.06A to 0.22A or 0.44A.</p>
<p>There are similar power savings to be had from the 12w <span class="caps">LED</span> boards over their
22w counterparts, consuming around 77% less real power in watts, and 43.2%
less total curren drawn. Again, compare 0.05A for the <span class="caps">LED</span> board to 0.22A for
the CFLs.</p>
<p>The difference between 22w and 32w CFLs and their respective <span class="caps">LED</span> counterparts
isn’t as significant as I originally expected, but I’m fairly sure this comes
down to the differences in the electronic ballasts being very small.</p>
</div>
<div class="section" id="benefits">
<h2>Benefits</h2>
<p>A notable part of the driving force behind me making the switch to LEDs was
the fact that these replacement lights were just so incredibly cheap. By
contrast, a single 32 watt <span class="caps">CFL</span> tube will cost $10 <span class="caps">AUD</span> - more than double the
cost of the <span class="caps">LED</span> panel. For me, a few have needed replacement over the last few
years, and quite a few of the old tubes we have were getting ‘sluggish’ to
turn on and flickering more recently. When you couple the insignificant cost
with the environmental benefits of using far less power and of not using
mercury, this feels like a no-brainer to me.</p>
<p>So, the overall benefits are:</p>
<ul class="simple">
<li><strong>No more replacements needed</strong>. Saving on manufacturing energy, materials and
chemicals when sourcing replacement tubes, not to mention savings to my
time, energy, and safety.</li>
<li><strong>Cost</strong>. For less than half the cost of one replacement tube, the LEDs
should last a long time and a lot longer than any one <span class="caps">CFL</span> or starter.</li>
<li><strong>Resiliancy</strong>. This remains to be seen if they’ll last for the claimed
50000 hours, the boards are designed with each set of 2 LEDs in parallel so
if one <span class="caps">LED</span> in a pair fails, the lights will stay on. If one <span class="caps">LED</span> fails, then
it can be replaced for almost nothing save a bit of soldering. My personal
thinking is that the rest of the electronics will fail before the LEDs themselves.</li>
<li><strong>Power savings</strong>. The <span class="caps">LED</span> replacements for the 32 watt CFLs use around 75%
less power, and the <span class="caps">LED</span> boards for the 22 watt CFLs use around 60% less
power. Mileage definitely varies here between brands of <span class="caps">CFL</span> light and
electronics, but on average it’s a great deal less.</li>
<li><strong>Instant on</strong>. No waiting or flickering when the lights turn on.</li>
</ul>
</div>
<div class="section" id="and-now-for-something-completely-different">
<h2>And now for something completely different…</h2>
<p>This little project has been a great way of getting familiar with electricity,
power factors, and efficiency in lighting. These <span class="caps">LED</span> boards look great and
whilst they’re a little colder white than what I had at home originally,
they’re brighter and the power savings are significant. Couple this with the
fact that each board cost less than half of a replacement <span class="caps">CFL</span> tube, and it’s
win-win all around — well worth it in becoming a ‘green’ house.</p>
<p>If there are any issues with the <span class="caps">LED</span> boards, I’ll report back.</p>
<p>This is the first in my series of ‘green’ projects. Stay tuned for more of
the same!</p>
</div>
<p>There are <a href="http://davidjb.com/blog/2014/07/project-green-house-1-led-replacement-lighting-for-round-cfls/#disqus_thread">comments</a>.</p> </article>
</aside><!-- /#featured -->
<section id="content" class="body">
<h1>Other articles</h1>
<hr />
<ol id="posts-list" class="hfeed">
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2014/05/nginx-with-shibboleth-fastcgi-authorizer-support-updated-to-16/" rel="bookmark"
title="Permalink to Nginx with Shibboleth (FastCGI authorizer) support updated to 1.6">Nginx with Shibboleth (FastCGI authorizer) support updated to 1.6</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-05-05T00:00:00">
Published: Mon 05 May 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/web.html">Web</a>. </p>
<p>tags: <a href="http://davidjb.com/tag/nginx.html">Nginx</a> <a href="http://davidjb.com/tag/shibboleth.html">Shibboleth</a> <a href="http://davidjb.com/tag/fastcgi.html">FastCGI</a> </p>
</footer><!-- /.post-info --> <div class="note">
<p class="first admonition-title">Note</p>
<p class="last">This was discussed in a <a class="reference external" href="http://davidjb.com/blog/2013/04/integrating-nginx-and-a-shibboleth-sp-with-fastcgi/">previous post</a>. Various changes
have happened since then, improving the customisation process and updating
for newer versions of Nginx and associated add-on modules.</p>
</div>
<p>I’ve updated the custom version of Nginx that supports operating with a
Shibboleth <span class="caps">SP</span> to version 1.6.0, now ...</p>
<a class="readmore" href="http://davidjb.com/blog/2014/05/nginx-with-shibboleth-fastcgi-authorizer-support-updated-to-16/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2014/05/nginx-with-shibboleth-fastcgi-authorizer-support-updated-to-16/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2014/03/scprsync-transfers-stall-at-exactly-2112-kb/" rel="bookmark"
title="Permalink to SCP/Rsync transfers stall at exactly 2112 kB"><span class="caps">SCP</span>/Rsync transfers stall at exactly 2112 kB</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-03-31T00:00:00">
Published: Mon 31 March 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/linux.html">Linux</a>. </p>
</footer><!-- /.post-info --> <p>In case your <span class="caps">SCP</span>, Rsync, or other sort of file transfer works for a short
period and then suddenly stalls (permanently), then you may want to examine the
<span class="caps">MTU</span> configuration on your network interface. After trawling the web for hours,
attempting to find a solution to why an <span class="caps">SCP</span> transfer ...</p>
<a class="readmore" href="http://davidjb.com/blog/2014/03/scprsync-transfers-stall-at-exactly-2112-kb/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2014/03/scprsync-transfers-stall-at-exactly-2112-kb/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2014/03/gmail-avatarphoto-always-reverts-after-being-changed/" rel="bookmark"
title="Permalink to Gmail avatar/photo always reverts after being changed">Gmail avatar/photo always reverts after being changed</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-03-17T00:00:00">
Published: Mon 17 March 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/google.html">Google</a>. </p>
</footer><!-- /.post-info --> <p>Got an unsightly image associated with your Gmail messages, your
Google Groups posts, Google Drive activity or somewhere else obscure
within Google’s domain? Tried changing that image several times
and it won’t budge - or it does and reverts itself right back?
Your main Google+ avatar just doesn’t ...</p>
<a class="readmore" href="http://davidjb.com/blog/2014/03/gmail-avatarphoto-always-reverts-after-being-changed/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2014/03/gmail-avatarphoto-always-reverts-after-being-changed/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2013/08/uwsgi-and-database-lockups-with-sqlalchemy/" rel="bookmark"
title="Permalink to uWSGI and Database Lockups with SQLAlchemy">uWSGI and Database Lockups with SQLAlchemy</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-08-26T00:00:00">
Published: Mon 26 August 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/web.html">Web</a>. </p>
</footer><!-- /.post-info --> <p>If you’re running a Python-based web application and using SQLAlchemy as your
database integration layer (as an <span class="caps">ORM</span> or otherwise), you may also be using
uWSGI to act as the application container.</p>
<p>If you try and fire up multiple processes to handle greater load coming in
with the uWSGI ...</p>
<a class="readmore" href="http://davidjb.com/blog/2013/08/uwsgi-and-database-lockups-with-sqlalchemy/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2013/08/uwsgi-and-database-lockups-with-sqlalchemy/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2013/07/unlocking-your-telstra-elite-zte-mf60-mobile-wi-fi-device-for-free/" rel="bookmark"
title="Permalink to Unlocking your Telstra Elite (ZTE MF60) Mobile Wi-fi Device for Free">Unlocking your Telstra Elite (<span class="caps">ZTE</span> <span class="caps">MF60</span>) Mobile Wi-fi Device for Free</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-07-30T00:00:00">
Published: Tue 30 July 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/freebies.html">Freebies</a>. </p>
</footer><!-- /.post-info --> <p>Ha, that’s a dodgy-sounding title if I ever heard one. If you’re
reading this, then I’ll assure you that these instructions are real,
open, and free, and that I’ve used them to unlock my device. Read on…</p>
<p><strong>Update</strong>: I should mention that hexecute’s site at ...</p>
<a class="readmore" href="http://davidjb.com/blog/2013/07/unlocking-your-telstra-elite-zte-mf60-mobile-wi-fi-device-for-free/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2013/07/unlocking-your-telstra-elite-zte-mf60-mobile-wi-fi-device-for-free/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2013/07/all-fanstatic-resources-being-served-with-texthtml-mimetype-by-webobwsgi/" rel="bookmark"
title="Permalink to All Fanstatic resources being served with ‘text/html’ mimetype by WebOb/WSGI">All Fanstatic resources being served with ‘text/html’ mimetype by WebOb/<span class="caps">WSGI</span></a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-07-29T00:00:00">
Published: Mon 29 July 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/web.html">Web</a>. </p>
</footer><!-- /.post-info --> <p>If you’re finding that you’re using <a class="reference external" href="http://fanstatic.org">Fanstatic</a> to
serve static resources within your Python-based server process, you may be left
scracthing your head if you suddenly find that resources aren’t being served
correctly. For me, this was manifesting as an incorrect <tt class="docutils literal"><span class="pre">Content-Type</span></tt>
header, always being set to ...</p>
<a class="readmore" href="http://davidjb.com/blog/2013/07/all-fanstatic-resources-being-served-with-texthtml-mimetype-by-webobwsgi/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2013/07/all-fanstatic-resources-being-served-with-texthtml-mimetype-by-webobwsgi/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2013/05/attributes-not-released-to-new-shibboleth-service-provider-sp/" rel="bookmark"
title="Permalink to Attributes not released to new Shibboleth Service Provider (SP)">Attributes not released to new Shibboleth Service Provider (<span class="caps">SP</span>)</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-05-28T00:00:00">
Published: Tue 28 May 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/web.html">Web</a>. </p>
</footer><!-- /.post-info --> <p>Just created a new Shibboleth Service Provider (<span class="caps">SP</span>) instance and found an
Identity Providers (IdPs) is not releasing attributes to you? Don’t
worry, you’re not alone. In fact, the issue is far more common than you think,
despite a lack of documentation on the web.</p>
<div class="section" id="confirming-the-problem">
<h2>Confirming the problem ...</h2></div>
<a class="readmore" href="http://davidjb.com/blog/2013/05/attributes-not-released-to-new-shibboleth-service-provider-sp/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2013/05/attributes-not-released-to-new-shibboleth-service-provider-sp/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2013/05/uwsgi-and-libxml2-conflicts-aka-installing-uwsgi-with-a-custom-libxml2/" rel="bookmark"
title="Permalink to uWSGI and libxml2 conflicts (aka Installing uWSGI with a custom libxml2)">uWSGI and libxml2 conflicts (aka Installing uWSGI with a custom libxml2)</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-05-08T00:00:00">
Published: Wed 08 May 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/web.html">Web</a>. </p>
<p>tags: <a href="http://davidjb.com/tag/uwsgi.html">uWSGI</a> <a href="http://davidjb.com/tag/libxml2.html">libxml2</a> <a href="http://davidjb.com/tag/xml-config.html">xml-config</a> </p>
</footer><!-- /.post-info --> <p>If you’re using uWSGI with <span class="caps">XML</span> support (this is its default), then it will
be requiring you to have <tt class="docutils literal">libxml2</tt> installed — or something similar that
provides <tt class="docutils literal"><span class="pre">xml-config</span></tt>. What you’ll find is some erratic behaviour (or
complete failure) when attempting to serve an application that is also
relying on ...</p>
<a class="readmore" href="http://davidjb.com/blog/2013/05/uwsgi-and-libxml2-conflicts-aka-installing-uwsgi-with-a-custom-libxml2/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2013/05/uwsgi-and-libxml2-conflicts-aka-installing-uwsgi-with-a-custom-libxml2/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="http://davidjb.com/blog/2013/04/integrating-nginx-and-a-shibboleth-sp-with-fastcgi/" rel="bookmark"
title="Permalink to Integrating Nginx and a Shibboleth SP with FastCGI">Integrating Nginx and a Shibboleth <span class="caps">SP</span> with FastCGI</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-04-22T00:00:00">
Published: Mon 22 April 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="http://davidjb.com/author/davidjb.html">davidjb</a>
</address>
<p>In <a href="http://davidjb.com/category/web.html">Web</a>. </p>
<p>tags: <a href="http://davidjb.com/tag/nginx.html">Nginx</a> <a href="http://davidjb.com/tag/shibboleth.html">Shibboleth</a> <a href="http://davidjb.com/tag/fastcgi.html">FastCGI</a> </p>
</footer><!-- /.post-info --> <div class="section" id="update">
<h2>Update</h2>
<p>With changes in Nginx after version 1.5.4, the auth request module is now
built in. This means the following instruction have changed, yet again.
For the latest information and build process, always see
<a class="reference external" href="https://github.com/jcu-eresearch/nginx-custom-build">https://github.com/jcu-eresearch/nginx-custom-build</a>.</p>
</div>
<div class="section" id="original-post">
<h2>Original post</h2>
<p><strong>tl;dr</strong>: You can have Nginx with ...</p></div>
<a class="readmore" href="http://davidjb.com/blog/2013/04/integrating-nginx-and-a-shibboleth-sp-with-fastcgi/">read more</a>
<p>There are <a href="http://davidjb.com/blog/2013/04/integrating-nginx-and-a-shibboleth-sp-with-fastcgi/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
</ol><!-- /#posts-list -->
<p class="paginator">
Page 1 / 13
<a href="http://davidjb.com/index2.html">»</a>
</p>
</section><!-- /#content -->
<section id="extras" class="body">
<div class="blogroll">
<h2>blogroll</h2>
<ul>
<li><a href="http://planet.plone.org">Planet Plone</a></li>
<li><a href="http://jcu.me">jcu.me Research Porfolio</a></li>
<li><a href="http://xckd.com">XKCD</a></li>
</ul>
</div><!-- /.blogroll -->
<div class="social">
<h2>social</h2>
<ul>
<li><a href="http://davidjb.com/feeds/all.atom.xml" type="application/atom+xml" rel="alternate">atom feed</a></li>
<li><a href="http://git.io/djb">GitHub</a></li>
<li><a href="http://twitter.com/davidjb_">Twitter</a></li>
<li><a href="http://linkedin.com/in/davidbeitey">LinkedIn</a></li>
<li><a href="http://facebook.com/david.beitey">Facebook</a></li>
<li><a href="https://plus.google.com/u/0/106527454335411502430">Google+</a></li>
</ul>
</div><!-- /.social -->
</section><!-- /#extras -->
<footer id="contentinfo" class="body">
<address id="about" class="vcard body">
Proudly powered by <a href="http://getpelican.com/">Pelican</a>, which takes great advantage of <a href="http://python.org">Python</a>.
</address><!-- /#about -->
<p>The theme is by <a href="http://coding.smashingmagazine.com/2009/08/04/designing-a-html-5-layout-from-scratch/">Smashing Magazine</a>, thanks!</p>
</footer><!-- /#contentinfo -->
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-24253455-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>
<script type="text/javascript">
var disqus_shortname = 'davidjb';
(function () {
var s = document.createElement('script'); s.async = true;
s.type = 'text/javascript';
s.src = '//' + disqus_shortname + '.disqus.com/count.js';
(document.getElementsByTagName('HEAD')[0] || document.getElementsByTagName('BODY')[0]).appendChild(s);
}());
</script>
</body>
</html>