Re: Drupal or Wordpress deployment

Hey Dave,
Here is a great link from the wordpress codex about running a dev version.
WP has a built in Import/Export tool that you can use. So just Export
the prod version and download it to your local machine. Then use the
local version's Import.
http://codex.wordpress.org/Running_a_Development_Copy_of_WordPress

One of the great things about using WP is that there is typically very
little you could want to do that NO ONE has tried before, or even come up
with at least a hack for. Usually there is a plugin that does what you
want almost flawlessly. And even so, you could write a custom plugin if
you don't find anything. If you have any questions you can email me
offlist as well. I do lots of client work on the nights and weekends,
mostly in WP.

brycekmartin [at] gmail dot com


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Dave <dfx1@xxxxxxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
11/19/2011 03:36 PM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
"nWeb Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] Drupal or Wordpress deployment






Bryce, I got shut out of my own wordpress site when I installed and
activated a new theme which didn't function properly. I was just starting
with wordpress, so now, if I go beyond activating modules and creating
content I will want to do that on my dev site. If I were creating or
modifying a theme how should I go about that? Download all of prod to dev
plus the database? And after testing what do I need to upload?

2011/11/18 Bryce Martin <BMartin@xxxxxxxxxxxx>

Dave,
If you are only going to be using themes and plugins then you can test
that stuff locally on your pc. Once you have tested in different

browsers

locally and tested plugin functionality you can load them on the
production site. Heck, with Wordpress you can activate/deactivate

plugins

and themes so easily that it literally takes seconds to revert back to

the

previous theme. Most of my customers only have a production site and

the

designer uses a local copy for testing themes.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Dave <dfx1@xxxxxxxxxxxxxx>
Sent by: web400-bounces+bmartin=c-sgroup.com@xxxxxxxxxxxx
11/18/2011 02:55 PM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
"Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] Drupal or Wordpress deployment






But with Drupal or Wordpress, I'll be changing themes, adding
functionality
by activating plugins or modules. I won't know what to promote from my

dev

site to prod site.

2011/11/18 Jorge Merino <jorge@xxxxxxxxx>

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.

--
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.

--
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.



--- This message (including any attachments) is intended only for the

use

of the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential,

and

exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited.

If

you have received this communication in error, please notify us and

destroy

this message immediately. ---
--
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.