I thought I’d start off the re-born blog with a post about Sweetcron. I very nearly abandoned WordPress and considered completely switching to Sweetcron the second I found it. I haven’t done though and this site will continue to use WordPress. However, I’ve set up a sub-domain to run Sweetcron at me.caramboo.com. So why two sites?
Automated Lifestream Blog Software
Sweetcron is software that pulls in the feeds offered by other sites, ideally your own or your own accounts. In particular it’s an excellent tool to aggregate all your social networking updates, uploaded images, loved songs, bookmarked links, favourited videos etc etc. If you use a site and you have a presence there, if that site has an RSS feed of your activities, Sweetcron can deal with it.
Having a site pull in a boat load of stuff is cool, but what’s the point. Well, you can serve up those feeds in any way you want and each individual feed item can display as much or as little information about itself as you want, provided of course that the information is in the feed in the first place. My personal preference is for bite sized chunks or excerpts which is probably the way most people go.
The really cool thing about it all is that once you’ve decided which feeds to import, figured out how you want them to be displayed and tweaked things a little, you can pretty much walk away and let it get on with things all on its own. If you haven’t got access to a cron utility, which is how the thing is automated, Sweetcron has a built in pseudo cron to update every 30 minutes.
So you end up with an automated sort-of-blog that records your activities. If you can’t be bothered blogging for a while but nevertheless continue tweeting or other such funky things, your legions of readers can see what you’re up to. If you still don’t get it, no worries, there’s plenty more other things to get excited about. The bottom line is, I think it’s fun.
Blogging
I mentioned that I nearly abandoned WordPress completely when I found Sweetcron. Well; as well as having all the super cool feed capabilities, Sweetcron has a built-in blogging feature. You can either have the blog posts feature amongst all the other items or even have them displayed more prominently, as in WordPress et al. The blogging facility isn’t as complex as WordPress’ but to be honest I don’t think it’s meant to be. It’s just there if you want it and it’s more than adequate for the task. I suppose you could say that you use WordPress for blogging but hey it can import RSS if you want, you can use Sweetcron as an RSS aggregator but hey it can do blogging if you want. Easy.
I’ve decided that the fun thing would be to interlink the two. Sweetcron takes the WordPress feed and WordPress can be made to list the Sweetcron latest items. Your blog then doesn’t get all cluttered and your lifestream just becomes that, a record of your day to day interaction with the interweb, all on its lonesome. Sweet.
Themes
Just as in WordPress, Sweetcron is themeable. OK there aren’t kazillions of themes out there but it’s relatively easy to get build your own theme based on the default ones that come supplied with the software or one of the third party themes available.
I’m currently using the SocialCubes Theme by Derek Punsalan. Tweaked a bit as usual by me. As always I’m intending to build my own theme from scratch but hey, I’m a slow worker remember!
I found a couple of pages that list Sweetcron themes:
So Let it Roll
So there you go, my Sweetcron lifestream is up and running and there for all to see. If you fancy one yourself and want some help, you can join the Sweetcron Google Group or just contact me and I’ll be glad to help out where I can.
Sweetcron and Nginx
I use the alternative (to Apache) web server Nginx to run my sites. It took me a while to figure out how to get Sweetcron to work happily under Nginx as there’s some rewriting to be done. After ages I finally figured out a way to make it work. The details are below after the read more:
Server Config:
# ———-
server {
listen 80;
server_name foo.bar.com;
access_log /var/log/nginx/foo.bar_access.log;
error_log /var/log/nginx/foo.bar_error.log;
location / {
root /var/www/foo.bar.com/;
index index.php index.html;
if (!-e $request_filename) {
rewrite ^(.*)$ /index.php last;
break;
}
}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
location ~ .php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
include /etc/nginx/fastcgi_params;
fastcgi_param SCRIPT_FILENAME /var/www/foo.bar.com/index.php;
}
}
#———————-
The /etc/nginx/fastcgi_params are unchanged from those that work for WordPress etc:
#———————-
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param SCRIPT_NAME $fastcgi_script_name;
fastcgi_param REQUEST_URI $request_uri;
fastcgi_param DOCUMENT_URI $document_uri;
fastcgi_param DOCUMENT_ROOT $document_root;
fastcgi_param SERVER_PROTOCOL $server_protocol;
fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE nginx/$nginx_version;
fastcgi_param REMOTE_ADDR $remote_addr;
fastcgi_param REMOTE_PORT $remote_port;
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $server_name;
# PHP only, required if PHP was built with --enable-force-cgi-redirect
fastcgi_param REDIRECT_STATUS 200;
#—————————–
In system/application/config/config.php I made sure this line read like so:
#——————————
$config['uri_protocol'] = "REQUEST_URI";
#——————————
Hope that helps someone out.
I am running WordPress with FeedWordPress at http://www.blogcottage.com as a RSS aggregator. What are the advantages of using Sweetcron over FeedWordPress and WP.
I just checked out FeedWordPress and my first impression was that it's similar to Planet. In fact when I read further it seems its author developed FeedWordPress as a replacement to Planet for his needs.
I reckon you could probably configure FeedWordPress to do a similar job to Sweetcron and vice versa. However, I personally think that FeedWordPress would be more suited to the aggregation of public feeds whereas Sweetcron would be better for its intended purpose, i.e. a personal lifestream.
I suppose at the end of the day there's more than one way to skin a cat. In any case, I'm going to install FeedWordPress just for a look-see.