2

On my current project the production site has the following folder structure:

--system
--config
--public_html
  -assets
  -index.php
  -admin.php
  -etc.

But, the staging site I need to create is different:

--system
--config
--public_html
  |
  |staging_subdirectory
    -index.php
    -admin.php
    -etc.

Both sites will have the system folder above web root and use focuslab's config setup.

Git workflow is also involved, so my best guess is to create a "staging" branch with the specific folder structure and only push to staging from that branch.

I know I can use a subdomain, but who would I set the $system_path variable located in the index.php and admin.php? Is staging overrides the way to go?

Any ideas?

2

I recently had this same issue. I resolved this way.

I pointed my staging domain to: | staging_subdirectory / public_html

And file structure looked like this:

--system
--config
--public_html
  |
  |staging_subdirectory
    -system
    -config
    -public_html
        -index.php
        -admin.php
        -etc.

I deployed production to / and staging to /public_html/staging_subdirectory/

| improve this answer | |
  • If I understand, the above web root -system and -config folders are empty directories in the staging server, right? – Sergio Acosta Nov 1 '13 at 21:30
  • Yes, I duplicated so staging was completely independant from production – Anna_MediaGirl Nov 2 '13 at 2:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.