I can't confirm what's going on but I believe that at least McAfee and maybe other firewall appliance providers recently starting blocking googlesyndication.com in the software of their appliances. It started happening at work this week where all of a sudden Google Adsense and parts of Google Analytics were unavailable to us. When I traced it, it was all requests to *.googlesyndication.com, mostly pagead2.googlesyndication.com. Once we created an entry within our McAfee appliances to allow those addresses through, everything went back to normal. YMMV.
.
12.20.2008
12.15.2008
Development Environment layout using Linux, Apache, PHP, and Subversion
Some of the age old questions I face lately are:
Some of you may be asking yourselves the same questions. The choice of dinner is a personal one. I won't go into that except to say that everyone loves a good burrito. Spicy! And you probably don't care about my take on Facebook etiquette since your friends list probably dwarfs mine.
But I do have some definite thoughts on the layout of development environments. And I find that there's a huge lack of information about this on the interweb, so here you go.
We use Linux, Apache, PHP, and subversion in our development environment and so these instructions will be biased towards these topics but I think you can apply this method using various other technologies.
I like to give each developer their own development web site and development database. I find it's easier for everyone to have their own individual sandbox to play in. We give them each their own domain using their initials, something like rzdev.domain.com for me and vbdev.domain.com for another developer, Vinny Bag-o-Donuts. We set the Apache directories up on the Linux dev box in a similar fashion:
/var/www/rzdev.domain.com/
/var/www/vbdev.domain.com/
This has a few benefits. If I need to show Vinny something with my site development, I can just send him the link to http://rzdev.domain.com/broken-page. I can make changes to code, even major infrastructure code and not break anything for the other developers. We do the same thing with the databases, prefacing them with our initials.
Now, since our dev boxes use Linux, we set up Samba for sharing on these web directories. This means that all the devs can edit files and use source code management on the Linux server itself or on their Windows machines (we use either Eclipse or Zend Studio and create projects on the shares, that's a whole different posting!).
This dev site layout is closely linked to the way we use Subversion for version control. When we start a new site or application, if we can split out the development evenly enough, we'll just have everyone work from the trunk version of the code, with each developer working on their own little section. Each developer puts the trunk in their Apache dir and we edit the Apache configs to reflect this:
/var/www/rzdev.domain.com/trunk/
/var/www/vbdev.domain.com/trunk/
The root of the dev sites typically look like this:
/var/www/rzdev.domain.com/trunk/docs ( your Apache document root )
/var/www/rzdev.domain.com/trunk/lib ( non-public PHP library code )
When we commit code changes in Subversion, we have a hook that updates our main development site here:
/var/www/dev.domain.com/trunk
Again, that site can be seen on the web at http://dev.domain.com/ This way, we can do integration testing on our code to make sure our new code doesn't break code from someone else within the dev site.
Now, the important thing here is that the Quality Assurance (QA) and Testing people ( if you're lucky enough to have them ), don't use any of these previously mentioned sites for their testing. Why not? Well, because if they're doing a good job and are therefore sufficiently anal, they're going to complain when code is changing on the site they're looking at.
So we give them their own test site and database that's viewed on the web at http://test.domain.com/ and setup in apache at:
/var/www/test.domain.com/trunk/docs
/var/www/test.domain.com/trunk/lib
The developers will meet and create the list of files and database changes that get moved over to the test site. How the actual moving is done doesn't really matter. If you have the time and energy to set up some Ant or Phing tasks, that works great. But copying/rsyncing files and running some SQL on the test database works just as well. The most important part is that the developers meet to decide which part can go to test. Otherwise, you could have code going to test and eventually production that might not be fully vetted.
When QA finds bugs in test.domain.com, they can send them to the developers. The developers can instantly start working on fixing the bugs in their own dev space at rzdev.domain.com and not affect the other developers or the ongoing testing of the application. Pretty nice right?
Advantages of this approach
Disadvantages
So what do you think? How do you setup YOUR PHP development environment?
..
- What's for dinner?
- Should I accept that friend request on Facebook for the friend of a friend of a friend that I knew 15 years ago?
- What's the best development and test environment layouts for PHP using Apache as a web server with Subversion for version control for multiple developers?
Some of you may be asking yourselves the same questions. The choice of dinner is a personal one. I won't go into that except to say that everyone loves a good burrito. Spicy! And you probably don't care about my take on Facebook etiquette since your friends list probably dwarfs mine.
But I do have some definite thoughts on the layout of development environments. And I find that there's a huge lack of information about this on the interweb, so here you go.
We use Linux, Apache, PHP, and subversion in our development environment and so these instructions will be biased towards these topics but I think you can apply this method using various other technologies.
I like to give each developer their own development web site and development database. I find it's easier for everyone to have their own individual sandbox to play in. We give them each their own domain using their initials, something like rzdev.domain.com for me and vbdev.domain.com for another developer, Vinny Bag-o-Donuts. We set the Apache directories up on the Linux dev box in a similar fashion:
/var/www/rzdev.domain.com/
/var/www/vbdev.domain.com/
This has a few benefits. If I need to show Vinny something with my site development, I can just send him the link to http://rzdev.domain.com/broken-page. I can make changes to code, even major infrastructure code and not break anything for the other developers. We do the same thing with the databases, prefacing them with our initials.
Now, since our dev boxes use Linux, we set up Samba for sharing on these web directories. This means that all the devs can edit files and use source code management on the Linux server itself or on their Windows machines (we use either Eclipse or Zend Studio and create projects on the shares, that's a whole different posting!).
This dev site layout is closely linked to the way we use Subversion for version control. When we start a new site or application, if we can split out the development evenly enough, we'll just have everyone work from the trunk version of the code, with each developer working on their own little section. Each developer puts the trunk in their Apache dir and we edit the Apache configs to reflect this:
/var/www/rzdev.domain.com/trunk/
/var/www/vbdev.domain.com/trunk/
The root of the dev sites typically look like this:
/var/www/rzdev.domain.com/trunk/docs ( your Apache document root )
/var/www/rzdev.domain.com/trunk/lib ( non-public PHP library code )
When we commit code changes in Subversion, we have a hook that updates our main development site here:
/var/www/dev.domain.com/trunk
Again, that site can be seen on the web at http://dev.domain.com/ This way, we can do integration testing on our code to make sure our new code doesn't break code from someone else within the dev site.
Now, the important thing here is that the Quality Assurance (QA) and Testing people ( if you're lucky enough to have them ), don't use any of these previously mentioned sites for their testing. Why not? Well, because if they're doing a good job and are therefore sufficiently anal, they're going to complain when code is changing on the site they're looking at.
So we give them their own test site and database that's viewed on the web at http://test.domain.com/ and setup in apache at:
/var/www/test.domain.com/trunk/docs
/var/www/test.domain.com/trunk/lib
The developers will meet and create the list of files and database changes that get moved over to the test site. How the actual moving is done doesn't really matter. If you have the time and energy to set up some Ant or Phing tasks, that works great. But copying/rsyncing files and running some SQL on the test database works just as well. The most important part is that the developers meet to decide which part can go to test. Otherwise, you could have code going to test and eventually production that might not be fully vetted.
When QA finds bugs in test.domain.com, they can send them to the developers. The developers can instantly start working on fixing the bugs in their own dev space at rzdev.domain.com and not affect the other developers or the ongoing testing of the application. Pretty nice right?
Advantages of this approach
- Uses source code management
- Developers can unit test their own code
- Developers can do integration testing between each other's code
- Developer A typically doesn't destroy code or data that developer B is using
- Developers don't destroy code or data that QA/testing is looking at
- Developers can both edit files and use source code management in either Linux or Windows environment
- Very scalable. Adding new developers into the mix is as simple as adding their respective sub domains and databases (of course, this can also be viewed as a disadvantage, see below)
- Less bugs make it to production
Disadvantages
- Lots of sysadmin overhead initially and with each subsequent domain added. You have to set up all those developer sites, rzdev, vbdev, etc. Same overhead when using branching within subversion. Plus, you have to setup all those databases and setup the config code to connect to the appropriate database for each developer domain.
- Lots of file space for all the sites and databases.
- Confusing for lone wolf and gunslinger developers who are used to overwriting production or each other's development code (too bad for them!)
So what do you think? How do you setup YOUR PHP development environment?
..
11.05.2008
Mysql and PHP help Obama become President of the United States
We have our answer to my earlier question about technology used by Obama and McCain. One small step for LAMP, one giant leap for LAMP-kind.
10.30.2008
linkedin.com needs to sync up company names when the company name changes
My invites to present and former colleagues via linkedin.com have started to tumble in as opposed to the normal trickle. I think that's a fairly accurate sign of our flagging economy as anything I can personally put a number on. Of course it could also be that I'm a loser who has never really used linkedin a lot and so have practically no contacts there. ;-)
What's annoying however is the way linkedin keeps track of company names and what happens when a company name changes. For instance, let's say I work at a company called "Davisons." I put that in my linkedin profile. "Davisons" gets bought by "Johnson, Inc" and they change the name of the company to "Johnson Davisons." So any new people coming into the company know it as "Johnson Davisons," not just "Davisons." When they look for current employees on linkedin, they won't find all of them because some have the old company named listed while some will have the new company name listed. Not to mention how bad this problem gets when one of your previous employers changes names after you have left.
This problem is what I would call an issue with name history. This kind of name history problem is starting to creep into other areas of the web as well. I've already had the misfortune of trying to email someone I haven't emailed in a few years and reached a completely different person (ie, one person's email acct was shut down and another started with the same address). Pretty embarassing -- makes me think twice about starting emails with "Hey dirtbag! Long time no see!"
The solution for linkedin's name history problem is pretty simple. They should ask you if the company has gone by any other names and let you choose from possible alternates (or even free type them). It won't take long for their system to build up the necessary relationships between past and current company names. It could even be pretty slick and auto-update old companies in your profile to their present name if the name is now different from what you specified.
A search for employees of "Davisons" in this case would give you both Davisons and Johnson Davisons and whatever other company names are "linked in" to this company.
What's annoying however is the way linkedin keeps track of company names and what happens when a company name changes. For instance, let's say I work at a company called "Davisons." I put that in my linkedin profile. "Davisons" gets bought by "Johnson, Inc" and they change the name of the company to "Johnson Davisons." So any new people coming into the company know it as "Johnson Davisons," not just "Davisons." When they look for current employees on linkedin, they won't find all of them because some have the old company named listed while some will have the new company name listed. Not to mention how bad this problem gets when one of your previous employers changes names after you have left.
This problem is what I would call an issue with name history. This kind of name history problem is starting to creep into other areas of the web as well. I've already had the misfortune of trying to email someone I haven't emailed in a few years and reached a completely different person (ie, one person's email acct was shut down and another started with the same address). Pretty embarassing -- makes me think twice about starting emails with "Hey dirtbag! Long time no see!"
The solution for linkedin's name history problem is pretty simple. They should ask you if the company has gone by any other names and let you choose from possible alternates (or even free type them). It won't take long for their system to build up the necessary relationships between past and current company names. It could even be pretty slick and auto-update old companies in your profile to their present name if the name is now different from what you specified.
A search for employees of "Davisons" in this case would give you both Davisons and Johnson Davisons and whatever other company names are "linked in" to this company.
Subscribe to:
Posts (Atom)