BlogSphere
Keep up to date with your favourite Rails bloggers in context.
by
Jonathan Clarke | 2 days ago |
Read more
Last April I splashed out on a bargain through E-Bay on a Dell XPS M1330. It truly is an awesome machine however there was one huge flaw, the Nvidia graphics card is completely fubar'd. Today Dell decided to offer the following:
Dell will offer a 12-month limited warranty enhancement specific to this issue. For all customers worldwide, we plan to add 12 months of coverage for this issue to the existing limited warranty up to 60 months from the date of purchase for the following systems
More information will be available from the Direct 2 Dell blog when they get it, however more information can be found here and here for those who are affected.
I have quite a few grievances about this. When Dell realized there was an issue with so many defective GPU's they quietly went along and released a bios upgrade (A12), as a result the fans are now on all of the time. It constantly has a GPU temp of above 60 degrees, any bit of load on it and it shoots through the roof up to 80-90 degrees.
Thankfully I have well over 3 years left on this warranty but with the fan being on all the time with the noise and decreased
battery life, not to mention the increased wear and tear on the fan
and other components would the entire system not warrent need to be replaced?
If the GPU or the motherboard needs a replacement, then what is it replaced with? Is there a defect free GPU available or do we just get landed back with a defective one again? If we get a defective one then how long will
that be covered under warrenty for? Personally I don't want to switch to the lower powered Intel graphics chip, but what is the alternative?

Dell, if you guys are reading any of this, give me some hope for this awesome machine, give us more information, issue a mass recall but for christ sake take more action; it's what your customers deserve.
by
Carlos Eduardo G. Franco | 2 days ago |
Read more
Pessoal,
Estamos desenvolvendo uma nova plataforma de cursos on-line, que visa também suprir as demandas e procuras por outros assuntos não ligados a Flex e Ruby on Rails. Então criamos um breve questionário de 3 questões para receber o feedback de vocês, para que possamos em seguida lançar os cursos em ordem de prioridade.
Gostaria muito de [...]
by
Scott Motte | 2 days ago |
Read more
Usually, when you create a model, you create a database, and then the model works with ActiveRecord. And it’s ActiveRecord (as far as I currently know) that lets you use validation techniques.
So how do we add validation techniques to something like a contact form on our Rails site that does not have a database?
Install [...]
by
Jony dos Santos Kostetzer | 2 days ago |
Read more
Tenho visto diversas pessoas falando do Shoulda, e algumas que já sentiram o gosto do RSpec e depois também gostaram do Shoulda. Até aí sem problemas. Agora, ao passo que surgem comparações entre RSpec e Shoulda, um sinal amarelo deveria aparecer por aí e deixar algumas coisas bem claras. E este é o objetivo do [...]
by
Mathias Meyer | 2 days ago |
Read more
In case you're coming to RailsConf Europe, you might be interested in the tutorial I tutorial on deploying and monitoring Rails applications I'm giving together with Jonathan Weiss.
See you there!
by
Fabio Akita | 2 days ago |
Read more

