One company, one work’s infrastructure III
Jul/091
Continued One company, one work’s infrastructure II.
And One company, one work’s infrastructure.
Well, but what happen if we haven’t a sysadmin department?
There are many other ways to create a work0s infrastructure. If you don’t have a sysadmin dep and want to use these techniques, you can do as follows.
First, we will assume that don’t have control or directly don’t have DNS & DCHP services. Then all employees have to be their own sysadmin.
When arrive a new developer they have to configure her own Apache server, checkout the projects and configure her own host server to associate projects with ips. Something like this:
127.0.0.1 project1 project2 …
It’s so easy, but “require“1 a strict nomeclature to document and teach to developers. And, in last instance, developer do it correctly, because there is no way to verify it.
If all is ok, you can change your own host file with all dev and project to check dev front-end.
Pros:
- So easy and so flexible.
- Don’t need sysadmin (and possible recurrent calls for systems to solve problems).
- Don’t require maintenance.
- If you don’t create a strict nomeclature, don’t need teach it to new dev.
Cons:
- It’s so less powerfull.2
- Don’t have control of user dev structure.
- Can take problems in dev with config files or with “duplicate names”.
- The CEO have to change at hand her own host file to see the devs front-end.
Then, What is the best? What’s the best for my company? The answer is I don’t know. You can use one or other, as you want. You can mix or change them for your own company situation. Or, you can invent another infrastructure.
These are the foundations of the infrastructure:
- At least, three spare servers3
- One control version server.4
- And, if you use “user dev zone“, two ways to create user dev infrastructure.
Well, with this you have a idea of how to do. I suppose5 that in future i will teach how to check “dev job”, but if you search for “SVN utils” you can easily give a idea.
- It’s not necesary, everyone can do everything. But if you want check the job or have a simple configuration file, and many developers. Should become necessary. ↩
- Yes, you can check the source – and this is the important- but it’s no easy to check front or know in with projects are the devs ↩
- User dev zone is so recomended ↩
- I recommend SVN ↩
- I have not writte so far ↩