Posted 18 Apr 2012, 4:24 am in Server Stuff
In case you're interested in the hardware behind this and my other sites, this is the post for you.
Main server: VPS.roph.eu
In both name and description, it's a VPS. As my main server, this is what almost all of my sites live on, and it continues to handle everything well, even with me starting new sites every now and then and with some of my older sites growing substantially. This VPS is from ServInt. It was my first foray into something higher up than shared webhosting, and I don't see myself leaving any time soon.
Up until recently I was on ServInt's base VPS, known as the "Essential". This originally came with 256 megs of guaranteed RAM and 1024mb burst when I ordered it back in 2006. Over the years ServInt have performed upgrades such that nowadays an Essential VPS has 768MB/1.5GB to play with. In March I moved to the next one up, the Essential+. This means that now I have 1GB guaranteed, 2GB burst. Overall, I can't complain about ServInt. They've been good to me over the years, especially in the earlier years when I was still learning the ropes of server management.
OS: CentOS 6
Other: WHM/cPanel, all bells and whistles as far as the stack goes. I've done various optimizations, though these are for another day / post.
Backup / Stats Server: nope.roph.eu
I'm not sure why I chose that name either. It was the first word said in the IRC channel for one of my sites. My next box came out of a desire to run a game server. Occasionally I'd ran an Unreal Tournament server on my ServInt VPS which performed great, though due to growth I didn't have the spare resources for it any more. I was also wanting to run a Team Fortress 2 server instead of Unreal Tournament 99, which uses... slightly more resources ;).
Nowadays, this server does something completely different - tracks my stats from most of my sites, and holds backups. This VPS is from Quickweb.co.nz, and is their Budget OpenVZ III, on a discounted yearly cycle. The main consumer of its resources is Piwik, an open source do-it-yourself stats tracker. The box keeps up nicely with tracking a few million pageviews each month. On the backup side, it's the destination for automated database backups from my main ServInt VPS. From this box I then occasionally pull recent database backups and store them at home too, should rainy days come.
OS: Debian 6
Other: Nginx, PHP5-FPM, MySQL
Download Server: rose.roph.eu
This box is from miniVPS, a UK based provider that resells from OVH in France. I have a 128MB OVZ VPS with them, and it serves my download server because the thing is fast. It maxes out my 60mbit/s line here in the UK, along with most of my friends' connections. I had originally bought this box intending to use it for VPN and IRC bouncing, though when I noticed how consistently speedy it was bandwidth wise I replaced my old download setup and moved everything here.
Some of my sites offer quite popular downloads (all legal, mind you), and my strategy up to this point had been to simply serve them off cheap shared hosting. It worked well enough :p.
OS: Debian 6
Other: Nginx, PHP-FPM only
Misc Server: lily.roph.eu
Yep, I've decided to name my servers after flowers. Why not? This is the last of my servers (for now?), and is a 128/256MB OVZ VPS from BuyVM. In all honesty, I didn't need a fourth server, but what with BuyVM's stock elusiveness and low prices, I couldn't resist. Besides, now I feel like a member of some elite club. For now, this server I use solely for my ZNC IRC bouncer. As BuyVM offer easy Reverse DNS, it's nice to show up on an IRC network with a roph.eu hostname. Though my main reason for using ZNC is the persistence and being able to connect to the same nick from multiple locations (Home desktop, laptop, intermittent Android phone). Aside from that, it's for testing and fooling around with. When you become interested in setting up and administering servers, you always want a test server. :)
OS: Debian 6
Other: Nginx, PHP-FPM, ZNC
Main server: VPS.roph.eu
In both name and description, it's a VPS. As my main server, this is what almost all of my sites live on, and it continues to handle everything well, even with me starting new sites every now and then and with some of my older sites growing substantially. This VPS is from ServInt. It was my first foray into something higher up than shared webhosting, and I don't see myself leaving any time soon.
Up until recently I was on ServInt's base VPS, known as the "Essential". This originally came with 256 megs of guaranteed RAM and 1024mb burst when I ordered it back in 2006. Over the years ServInt have performed upgrades such that nowadays an Essential VPS has 768MB/1.5GB to play with. In March I moved to the next one up, the Essential+. This means that now I have 1GB guaranteed, 2GB burst. Overall, I can't complain about ServInt. They've been good to me over the years, especially in the earlier years when I was still learning the ropes of server management.
OS: CentOS 6
Other: WHM/cPanel, all bells and whistles as far as the stack goes. I've done various optimizations, though these are for another day / post.
Backup / Stats Server: nope.roph.eu
I'm not sure why I chose that name either. It was the first word said in the IRC channel for one of my sites. My next box came out of a desire to run a game server. Occasionally I'd ran an Unreal Tournament server on my ServInt VPS which performed great, though due to growth I didn't have the spare resources for it any more. I was also wanting to run a Team Fortress 2 server instead of Unreal Tournament 99, which uses... slightly more resources ;).
Nowadays, this server does something completely different - tracks my stats from most of my sites, and holds backups. This VPS is from Quickweb.co.nz, and is their Budget OpenVZ III, on a discounted yearly cycle. The main consumer of its resources is Piwik, an open source do-it-yourself stats tracker. The box keeps up nicely with tracking a few million pageviews each month. On the backup side, it's the destination for automated database backups from my main ServInt VPS. From this box I then occasionally pull recent database backups and store them at home too, should rainy days come.
OS: Debian 6
Other: Nginx, PHP5-FPM, MySQL
Download Server: rose.roph.eu
This box is from miniVPS, a UK based provider that resells from OVH in France. I have a 128MB OVZ VPS with them, and it serves my download server because the thing is fast. It maxes out my 60mbit/s line here in the UK, along with most of my friends' connections. I had originally bought this box intending to use it for VPN and IRC bouncing, though when I noticed how consistently speedy it was bandwidth wise I replaced my old download setup and moved everything here.
Some of my sites offer quite popular downloads (all legal, mind you), and my strategy up to this point had been to simply serve them off cheap shared hosting. It worked well enough :p.
OS: Debian 6
Other: Nginx, PHP-FPM only
Misc Server: lily.roph.eu
Yep, I've decided to name my servers after flowers. Why not? This is the last of my servers (for now?), and is a 128/256MB OVZ VPS from BuyVM. In all honesty, I didn't need a fourth server, but what with BuyVM's stock elusiveness and low prices, I couldn't resist. Besides, now I feel like a member of some elite club. For now, this server I use solely for my ZNC IRC bouncer. As BuyVM offer easy Reverse DNS, it's nice to show up on an IRC network with a roph.eu hostname. Though my main reason for using ZNC is the persistence and being able to connect to the same nick from multiple locations (Home desktop, laptop, intermittent Android phone). Aside from that, it's for testing and fooling around with. When you become interested in setting up and administering servers, you always want a test server. :)
OS: Debian 6
Other: Nginx, PHP-FPM, ZNC
Posted 11 Apr 2012, 1:15 am in Blite
Update: I've fixed this to work with Blite 0.1-beta3, and also added a form after uploading an image to quickly upload another image.
I mentioned I was going to write an image uploader in my first post, though wasn't actually sure I was going to do it. But tonight was one of those nights where I just felt productive, so after a few hours of work, here it is. In true inception (or imageception, eh?) style, I've uploaded some images of me using my uploader, with my uploader:

