Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
local web development tool Virtualhostx offer on today only
Mac users who want to develop locally on their machine with a proper test domain names instead of subdirectories under localhost, and don’t want to shell out for Mamp Pro (39€), there’s an offer on today for another product called VirtualhostX at only 10,95$ or ~7,75 € (normally 19$).
I use Mamp Pro, which makes life very easy, so can’t vouch for VirtualhostX but in principle they aim to do mostly the same thing. Some major advantages to a basic MAMP or XAMPP installation:- use an almost equal sounding domain development name (makes on/offline transfers easy as no subfolders involved)
- locate one’s files outside of the MAMP or XAMPP directory, allowing you to update MAMP more easily without losing stuff.
- you can, of course, do this all manually for free, but these programs mean you don’t need to manual fiddling with httpd, vhttpd and hosts files.
» macupdate virtualhostx promo.
» link to google’s search results on using virtualhostx with mamp(via google.
TXP Builders – finely-crafted code, design and txp
Offline
Re: local web development tool Virtualhostx offer on today only
jakob wrote:
you can, of course, do this all manually for free, but these programs mean you don’t need to manual fiddling with httpd, vhttpd and hosts files.
That’s one of the mysteries that has baffled me for the longest. Since the Macs are used by so many web developers, you’d think Apple would of made it easier for people to modify their hosts file and add a virtualhost to the Apache server.
Coming from a Linux background, where today it’s rather easy to add domains via the new Apache 2.* config files layout, seeing mention of MAMP and other services on top of what is already built into OS X, had me wondering why the need.
But for $10, having a utility to do the grunt work of configuring your environment is not bad.
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Re: local web development tool Virtualhostx offer on today only
Nice find jakob – it’s a pretty neat app.
hcgtv wrote:
Coming from a Linux background, where today it’s rather easy to add domains via the new Apache 2.* config files layout, seeing mention of MAMP and other services on top of what is already built into OS X, had me wondering why the need.
Bert, what do you do for adding new vhosts? On Ubuntu, I usually do:
$ sudo -s
$ cd /etc/apache2/sites-available/
$ cp <existing_site> <new_site>
$ a2ensite <new_site> && vim !$
$ echo 127.0.0.1 <new_site>.<tld> >> /etc/hosts
$ /etc/init.d/apache2 reload
On OS X (MacPorts, but similar to the default Apache install), it’s:
$ sudo -s
$ vim /opt/local/apache2/conf/extra/httpd-vhosts.conf # cp an existing vhost
$ echo 127.0.0.1 <new_site>.<tld> >> /etc/hosts
$ apachectl restart
I prefer Debian/Ubuntu’s way of doing virtual hosts, but OS X’s isn’t too bad. Personally, I prefer a CLI to a GUI for most applications, but a GUI is nice for applications I’d rather not RTFM for (e.g., window managers).
Offline
Re: local web development tool Virtualhostx offer on today only
jm wrote:
Bert, what do you do for adding new vhosts? On Ubuntu, I usually do:
As you outline, it’s the steps I take on Debian also.
I do create the new domains’s directory under /var/www/ before reloading apache and I also create a custom log file for the domain and throw it into a seperate directory under /var/log/apache2/, just to make going through the error messages an easier task.
In the Apache 1.3 days it was a chore, but with Apache2 and the way Debian lays out their config files, it’s been a pleasant experience dealing with the web server. I imagine Ubuntu, as evidenced by the steps you also take, follows the same config layout.
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline