In our case, we usually create subdomains and separate install folders for each web product,
e.g.
Production: www.example.com
Dev: dev.example.com

Folders on the server:
Production: /www/drupal
Dev: /dev/drupal

Then we synchronize the changes from the dev folder to the production folder, and of course we never modify code directly on production folders.

~jmerinoh


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Dave
Sent: Friday, November 18, 2011 11:47 AM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] Drupal or Wordpress deployment

Hi all,

Just wondered if anyone's using Drupal or Wordpress and how you are going about taking your production site to development, to staging and then back to production. I mean, how do you know what get's modified exactly? In my case I will probably just have my development server and no staging site.

Thanks.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.