Yup, that's it. I'm one for simplicity. This uploader is tied to Blite. You must be logged in as an administrator of the parent directory's Blite install in order to upload images. Otherwise, you'll be sent to the Blite login page.
If you'd like to use or critique it, here is the current source code. You'll also need the brilliant class.upload.php from Verot. Make a subfolder from your blite install, make sure this new folder is writable, place class.upload.php and my script in there and then access it via your browser. The script will upload images into folders based on year and month.
As I'm using a rich text editor with my blite install I can simply select the images and copypaste them into this post. For a regular install, you also get the raw HTML.
I mentioned I was going to write an image uploader in my first post, though wasn't actually sure I was going to do it. But tonight was one of those nights where I just felt productive, so after a few hours of work, here it is. In true inception (or imageception, eh?) style, I've uploaded some images of me using my uploader, with my uploader:

Yup, that's it. I'm one for simplicity. This uploader is tied to Blite. You must be logged in as an administrator of the parent directory's Blite install in order to upload images. Otherwise, you'll be sent to the Blite login page.
If you'd like to use or critique it, here is the current source code. You'll also need the brilliant class.upload.php from Verot. Make a subfolder from your blite install, make sure this new folder is writable, place class.upload.php and my script in there and then access it via your browser. The script will upload images into folders based on year and month.
As I'm using a rich text editor with my blite install I can simply select the images and copypaste them into this post. For a regular install, you also get the raw HTML.
Posted 10 Apr 2012, 1:51 pm in Blite
Apart from the default theme of course :)
I've been tinkering with this since I first started to properly use Blite and now I would say that it's rather complete. I've cleaned up a few mistakes here and there, brought everything in line and most importantly, added a text editor. Because of that, installing this theme requires more than dropping its folder into your themes directory. It's still simple though, and you don't need to modify any core Blite files.
Download BlackBlueBlite!
I included a small readme in the .zip. Just copy the theme folder into your themes directory, and then place nicEdit_blackblueblite.js and nicEditorIcons.gif into the root directory of your blite install. Keeping in line with Blite's lightness, I've used the small and efficient NicEdit, a single file Javascript library that lets you turn any text area into a WYSIWYG editor. It's what I'm using to write this post, so here's the obligatory screenshot:

