More on what we have done
Over the past few weeks we have been busy working but we haven’t really said much about what we have been doing. Hopefully this post will clear things up a bit.
The (dv) server
The main thing we did before releasing the beta was moving from the unsuitable (gs) Grid Server to a (dv) Dedicated Virtual Server. After about a day waiting for MediaTemple’s customer support to give us root access, and another day for them to install the developers package we were free to do whatever we wanted with it! (Their responses were only a few hours but due to timezone differences and other commitments it took us two days to get it sorted).
After that we started to move everything over to there. Rather than using the default Apache we decided to roll our own version of Lighttpd (I couldn’t find the package manager). We then setup Fastcgi and PHP 5.1 to work together nicely and then after that Juvely flew along as you see today (before it was normal to wait over 10 seconds for a page to load!).
The next thing we did was move a few bits around within the Subversion repository then create some working copies on the server. After adding some stuff to hooks/post-commit all we have to do now is commit a new revision and our working copies automatically update! This saved tonnes of time as before this we were using a script we had to run manually to update it which took ages (note: we could have done this before, but I only learned howto while setting up the (dv)). We then setup the production copy of Juvely to use branches so we didn’t accidentally break anything.
Backups
A few days later I thought “Hmm, we had better have some sort of backup system”. I saw the MediaTemple offered a live snapshot system for the whole (dv) but this was another $20 a month, a bit too much as we aren’t making anything yet. So I did a bit of research and a couple of hours later we had an nightly offsite backup system that stores everything on Amazon S3. Backups are fully automated but every few days I still check it to delete the old backups, we could write a script for this but this adds some piece of mind. Anyway, the bill should be through next week (Im shaking in my boots!) so I’ll see how it compares to MediaTemple’s offerings on cost.
Communication
One thing that we wanted people to be able to do when we launched into the beta was to easily contact us. We setup forums, contact forms and email addresses but so far they have hardly been used. The forums are currently just holding our (rather poor) documentation and the contact forms and email addresses are just as bad. The contact us form on the site sends as email to support@juvely.com as does the one within Juvely. This email address is an alias to James’ and I email addresses. So hopefully you can see the problem: how do we know whether the other person has replied? Well, we don’t - so if you report something and get an email back from both James and myself, sorry! Anyway, we should be sorting something out in the next few days so I’ll post again then with what we did.
Righty, I think that is all I planned to explain today. I don’t think I missed anything, but if you know something I did miss or want to know more then leave a comment below! We should have a rollout later today or tomorrow with some new features, so keep an eye open!
Update:
We had an email from one of the MediaTemple Customer Support blokes saying they are glad to hear that that (dv) server is suitable for our needs! He said that he has passed on our suggestion about integrating root access and the developer tools into an option in the (mt) account centre! He also pointed out that the Plesk interface has a similar backup system included (at no extra cost) similar to what we are already doing. Details of the (dv) backup options can be found here.