Posts Tagged ‘development’
After adding the status.justuptime.com feature last week, we in the JDI office have taken full advantage of the system and have it on our main development screen and I even have it on my docked iPhone (sorta like a third screen 
).
Everyone in the office is able to keep an eye on all of our servers and someone can quickly jump onto fix any problems that come up. One of our servers was seen to be down earlier so I took a photo, the server was back up and running within 2 minutes of going down thanks to the quick response system we have setup at Just Host so all is good .
Why not get your website or servers into JustUptime.com and make life easy for yourself. Automate the way you monitor your uptime and get the reports you need to keep your eye on the ball.
At Just Develop It we are always investing in new businesses and developing new products.
The picture above is a photo of the whiteboard in my office with a list of all our current JDI projects. The 2 lines with something missing are simply new projects which i decided to hide until we announce them
Over the past week I have been learning and working with Zend Framework on a new site im creating, 20DollarBanners.com. Everything has been working great all week on my windows machine, and I thought it was about time to upload to one of our live web servers for testing. As with most sites, as soon as I went from Windows to Linux all hell broke out. I got the following error, and couldn’t see anywhere in the code why it was happening.
exception ‘Zend_Controller_Dispatcher_Exception’ with message ‘Invalid controller specified (index)’ in /home/username/library/Zend/Controller/Dispatcher/Standard.php:249 Stack trace: #0 /home/username/library/Zend/Controller/Front.php(914): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http)) #1 /home/username/public_html/index.php(54): Zend_Controller_Front->dispatch() #2 {main}
After a little playing around on my local machine, I managed to reproduce the same error, and found that it was a problem with the filenames of my controller files. I checked on the linux server, and everything looked in order apart from one small difference. The filename on the server was indexController instead of IndexController, the captial I made all the difference.
After googling the problem, all I found was a load of results with pages just showing the error message, so hopefully this blog post will be of use to anyone else who finds themselves in the same situation I did.