I had to make a few edits to the JS library to make it play nice with this theme, since the lib has hard-coded colours. To other users out there playing with blite, it should be fairly obvious how I've added the editor; it can all be done from within sub_post.tpl.
I should also add, that in the course of writing this post I've just remembered some fixes I forgot to do, chief being the admin login page. A new version coming soon :P
I've been tinkering with this since I first started to properly use Blite and now I would say that it's rather complete. I've cleaned up a few mistakes here and there, brought everything in line and most importantly, added a text editor. Because of that, installing this theme requires more than dropping its folder into your themes directory. It's still simple though, and you don't need to modify any core Blite files.
Download BlackBlueBlite!
I included a small readme in the .zip. Just copy the theme folder into your themes directory, and then place nicEdit_blackblueblite.js and nicEditorIcons.gif into the root directory of your blite install. Keeping in line with Blite's lightness, I've used the small and efficient NicEdit, a single file Javascript library that lets you turn any text area into a WYSIWYG editor. It's what I'm using to write this post, so here's the obligatory screenshot:

I had to make a few edits to the JS library to make it play nice with this theme, since the lib has hard-coded colours. To other users out there playing with blite, it should be fairly obvious how I've added the editor; it can all be done from within sub_post.tpl.
I should also add, that in the course of writing this post I've just remembered some fixes I forgot to do, chief being the admin login page. A new version coming soon :P
Posted 9 Apr 2012, 10:32 pm in Blite
As I mentioned in my first post, this blog is powered by a new blogging script named Blite. The project is a result of Doug Robbins' work, and it would appear that I'm the first user, at least in a production sense.
Over the past two days I've been tinkering with the software, and now I'd say I'm pretty familiar with it. So for those of you who are perhaps looking to start a blog and are wondering if Blite is for you, I thought I'd share my views.
This makes it incredibly simple to setup and very light on resources, which were indeed Doug's goals in writing the software. Take a peek at the bottom of this page to see hints of its speed and memory consumption. Now while Roph.eu is running on a relatively powerful dedicated server, Blite will still fly on your run of the mill shared hosting account. It remains to be seen how it will hold up in high traffic situations, though due to its simplicity this should not be an issue. I'm a PHP/MySQL kinda guy and have not dabbled with SQLite, but from the PHP side of things, there aren't any things that stand out to me or that I would change out of resource concerns.
Yup, that's it. There are a few little extra areas with one or two options via the links at the bottom, but what you see above is pretty much all there is. This isn't a negative mind you, one thing that turns me away from Wordpress is that I find it to be prohibitively bloated.
To change your password, you literally enter the hashed variant of it. Indeed, this is something you must do as part of the initial setup process. There is no theme "installation" per se, you simply place the theme in the "themes" directory of your Blite install, and it's ready to use.

