Continued One company, one work’s infrastructure.
Now we have a “job’s flow”, perfect. But, how can we set and use “dev” and “user dev” zones?
We assumed that “pre” and “pro” are in external hostings or at least in the DMZ1. They will be set as subdomains or domains in internet as usual
But, what happen with local domains? Here are two ways of action:
First with a sysadmin department2
This way need a sysadmin because spend more time to configure all, and maintain after. but it’s more powerfull, facility the check and the only think you need are install, configure and update the combo DHCP + DNS services and local XAMP services.
Note: I’m not a sysadmin, and I don’t know if this is the best way or how automate this. I shall be grateful if you can edit and complete this section.
The way is so easy. Install and prepare DHCP and DNS servers. DHCP will be set to use our own DNS server. When this will be ok you must configure DHCP to associate developer server with a unique IP. And DNS will be set to associate this IP to local name3
Ok, in all intranet you can see devel zone with this name, perfect. Now go with “user dev” zones.
When arrive a new “user pc” at work, sysadmin must set DHCP server to associate the ethernet mac with a single IP, and DNS to associate this IP with her own “pc name”4
So far, so easy and smooth. You can use local name to access at “devel”. And “machine name” for each pc.
And now, when arrive a new developer, sysadmin only have to associate unique user name with employee and create an alias between user and “pc name”5
Thus, the employee only has a easy couple of things to do. Configuring virtual servers of its own apache and checkout of the code for each project.
And in the intranet, you has CEO can check and control all user’s frontend easily; for example:
We uses “devel” name for developer zone, and we have only one employee with username “alquesada”.
We have two projects actives and developing: “develname1″ and “otherdevel”.
Well, if all be ok, you can see in the intranet:
| Project/Devel Zone | Developer Zone | User Devel Zone (alquesada) |
|---|---|---|
| develname1 | http://develname1.devel | http://develname1.alquesada |
| otherdevel | http://otherdevel.devel | http://otherdevel.alquesada |
- Remember that “pre” will be see by the client ↩
- Sysadmin dep may have one hundred employees, two, or just one, you as CEO ↩
- This will be “local”, “devel”, “dev”, or something else ↩
- It’s important to bring a comprehensive suite of business material. This can be easy if each PC has its own name as “develPC-130″ ↩
- This can become difficult exponentially with the number of employees. This is where the sysadmin will look and claim their range. ↩
Feedback
Comments
No Responses to “One company, one work’s infrastructure II”Trackbacks