I need an experienced developer/site admin to assist with the writing of set of: RewriteCond RewriteRule Within the Apache [login to view URL] file - VirtualHost section. MORE INFO The application uses sub-domains for clients. When a client registers, they enter a sitename which I use as a subdomain under the main domain which at the moment is "[login to view URL]". An example of this would be: client's sitename is "sydney" The subdomain would be [login to view URL] Inside the application I create a directory for each registered client. The directory is created using the sitename and the first character of the sitename. An example: client's sitename is "sydney" Directory on the server would be: /root/s/sydney My needs are as follows: I want to use rules to point the [login to view URL] to the clients directory on our server. Example: [login to view URL] would point to /root/s/sydney/ on our server. There are conditions that influence and change the rule: ("sitename" refers to client's personal domain) 1. "[login to view URL]" converts to: [login to view URL] 2. "[login to view URL]" points to /root/css/ 3. "[login to view URL]" points to /root/jscript 4. "[login to view URL]" points to /root/images/ 5. "[login to view URL]" points to directory: /root/ -- please note the above is correct, when 6 below is not matched, it resolves to the root (same as [login to view URL]) 6. [login to view URL] points to directory and filename: /root/x/sitename/filename -- (where the x is the first character of the sitename) -- note: only resolves for filenames with the following suffix: htm, js,css Some examples and results needed: 1. [login to view URL] = /root/ 2. [login to view URL] = [login to view URL] = /root/ 3. [login to view URL] = /root/ 4. [login to view URL] = /root/ 5. [login to view URL] = /root/p/perth/[login to view URL] 6. [login to view URL] = /root/q/qld/[login to view URL] 7. [login to view URL] = /root/[login to view URL] 8. [login to view URL] = root/css/[login to view URL] 9. [login to view URL] = /root/t/tooma/[login to view URL]
## Deliverables
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
## Platform
Apache Server 1.3 Unix Currently running Mac OS 10.4