Obviously what you'll notice here is you literally write your post, exactly as it will be output. Raw HTML. This is fine for me or blite's other current users who are mostly geeks, and it means it's easy to do whatever we'd like in a post easily, such as embedding media and so on. However, a great many potential users will shy away for this reason. Though having said that, I feel I wouldn't even need to ask Doug about whether he plans to include a more advanced editor in future releases, it's surely on the to-do list.
Another feature I'd like to see is the option of uploads. Few blogs or blog posts are without included media, and though I could head off to a nice image host like imgur, I'd prefer to host my images myself. Uploading images manually and creating thumbnails myself would be dull, so to that end I'm currently working on a little image upload script that will generate various sensible thumbnails for this blog.
Overall I think Doug has a nice start on his hands here, and with continued development, Blite could become very popular. I'm sure I'm not alone in my distaste for Wordpress or simply lack of need for all of the bells and whistles that come as part of a package like WP.
Unless you are a technical user prepared to deal with HTML posting and preparing media externally, I would say at this stage that Blite is not for you. Though watch this space, I think there is great potential. :)
Over the past two days I've been tinkering with the software, and now I'd say I'm pretty familiar with it. So for those of you who are perhaps looking to start a blog and are wondering if Blite is for you, I thought I'd share my views.
Internals
Blite runs purely in PHP, using SQLite as its storage engine. SQLite is a database engine built right into PHP, and the due to how SQLite functions this means that in reality the "database" is simply one file located on your web hosting space, modified directly by PHP itself. As such, you don't need to be running a database server such as MySQL or PostgreSQL.This makes it incredibly simple to setup and very light on resources, which were indeed Doug's goals in writing the software. Take a peek at the bottom of this page to see hints of its speed and memory consumption. Now while Roph.eu is running on a relatively powerful dedicated server, Blite will still fly on your run of the mill shared hosting account. It remains to be seen how it will hold up in high traffic situations, though due to its simplicity this should not be an issue. I'm a PHP/MySQL kinda guy and have not dabbled with SQLite, but from the PHP side of things, there aren't any things that stand out to me or that I would change out of resource concerns.
Administration
One thing you can't see as an outside user is how you would administrate your Blite install. So here is what the main admin area looks like:Yup, that's it. There are a few little extra areas with one or two options via the links at the bottom, but what you see above is pretty much all there is. This isn't a negative mind you, one thing that turns me away from Wordpress is that I find it to be prohibitively bloated.
To change your password, you literally enter the hashed variant of it. Indeed, this is something you must do as part of the initial setup process. There is no theme "installation" per se, you simply place the theme in the "themes" directory of your Blite install, and it's ready to use.
Features
The next aspect I'd like to touch on is posting. Here's my view as I write this post:
Obviously what you'll notice here is you literally write your post, exactly as it will be output. Raw HTML. This is fine for me or blite's other current users who are mostly geeks, and it means it's easy to do whatever we'd like in a post easily, such as embedding media and so on. However, a great many potential users will shy away for this reason. Though having said that, I feel I wouldn't even need to ask Doug about whether he plans to include a more advanced editor in future releases, it's surely on the to-do list.
Another feature I'd like to see is the option of uploads. Few blogs or blog posts are without included media, and though I could head off to a nice image host like imgur, I'd prefer to host my images myself. Uploading images manually and creating thumbnails myself would be dull, so to that end I'm currently working on a little image upload script that will generate various sensible thumbnails for this blog.
Conclusion
You should take into account that it's still very early days for Blite. The current version number is 0.2 with the obligatory beta tag. Some parts are unfinished, others confirmed due to be scrapped or changed. This could also mean that my review quickly becomes outdated, though I'll try to add notes as and when updates occur.Overall I think Doug has a nice start on his hands here, and with continued development, Blite could become very popular. I'm sure I'm not alone in my distaste for Wordpress or simply lack of need for all of the bells and whistles that come as part of a package like WP.
Unless you are a technical user prepared to deal with HTML posting and preparing media externally, I would say at this stage that Blite is not for you. Though watch this space, I think there is great potential. :)
Posted 8 Apr 2012, 4:41 pm in Misc
I tried writing one a couple of years ago, though things kind of died. I'm also not too fond of wordpress. The following quote from bash.org puts it quite nicely:
This new blog is powered by Blite, a great little project by Doug Robbins. I first noticed his work as a fellow customer of ServInt, where he wrote some server information scripts. Then he showed up on Lowendbox.com, a great site for finding low cost small VPS servers.
On this new blog I plan to document my adventures writing and administering a number of sites, and the technology behind them. Let's see how it goes. :)
First thing to do is make a new theme for this blog. Perhaps I'll be the first Blite theme author; better get to work!
wordpress is an unauthenticated remote shell that, as a useful side feature, also contains a blogThis new blog is powered by Blite, a great little project by Doug Robbins. I first noticed his work as a fellow customer of ServInt, where he wrote some server information scripts. Then he showed up on Lowendbox.com, a great site for finding low cost small VPS servers.
On this new blog I plan to document my adventures writing and administering a number of sites, and the technology behind them. Let's see how it goes. :)
First thing to do is make a new theme for this blog. Perhaps I'll be the first Blite theme author; better get to work!

