Skip navigation
RLS
Currently Being Moderated

Best Method For Server Variables in Multi-Developer / Multi-Server environment?

May 14, 2012 9:34 AM

In addition to having a development environment on my laptop and my desktop, we have a staging server and a production server. Furthermore, we have one or more developers and contributors who may have one or more development environments of their own.

 

Each of these environments may have their own copy of ColdFusion (developer, standard, enterprise - whatever is needed) and their own copy of SQL Server / Express / whatever, their own data source name, data user name, data password, names for CF Mappings, and so forth.  So, while the SQL tables and directory structure of the code is all the same, there are many things different from one to the next.

 

Certainly, we need to have a large number of variables so when someone uploads via SVN commit they don't screw everyone else up because they shove their own local names into place.

 

How do YOU handle that?  XML file?  CFC? some form of .INI file?   Looking for a solid way to handle this for a myriad of developers and environments, so I welcome seeing YOUR solution.

 

Thank you!

RLS

 
Replies
  • Currently Being Moderated
    May 14, 2012 3:28 PM   in reply to RLS

    Hello,

     

    There isn't any real 'right' way to do it, but there are lots of 'standards' and 'guidelines' that can be implemented.  The trick is coming up with ones that the team members will use.

    If at all possible, everything should be planned out and agreed upon before any code is written.

    Changes to the agreed upon variables, code etc. should be communicated with team members via an approved medium (email, Jira updates, whatever works for your group).

    If you have a project manager or resource manager, sometimes their duties may be able to help reinforce whatever 'standards' your group decides to enact.

     

    If your group writes their applications as. . well, applications  (using CFCs), then you can scope your variables for just the CFC's in question.   That doesn't solve all of the problems or issues, but it can certainly help.

     

    Some of the MVC methodologies can help as well, since they help to reinforce your teams coding practices by their very nature.  There are a number of them that are out there that are rather solid.  FuseBox, ColdBox, Model Glue etc.

     
    |
    Mark as:
  • Currently Being Moderated
    May 15, 2012 6:35 AM   in reply to RLS

    RLS wrote:

     

    In addition to having a development environment on my laptop and my desktop, we have a staging server and a production server. Furthermore, we have one or more developers and contributors who may have one or more development environments of their own.

     

    Each of these environments may have their own copy of ColdFusion (developer, standard, enterprise - whatever is needed) and their own copy of SQL Server / Express / whatever, their own data source name, data user name, data password, names for CF Mappings, and so forth.  So, while the SQL tables and directory structure of the code is all the same, there are many things different from one to the next.

     

    Certainly, we need to have a large number of variables so when someone uploads via SVN commit they don't screw everyone else up because they shove their own local names into place.

    Use configuation/change management to keep track.

     

    Best Method For Server Variables in Multi-Developer / Multi-Server environment?

    ...

    How do YOU handle that?  XML file?  CFC? some form of .INI file?   Looking for a solid way to handle this for a myriad of developers and environments

    I would use a configuration management database. You could configure every application, server, environment to automatically update the database with its own data.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points