Hi Paul,

This is pretty much what I want

Site 1 - 127.0.0.1
Site 2 - 127.0.0.2
Site 3 - 127.0.0.3

If we want anyone else to see it we update the testing server which
has a full licence on it.

Cheers,
Mark

On Mon, 7 Mar 2005 17:23:16 +1100, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> On Mon, Mar 07, 2005 at 02:58:54PM +1100, Mark Lynch wrote:
> 
> > I've just set up a new development environment and practices at a new
> > job I've started working on and come across a limitation of the CF
> > Development version and I'm keen to understand what others have done
> > to avoid it.
> >
> > The setup is as follows - pretty typical development setup with
> > Development Licences of CF on each of them.  We are using apache on
> > the machines as the web server to allow simpler management across all
> > the machines.
> >
> > We also have a development server which is a full licensed copy which
> > we use for testing.
> >
> > The problem is that we typically have a 3 of 4 different websites set
> > up on each machine which is nice and easy with apache and using named
> > virtual host we can have them all on the 127.0.0.1 address.
> >
> > The problem is you can't use ssl on virtual named hosts (or on more
> > than 1) so we can only have SSL setup on one of the sites.
> >
> > So question (finally) is: how do people get around this?
> >
> > And for MM - is there a major reason why the Developer restriction
> > couldn't be one IP address and the entire 127.0.0.1 domain?  This
> > wouldn't make it any more likely to be used  unlicensed - would it?
> 
> With Ver 7 the Developer Edition will allow access from the local
> machine + 2 other IPs. Does that specifically state that the Apache
> server must be *configured* on 127.0.0.1 ?
> 
> A simple test would be to pick a set of IPs from one of the
> private address (192.168.X.X  or 10.x.x.x) and set up several
> domains on that. Then see if CF will allow access to them
> from the server + 2 other machines.
> 
> eg:
> test1 on 192.168.1.1
> test2 on 192.168.1.2
> test3 on 192.168.1.3
> 
> That way you can generate dummy SSL certificates for them, and
> test CF. Also it'll mean that they'll never be seen by anyone
> on the 'Net.
> 
> Cheers
> 
> Paul Haddon
> Technical Services Manager
> Formstar Print Technologies
> 
> 
> ---
> You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to [EMAIL PROTECTED]
> Aussie Macromedia Developers: http://lists.daemon.com.au/
> 


-- 
www.lynchconsulting.com.au

---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to