htaccess rules for Perch CMS
Perch CMS makes content management for small business clients a cinch.
The following htaccess rules help you get Perch CMS to load your website without interfering with accessing the admin console...
Server articles
Perch CMS makes content management for small business clients a cinch.
The following htaccess rules help you get Perch CMS to load your website without interfering with accessing the admin console...
Thanks, in recent years, to the introduction of Composer managing package dependencies for PHP has become much easier, quicker and far less stressful. The following are some Composer essentials that all PHP developers should be familiar with...
One of the great things about Mac OS X for developers?
The sheer amount of built-in, open source technologies available by default: Apache, Bash, Curl, Emacs, Nano, Perl, PHP, Python and Ruby to name but a handful.
In this article we'll guide you through bypassing the version of PHP installed by default on Mavericks and using a different binary instead.
Speed up your PyroCMS projects with the following optimisation tips for faster loading webpages...
If you manage a website (or a number of websites) you will inevitably, at some point, experience unwanted form spamming. It's certainly not the highlight of anyone's day but sadly a persistent experience in today's connected world. If you are able to use and configure .htaccess files on your web server then you can implement IP blocking to help minimise unwanted form spam.
When installing the Android platform for Cordova PhoneGap 3.1 on Mac OS 10.9 you might come across an error message informing you that the ant command could not be executed.
This is a relatively simple fix to implement, all it requires is a little command line jiggery-pokery.
We've been developing with Codeigniter for the past 3 and a half years but given Ellis Lab's recent announcement a lot of people are asking the same question: what's the future of the framework? Despite understanding, and agreeing with, the reasoning behind Ellis Lab's decision there are many others questioning the wisdom of 'abandoning' one of the most popular and widely used PHP frameworks. Given its adoption rate amongst the PHP development community some are viewing this decision as suicidal for the future of Codeigniter.
Many developers are predicting its demise, stating quite vocally that Codeigniter is finished, and have started abandoning the framework altogether in favour of alternatives such as Laravel. We have to ask though - is all of this speculation accurate or even fair?
We've recently started using PyroCMS for some of our projects and have been really impressed with the power, flexibility and intuitiveness of the platform (particularly compared with more widely used alternatives such as WordPress). It's safe to say that it's a CMS that we plan to continue working with for a long time to come although, in our experience, remote deployment can be a major pain to contend with...
We've recently been developing with Laravel 4 and hit some issues with getting the apache mod_rewrite rules to work when transferring a website from our local development server to the remote server.
After many headaches and roadbumps along the way here's how we resolved that issue...