Question

Real life example:

On my local wamp server my website is structured like so:

Example/trunk/
  lib/
  config/
  model/
  web/
    index.php/
    (other web/ content e.g. JS/, CSS/)
  app/

When I up try to deploy onto a VPS hosting environment, however, the file structure I must organize in is something like this:

public_html/
  example/
    lib/
    config/
    model/
    app/
  example.com/
    index.php/
    (other web/ content e.g. JS/, CSS/)
  example2.com/ (another domain)
  example3.com/ (another domain)

My only idea for a solution is for maintaining to separate repos for the original web/ and the other files contained in trunk. However, while making it possible to maintain, forces me to fundamentally divide a single project into two separate pieces…

Any ideas for a better solution??

Answer 1

You can try to symlink stuff around, i.e. put the repo outside of public_html altogether and create symlinks from public_html to appropriate parts of the repo.