[wp-hackers] WP Development & Production Sites

[Jacob Santos]

I agree with Jeremy on this. There is a TDWTF article where everyone tried
to find the best solution to keeping one's hands warm while riding
a bicycle. Now, everyone had really great ideas, including pumping warm
water in from a mechanism attached to the pedals which would warm the water
through friction or something powered by the pedaling.

The point is, "Gloves." And one shouldn't forget that.

The second point is WTF? are you doing combining Development with
Production? That is like running on thin ice, naked, and wondering why
you're dead several moments later.

The point of Development and Production is to keep them separate and if that
is not the case, then you are doing something wrong. The point of
development is testing. Once that is achieved, then you move over to
production.

Jacob Santos

On Mon, Nov 22, 2010 at 7:35 PM, William Davis <will.davis at gmail.com> wrote:

> Also, SQL dumps are a pain in the ass. Why have WP-import/export at all?
>
>
> On Nov 22, 2010, at 8:33 PM, Ryan Bilesky wrote:
>
>  that would get everything, even settings from plugins the user may no
>> longer
>> have installed.
>>
>> On Mon, Nov 22, 2010 at 5:28 PM, Andrew Nacin <wp at andrewnacin.com> wrote:
>>
>>  On Mon, Nov 22, 2010 at 7:41 PM, Ryan Bilesky <rbilesky at gmail.com>
>>> wrote:
>>>
>>>  what if there was a plugin that could backup the settings you've set
>>>>
>>> from
>>>
>>>> one site (say a dev site) and import them to another site (say your
>>>> production site).  Now I am not aware of any way currently to where a
>>>> plugin
>>>> can know what settings another plugin makes, but you could have a txt
>>>>
>>> file
>>>
>>>> with a list of option names like
>>>>
>>>> setting1
>>>> setting2
>>>> ect
>>>>
>>>> Go though the db and get_option for each of those, save it out to a file
>>>> like
>>>>
>>>> setting1:value1
>>>> setting2:value2
>>>> ect
>>>>
>>>> Import that generated file into the production site that would step
>>>>
>>> though
>>>
>>>> that file line by line and update_option to move all settings from one
>>>>
>>> site
>>>
>>>> to another.
>>>>
>>>
>>>
>>> I believe they call that an SQL dump.
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>
>>>  _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>