Re: [gentoo-user] A networking question...

[Mick <michaelkintzios@gmail.com>]

2009/5/8 Steve <gentoo_sjh@shic.co.uk>:
> Mick wrote:
>>
>> An adaptor can have more than one public IP address (multi-homing) and you
>> can use something like: ifconfig eth0:0 192.168.0.2 netmask 255.255.255.0 up
>> to set them up (increment eth0:1, eth0:2, etc accordingly).  However, if
>> your SSL vhost is listening on a random port you don't need binding of many
>> addresses to one NIC.  You can use the same ip address.
>>
>
> This is the essential bit I was missing, I think.  I knew it was possible to
> set up "multi-homing" (as I'd seen it on other systems) but I'd forgotten
> what it was called... and that made searching for documentation, erm,
> hard... though even knowing the term hasn't given me a slam-dunk search
> result through google.  I presume I need to fiddle with /etc/conf.d/net -
> somehow - in order to convince /etc/init.d/net.eth0 to do what I need.

Well, how often do you reboot?  You only need to run it once and
therefore you won't need to modify your conf.d/net configuration.  If
you have to, I think it that file is well commented anyway.

>> Other than vhost I guest you can run a second instance by reading section
>> 5 here (but I'm not sure you need to do that anyway):
>>
>> http://www.gentoo.org/proj/en/php/php4-php5-configuration.xml
>
> That's all helpful material - suggesting, at least, that there's no neat
> gentoo-specific one-liner to achieve the two instances I need... plus it
> highlights specific problems I might have with interactions between PHP in
> my two instances. Hmmm... I hadn't anticipated that... frustrating.

No, this would only be the case if you *need* to run two separate php
slots.  In your case (I assume) you will be using the same php
version.

> I guess the other route I could consider would be virtualisation -
> establishing a completely separate installation... at least that way I could
> be sure that no aspect of my 'alive' system could impact the configuation of
> my development system... allowing me maximum confidence that I know what's
> needed when I come to deploy.

That's perhaps more complicated a solution than what it needs to be.

> Somewhat frustratingly, this seems to be morphing into a considerably more
> involved problem than I'd envisaged. ;)

I don't know if your https dev't website uses different php, ruby,
perl, etc. versions and what not.  However, if all these are kept the
same then as long as you point your dev't SSL site it to a different
mysql user/database (assuming you're using one) and you keep its
webroot fs into a different directory with separate user
authentication, then your're good to go with just the virtual hosts
solution that I suggested and webdav access for editing its content.
No need for multi-homing, complete virtualisation or anything else.
Ask if you need more detail on setting it up.

HTH.
-- 
Regards,
Mick