Purchase additional IPs for Developer edition

Ok, thanks everyone to your posts.

We are using Git, and I'm aware not to it's best potential. I am moving to words each developer running their own copy, and yes I understand that Git can help ensure they always match up.

Appriciate your concerns, and your help.

For the time being however, we've got, and will keep for some time, a local copy of the site, that I could do with accessing from a couple more pcs.

So if anyone can elaborate on Reed's post about setting up a "fully licensed development system install" that'd be great.

Is it as simple as adding the licence key to the local server?

PeteComcar wrote: We're only a small company, we've got 2 developers so the CF Developer edition is perfect for us to work on together locally, and then we've got the standard edition on the live site. We're looking to get another developer in, which is going to obviously cause problems working on a common local server, and we also have a couple of old pcs that we use for testing locally. Paying 1k for another local copy seems a bit steep to just view the local dev site by one more computer, so I could install local dev copies on each machine and then have a single central demo pc for us to all commit our work to, so we can test before upload. Does anyone else have a similar problem? If so how do you get around it? Would anyone else like the idea of being able to purchase an additional IP count for the devloper licence? Is it something Adobe could consider? Admittedly once the development team was big enough a full version is justifiable, but not for just 1 more dev.

I don't see what the problem is. Each of the 3 developers can install his own Developer Edition. Availability is then increased to 6 IP addresses.

You have correctly identified what I consider to be the main challenge: the use of version control (CVS or SVN) to commit work.

You will get the full benefit of version control when you:

1) divide your code environment into subsections Development => Test => Acceptance => Production;

2) make strict agreements which code goes where, when and how to commit code, when to move code from one environment to the next, how and by whom?

I am assuming that you're using Eclipse as your IDE (Integrated Development Environment). Both CVS and SVN work well with Eclipse.

My 2p? I recommend not developing on a shared dev server if poss.  There's generally no reason that one needs to develop like that, I think.  There's not been a situation for me in the last 10 years with various sizes of clients / sites that I've needed to develop on a server.

--

Adam

What version of CF do you have for Standard Edition?  If CF9, then you are all set, because it allows you to setup a fully licensed development system install at no extra cost.  IF CF8, then a possibility would be to setup a second PC with developer edition, and on the existing system share out the /inetpub/wwwroot folder so that both PCs would see all of the same CF sources.  That is also more flexible because you can have independent testing going on at the same time without getting in each other's way when you need to do things like a CF restart.

-reed