Highlighted

clarification on Developer vs. Enterprise version

New Here ,
Aug 14, 2014

Copy link to clipboard

Copied


Small Cold Fusion shop and our setup has long been that we've each had our own CF server (development version) on our desktop that we developed against.  We are being forced to move to a single server environment so I am researching best ways to do this.  The first thing that jumped out was that we'd need multiple instances of the server so that each developer could hose/restart/etc their CF service.  That obviously points to CF Enterprise and it's hefty price tag.  After some research, it appears that the developer version WILL work the same way as the Enterprise version (multiple instances), with the same limitations as dev (localhost and one other IP address).  This sounds like a much better solution, but I just wanted to confirm - is it safe to assume the ip restrictions are per instance?  Seems it'd be silly to allow multiple instances, but still limit the ip's at the overall server level.  We'll be looking for a setup where developer 1 (and their ip address) can use instance 1, developer 2 (and their ip) can use instance 2, etc.

Thanks!

Views

124

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

clarification on Developer vs. Enterprise version

New Here ,
Aug 14, 2014

Copy link to clipboard

Copied


Small Cold Fusion shop and our setup has long been that we've each had our own CF server (development version) on our desktop that we developed against.  We are being forced to move to a single server environment so I am researching best ways to do this.  The first thing that jumped out was that we'd need multiple instances of the server so that each developer could hose/restart/etc their CF service.  That obviously points to CF Enterprise and it's hefty price tag.  After some research, it appears that the developer version WILL work the same way as the Enterprise version (multiple instances), with the same limitations as dev (localhost and one other IP address).  This sounds like a much better solution, but I just wanted to confirm - is it safe to assume the ip restrictions are per instance?  Seems it'd be silly to allow multiple instances, but still limit the ip's at the overall server level.  We'll be looking for a setup where developer 1 (and their ip address) can use instance 1, developer 2 (and their ip) can use instance 2, etc.

Thanks!

Views

125

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Aug 14, 2014 0

Have something to add?

Join the conversation