Desde meu relato sobre a RailsConf eu já havia dito que Josh Peek tinha um branch do Rails no Github, num trabalho para o Google Summer of Code, tendo Michael Koziarski como mentor.
Finalmente, David Hansson anunciou que Josh Peek passa a fazer parte do Core Team, e uma das coisas que isso implica é finalmente fazer o merge do branch de thread-safe do Josh para dentro do trunk oficial!
Agora, Charles Nutter – sempre à frente dessas polêmicas iniciais – resolveu escrever uma lista de perguntas e respostas (Q/A) sobre que efeitos thread-safety causa no Rails, e especialmente sobre o mundo JRuby. Naturalmente existem muitas opiniões do próprio Charles aqui, mas a maior parte deve ser factualmente correta.
Segue a tradução do artigo dele:
by
Jonathan Stegall | 2 days ago |
Read more
My links for 2008-08-17
by
Marcus Ahnve | 2 days ago |
Read more
Cleaning up cable mess in basement #
Powered by Twitter Tools.
by
Geoffrey Parsons | 2 days ago |
Read more
I’ve been slowly fixing up a house and things have been going pretty well if i do say so myself. I’d been dreading renovating the kitchen however and as such it sat in 50’s form for quite a while before i touched anything.
Well i’d finally had enough of it and decided (with a little encouragement) [...]
by
Ben Scofield | 2 days ago |
Read more
So as it turns out, Milorad Cavic has a blog. (If the name’s not ringing a bell, you probably haven’t been watching one of the most remarkable sporting accomplishments in history—he was the swimmer out-touched by 0.01 seconds in the 100m Olympic butterfly.) For me, this brings two surprises: first, that a world-class athlete is [...]
by
Scott Hacker | 2 days ago |
Read more
After Twittering for a few months, I started to feel uncomfortable about not owning my data, and wanted an automated way to store a copy of each Tweet for posterity. Another installation of WordPress would be perfect as a Twitter backup repository (alternatively, you could copy all of your tweets to a dedicated category [...]
by
Fernando Blat | 2 days ago |
Read more

iwannagothere.net is the last project from mamuso, Maria and me. It's a site about traveling with two main purposes:
- share all the special places you have discovered in your travels: a singular monument, a delicious and cheap restaurant, a small museum with special charm, a park where you can see the most wonderful sunset ever...
- help you to prepare your travels with all the information uploaded in the site
It's a kind of independent and high quality information travel guide.
As in unvlog.com we developed it in Ruby on Rails, (now running version 2.1), in our free time, along 3 months. Now we are refining a lot of details, and adapting some parts that we have seen people don't us as we thought.
We are going to explain all the technical issues we had in a serie of small posts in this blog or in the iwannagothere's blog. As well, we are going to present it at Spanish Rails Conference 08 in November.
We hope you enjoy the site and find it useful.
by
Phillip Oertel | 2 days ago |
Read more
… and be prepared to suck in the process.
Two excellent – and classic – articles on how to become an expert programmer:
on your way, be prepared to create lots of prime examples of
coding horror. below are some of mine.
to put it differently: the best you can do is to suck less as a programmer, year by year. i recently talked to a guy who had lots of architecture knowledge, knew rails’ activerecord inside out, said he counted Scheme as his favourite language, and in general seemed a top coder. it turned out later on he barely could handle simple regular expressions.
(warning, coding horror)
product catalog (first tries with ruby on rails, 2005)
class ProductsController < ApplicationController
#before_filter :authenticate
layout 'shopAdmin'
helper :sort
include SortHelper
def initialize
super
@categories = Category.find_all
@materials = Material.find_all
end
def index
list
render_action 'list'
end
def list
sort_init 'category_id'
sort_update
@session['cart'] = 'A SHOPPING CART'
@products = Product.find(:all, :order => sort_clause)
@category = @params['category']
end
...
end
webshop (2000)
function layout_head($proj_name,$pid) {
echo '<table width=600 border=0 cellspacing=2>';
echo "<tr><td>projektomat v 0.013</td><td align=right rowspan=2><a href=http://rmltk.weinbau-jauk.at/index.php?pid=$pid>[bersicht]</a><br/><a href=http://rmltk.weinbau-jauk.at/protected/upload.php?pid=$pid&proj_name=$proj_name>[neue datei hochladen]</a></td></tr>";
echo "<tr><td>aktuelles projekt: <b>$proj_name</b></td></tr></table>";
}
online calendar (1999)
<?php
if (!defined(INCLUDES)) include("./includes.inc.php");
if (!defined(HEADER)) include("./header.inc.php");
$class = "termin".$func;
$termin_head = "<title>Termin</title>\n<body class='$class' onload=self.focus();document.termin.stunde.focus();>\n<link rel='stylesheet' href='$templatepath/style.css'>";
$datum = mysql2dmy($datum[3]); ## killdatumarrayhere....
if (@$func=="edit") {
bearbeiten($id);
exit;
}
if (@$eintrag_neu) {
echo submit("neu");
} elseif (@$eintrag_update) {
echo submit("update");
} else {
neu(0);
}
online calendar, snippet 2 (1999)
function submit($typ) { ### NEUEN und UPGEDATEDEN termin add_info und eintragen in db
global $jahr,$monat,$tag,$stunde,$minute,$dauer,$text,$projekt,$protrack,$projekt_id,$teambox,$id;
$datum = "20$jahr-$monat-$tag";
$zeit = "$stunde:$minute:00";
$text = nl2br($text);
$nr=1;
$i=1;
@end($teambox);
$lastelementnr = @key($teambox); # hier werden die werte der checkboxes (per get bergebenes array teambox[$id]) , werte yes oder unset
while ($i <= $lastelementnr) { # nach $team_id[$nr] = teambox gewandelt und dann weiter in brauchbare db-query-teile umgewandelt
if (@$teambox[$i] AND $nr <= 5) {
$$teambox[$i] =$i; # yes wird durch den entsprechenden zhlerwert ersetzt
$team_id[$nr] = $$teambox[$i];
# echo "<pre>team_id[$nr] = $team_id[$nr]</pre>"; ## mal echo einschalten und die ausgabe ansehen
@$team_cols .= ",team_id$nr";
@$team_vals .= ",'$team_id[$nr]'";
@$team_update .= ",team_id$nr='$team_id[$nr]'";
$nr++;
}
$i++;
}
online questionnaire application (2001)
class radQuizBase
{
var $dbName, $form;
var $debugFlag = false;
var $quiz = array();
var $quizForm;
// variablen fr fragen
var $questionTypes = array (
'free' => 'Freie Antwort',
_continues ... file has ~1.200 lines ..._
class radQuizAdmin extends radQuizBase
{
var $task;
# variablen fr fragebogen administration
var $qSetName, $insertBeforeQuestionId, $qSetType;
var $transDifficulty = array(
'n.a.',
'leicht',
'mittel',
'schwierig'
);
_continues ... file has ~2.000 lines_ [...]
a self-written cms (2000)
################################ / logic start
if($func=='newEntry')
{
$newId = newEntry($pid);
eingabeseite($newId);
}
else
{
// classic logic based on $pid and $aenderung
if (!$pid)
{
echo auswahlseite($category);
}
else
{
if($showMulti == 'true')
{
echo showMulti($pid);
}
elseif (!file_exists(WA_ROOT.'/xml/'.$pid.'.xml'))
{
$parms['title'] = $navititle;
$parms['id'] = $pid;
neue_seite($parms);
eingabeseite($pid);
}
else // bearbeite bestehende seite
{
if(!$aenderung)
{
eingabeseite ($pid);
}
else
{
aenderung ($pid);
}
}
}
}
by
Fernando Blat | 2 days ago |
Read more
I think that the moment has arrived. This blog switches to English (to my bad English, that surely all Spanish will understand), because this is the only way to participate in the conversation of the international community.
by
Kurt Schrader | 2 days ago |
Read more
The easiest way to run Merb from edge:
$ sudo gem install sake
$ sake -i http://github.com/wycats/merb-more/tree/master%2Ftools%2Fmerb-dev.rake?raw=true
$ sake merb:clone
$ sake merb:install:all
This will install the edge versions of all of the merb gems.
To keep things up to date, navigate to the directory that you ran the commands in and do:
$ sake merb:update
$ sake merb:install:all
by
Ruby Hammer | 2 days ago |
Read more
Теперь доступна новостная лента в формате RSS 2.0
Подписаться можно по тут или по ссылке внизу главной страницы.
by
Adam Keys | 2 days ago |
Read more
Wherein Last.fm has neat data
by
Rafe Colburn | 2 days ago |
Read more
Unlike me, you probably didn’t sit through John McCain’s hour with Rick Warren at the Saddleback Civil Forum last night. Here’s their conversation, distilled.
Pastor Rick Warren: Who are three wisest people you’d rely on for advice if you are elected?
John McCain: David Petraeus, who is the greatest American in history besides me, John Lewis, and [...]
by
Ian Fieldhouse | 2 days ago |
Read more

Specs are your unit tests, their fast and lean and always running, helping you refactor and develop your code. They describe the system at the object level (and dependent on how you mock/stub they do this in isolation). Stories are like integration tests, they document how your system works. They help you know that your system meets the customers requirements.
Your spec test is going to care about testing each action in your controller.
Your story is going to care about usage of the system cutting through models/controllers/views.
Hence specs tend to have a high coverage while stories cover only that which is important to the customer!
Saved By: Ian Fieldhouse | View Details | Give Thanks
Tags: development, testing, ruby, rspec, story-framework, reference
by
Adriaan de Jonge | 2 days ago |
Read more

Last week I remembered that a few years ago, just before I discovered XForms, I was actually looking for an XSLT processor that works bidirectional. Meaning that after the transformation, if you change something in the output document, the equivalent values in the input document also change. Like this:

Back then, there was an alpha quality example project called Wobzilla that demonstrated a technique that works this way. XForms also works this way, but that is a bit less flexible than two way XSLT. The latter can be used in a pipeline and might even function under an XForm to simplify the input/output document used in the XForm.
How difficult is it to create technology like this that works in a Cocoon pipeline or an Orbeon pipeline?
by
Mando Escamilla | 2 days ago |
Read more
Butterflies and gorillas on the loose!
by
Cássio Marques | 2 days ago |
Read more
Comecei a estudar um pouco de Erlang recentemente. A linguagem realmente é bem diferente daquilo que estou acostumado, principalmente por ser um linguagem totalmente funcional e possuir certos conceitos que em um primeiro momento realmente podem confundir a cabeça de quem está mais acostumado com linguagens imperativas.
Na verdade, eu já acabei usando diversos conceitos de [...]
by
Ryan L. Cross | 2 days ago |
Read more
Perian: The swiss-army knife of QuickTime® components
by
Heungseok Do | 2 days ago |
Read more
이 글은 꽃띠앙님의 2008년 8월 17일의 미투데이 내용입니다.
<!-- end of daily_digest -->
by
Fred Grott | 2 days ago |
Read more
First let me state that I do respect
Mahalo.com is a collection of wiki like articles by the masses also whereas collaboration is controlled by a select few by Mahalo.cm. Thus is by no means demeans or reduces contributions from both wikpedia or Mahalo.com its just that is the way they were set-up.
In both cases you have two clouds that collaborate between the two clouds. The controlling entity, Wikipedia Foundation or Mahalo.com, and the users. Its a mix of both direct and loosely coupled collaboration but the direction is somewhat non bi-directional in some cases. Now on to the unit part of the point.
While wikipedia has two distinct units a small article and a book size piece of knowledge Mahalo.com only has small bite size articles. Thus, it can be said that Mahalo.com does not compete with Wikipedia. Google's Knol has or goes from the small bite size article to a collection of articles just as WIkipedia so Knol can be said not to compete with Mahalo.com but more with wikipedia.
It is the indirect competition that matters here ie the composition of the interaction between the clouds of control and users. In Google's Knol case the controller cloud is the user that happens be author. The rating system serves as a 2nd editor with users being able to rate and review and offer suggestions for changes to the author. This indirect competition will force Mahalo.com and Wikipedia Foundation to review their own model where they may come up with new ways to configure the clouds to increase collaboration which by the way increases viewership for all three, Wikipedia, Mahalo.com , and Google Knol.
I must admit a few week sago I was incline to support Jason's conclusion. But, than I decided to try Knol and find out for myself what the interaction was and how it was different form both Wikipedia and Mahalo.com. Because I use all three for very different reasons and purposes, I certainly hope that I am right and not Jason.
by
Peat Bakke | 2 days ago |
Read more
I spent this morning adding i-name support to the open_id_authentication plugin. Until it gets merged with the master repository, you’re welcome to take a look and tinker with my branch on Github: http://github.com/peat/open_id_authentication
What is an i-name? It’s an alternative way to identify yourself through OpenID. Instead of using my DNS based [...]
by
Mando Escamilla | 2 days ago |
Read more
Butterflies and gorillas on the loose! -
http://snaptweet.com/1d05d
by
Mike Perham | 2 days ago |
Read more
This is an excellent summary of REST, why SOAP services should be considered broken and why your services should be RESTful. One overlooked benefit of REST: interacting with the HTTP ecosystem correctly. You might not be using a caching proxy on the server-side but if your clients want to use a caching proxy, making your [...]
by
Coby Randquist | 2 days ago |
Read more
Rails 2.1 - fully restful
Gems
haml
annotate_models
rails coolapp
haml --rails ./coolapp
cd coolapp
script/plugin install http://svn.techno-weenie.net/projects/plugins/attachment_fu/
script/plugin install http://svn.hamptoncatlin.com/make_resourceful/trunk
by
Nicholaus Luster Ames | 2 days ago |
Read more
Well its day 3 of ridiculous road trip oh eight (better name to come). It took us 14 hours to do a 9 hour drive. The VW bus, Mamasita, isn’t ‘suppose’ to go over 55 or 60 mph, but we didn’t know that the speedometer was 10 mph off. So we were going 45 the whole way from Seattle to McCall Idaho. But 14 hours in a car with 3 beautiful women never hurt a pale kid like me. Threes company, you can call me Jack Tripper. We stopped to swim in the Columbia River and had amazing sandwiches in Pendleton, OR. By the time we got in it was almost 4 in the morning.
But we got there and day 2 was awesome. The day started out great with a run out the front door of the cabin and a big dive off the dock. The Bagley Family cabin is amazing, with a huge deck, grassy lawn all the way to the dock and a great fire pit. We had a breakfest cooked on their wood fired outdoor griddle of blueberry pancakes and bacon. Later there was boating, innertubing (neck hurts), cliff jumping, great food, smores, killed a man with a trident, booze, mushrooms and just an amazing day that just seamed to end. After a day like yesterday, people you just met, seem like great friends by the time you finally go to bed (...with them (JK)). They even have wifi here, so i figured i better post while I still can.
Today will prolly be more of the same, maybe mixing it up with a bike ride or a hike. Tomorrow the Apple Gang, Dagen, Roxy, Marely, Olivia, Nikki, and yours truly, will be leaving for Jackson Hole, where we will go camping with a Emma, childhood/family friend. Everything is going great and will continue to go so, because you know I do it. More to come.
number of cars passed: 5
number of peace or hang loose signs: 3
number of middle fingers: 1
road side observation: cows with numbers on them = how soon til I eat them (Echo, Oregon)
<embed pluginspage="http://www.macromedia.com/go/getflashplayer" src="http://picasaweb.google.com/s/c/bin/slideshow.swf" type="application/x-shockwave-flash" flashvars="host=picasaweb.google.com&RGB=0x000000&feed=http%3A%2F%2Fpicasaweb.google.com%2Fdata%2Ffeed%2Fapi%2Fuser%2FNicholaus.L.Ames%2Falbumid%2F5235562129228366673%3Fkind%3Dphoto%26alt%3Drss" height="267" width="400"></embed>
by
Charles Nutter | 2 days ago |
Read more
There's been a little bit of buzz about David Heinemeier Hansson's announcement that
Josh Peek has joined Rails core and is about to wrap up his GSoC project making Rails finally be thread-safe. To be honest, there probably hasn't been enough buzz, and there's been several misunderstandings about what it means for Rails users in general.
So I figured I'd do a really short Q/A about what effect Rails thread-safety would have on the Rails world, and especially the JRuby world. Naturally there's some of my opinions reflected here, but most of this should be factually correct. I trust you will offer corrections in the comments.
Q: What does it mean to make Rails thread-safe?A: I'm sure Josh or Michael Koziarski, his GSoC mentor, can explain in more detail what the work involved, but basically it means removing the single coarse-grained lock around every incoming request and replacing it with finer-grained locks around only those resources that need to be shared across threads. So for example, data structures within the logging subsystem have either been modified so they are not shared across threads, or locked appropriately to make sure two threads don't interfere with each other or render those data structures invalid or corrupt. Instead of a single database connection for a given Rails instance, there will be a pool of connections, allowing N database connections to be used by the M requests executing concurrently. It also means allowing requests to potentially execute without consuming a connection, so the number of live, active connections usually will be lower than the number of requests you can handle concurrently.
Q: Why is this important? Don't we have true concurrency already with Rails' shared-nothing architecture and multiple processes?A: Yes, processes and shared-nothing do give us full concurrency, at the cost of having multiple processes to manage. For many applications, this is "good enough" concurrency. But there's a down side to requiring as many processes as concurrent requests: inefficient use of shared resources. In a typical Mongrel setup, handling 10 concurrent requests means you have to have 10 copies of Rails loaded, 10 copies of your application loaded, 10 in-memory data caches, 10 database connections...everything has to be scaled in lock step for every additional request you want to handle concurrently. Multiply the N copies of everything times M different applications, and you're eating many, many times more memory than you should.
Of course there are partial solutions to this that don't require thread safety. Since much of the loaded code and some of the data may be the same across all instances, deployment solutions like Passenger from Phusion can use forking and memory-model improvements in Phusion's Ruby Enterprise Edition to allow all instances to share the portion of memory that's the same. So you reduce the memory load by about the amount of code and data in memory that each instance can safely hold in common, which would usually include Rails itself, your static application code, and to some extent the other libraries loaded by Rails and your app. But you still pay the duplication cost for database connections, application code, and in-memory data that are loaded or created after startup. And you still have "no better" concurrency than the coarse-grained locking since Ruby Enterprise Edition is is just as green-threaded as normal Ruby.
Q: So for green-threaded implementations like Ruby, Ruby EE, and Rubinius, native threading offers no benefit?A: That's not quite true. Thread-safe Rails will mean that an individual instance, even with green threads, can handle multiple requests at the same time. By "at the same time" I don't mean concurrently...green threads will never allow two requests to actually run concurrently or to utilize multiple cores. What I mean is that if a given request ends up blocking on IO, which happens in almost all requests (due to REST hits, DB hits, filesystem hits and so on), Ruby will now have the option of scheduling another request to execute. Put another way, removing the coarse-grained lock will at least improve concurrency up to the "best" that green-threaded implementations can do, which isn't too bad.
The practical implication of this is that rather than having to run a Rails instance for every process you want to handle at the same time, you will only have to run a certain constant number of instances for each core in your system. Some people use N + 1 or 2N + 1 as their metric to map from cores (N) to the number of instances you would need to effectively utilize those cores. And this means that you'd probably never need more than a couple Rails instances on a one-core system. Of course you'll need to try it yourself and see what metric works best for your app, but ultimately even on green-threaded implementations you should be able to reduce the number of instances you need.
Q. Ok, what about native-threaded implementations like JRuby?A. On JRuby, the situation improves much more than on the green-threaded implementations. Because JRuby implements Ruby threads as native kernel-level threads, a Rails application would only need
one instance to handle all concurrent requests across all cores. And by one instance, I mean "nearly one instance" since there might be specific cases where a given application bottlenecks on some shared resource, and you might want to have two or three to reduce that bottleneck. In general, though, I expect those cases will be extremely rare, and most would be JRuby or Rails bugs we should fix.
This means what it sounds like: Rails deployments on JRuby will use 1/Nth the amount of memory they use now, where N is the number of thread-unsafe Rails instances currently required to handle concurrent requests. Even compared to green-threaded implementations running thread-safe Rails, it willl likely use 1/Mth the memory where M is the number of cores, since it can parallelize happily across cores with only "one" instance.
Q: Isn't that a huge deal?A: Yes, that's a huge deal. I know existing JRuby on Rails users are going to be absolutely thrilled about it. And hopefully more folks will consider using JRuby on Rails in production as a result.
And it doesn't end at resource utilization in JRuby's case. With a single Rails instance, JRuby will be able to "warm up" much more quickly, since code we compile and optimize at runtime will immediately be applicable to all incoming requests. The "throttling" we've had to do for some optimizations (to reduce overall memory consumption) may no longer even be needed. Existing JDBC connection pooling support will be more reliable and more efficient, even allowing connection sharing from application to application as well as across instances. And it will put Rails on JRuby on par with other frameworks that have always been (probably) thread-safe like Merb, Groovy on Grails, and all the Java-based frameworks.
Naturally, I'm thrilled. :)
by
Robert Gogolok | 2 days ago |
Read more
The fixtures path in merb_activerecord version 0.9.4 is now by default spec/fixtures instead of test/fixtures!
by
Ezwan Aizat bin Abdullah Faiz | 2 days ago |
Read more
aizatto: when it comes to HTTP status codes, I'm spoiled for choice!
by
Scott Motte | 2 days ago |
Read more
I’ve installed WP-Syntax on my blog. It will help brighten up my lines of code.
It was an easy install and pretty easy to use. Intead, of just using the pre html tag, I know do something like this:
pre lang=”ruby” line=”1″
#put some ruby code
Categories.find(:all, :conditions => ['cool_field = ?', 'awesome'])
pre
1
2
#put some ruby code
Categories.find(:all, :conditions => ['cool_field [...]
by
Ruslan Voloshin | 2 days ago |
Read more
Рапидшара, аплоад.ком.юа.
Наконец google page creator .
Выложи там, а сюда ссылку дай.
Лично я считаю, что если начал изучать, то купи себе книжку! (С)
Это существенно дешевле чем ломать глаза перед монитором.
by
Rick Bradley | 2 days ago |
Read more

(posted by rickbradley)
zoom
by
Scott Motte | 2 days ago |
Read more
Detailed tutorial on nginx, mysql, php, wordpress setup. bonus: it includes setup instructions for the super cache plugin
Tell us what you think of the new BlogSphere feature. We are continually looking to improve and update the
functionality based on your feedback.