Now that we have a Development Webserver, we may have a local DNS server running to use a local TLD on the localhost and we have SSL added to our setup, we have discarded VirtualHostX , there is one thing that needs manual labor; and we hate that! (don’t we?). Maintaining the Apache2 Virtual-Host Configuration file and – in case of a DNS-less setup – the hosts file. Now, we do this automated! (Read on!)
Posts filed under “Apache2”
Apache2 is already installed on any Mac and most setups (like MAMP or MacPorts) just ignore the built in Apache and install their own version. Shame. You wouldn’t ignore your own car just and get another one to pull a trailer while your own car can do the job perfectly.
Hi all. It’s been a while since I posted something interesting, sorry ’bout that. For now I can make setting up a new web server, or upgrading it after an OSX upgrade, a bit easier. A colleague of mine tried it and ran into some problems concerning the different steps to take, so this post should help you get it done with more ease.
When building API-like applications in PHP, one issue will always remain; a high load will eventually slow down everything. To prevent over-loading, anyone will come to the conclusion a cache is needed. The most access calls should be served without recalculating anything to free up CPU-time.
Caching can be done on Disk, in a database (indirectly also Disk-caching), or directly in memory.
To setup MemCache and use this memory-caching-system, read on :)
It has been a while since I posted my guides for setting up a local development environment and how to add SSL to this set-up. This setup, among other things, required the use of a hostname-to-ip-management type of software. My choice was VirtualHostX.
Today I have successfully eliminated the need for VirtualHostX – at least, in my development environment.