Re: request for error checking feature [message #184068 is a reply to message #184065] |
Wed, 04 December 2013 03:45 |
Jerry Stuckle
Messages: 2598 Registered: September 2010
Karma:
|
Senior Member |
|
|
On 12/3/2013 9:42 PM, Ben Bacarisse wrote:
> Jerry Stuckle <jstucklex(at)attglobal(dot)net> writes:
>
>> On 12/3/2013 7:02 PM, Ben Bacarisse wrote:
>>> Christoph Michael Becker <cmbecker69(at)arcor(dot)de> writes:
>>>
>>>> richard wrote:
>>>>
>>>> > Correcting errors one at a time, uploading, and doing that a few hundred
>>>> ^^^^^^^^^
>>>> > times is tedious, time consuming, and damn boring.
>>>>
>>>> Set up a development environment on your local machine -- that'll save
>>>> you a lot of time. No need to upload any files in this case -- just
>>>> edit them in place and refresh the browser window.
>>>
>>> For people doing a lot of development a full server + PHP + bells +
>>> whistles is invaluable, but for simple stuff it is worth knowing that
>>> recent PHP versions come with a built-in server mode.
>>>
>>
>> Which may or may not operate the same as the production server. It
>> depends on a lot of factors, including the exact server being used,
>> the modules loaded and the server configuration, amongst other things.
>
> Yes, it's main value is probably for learning PHP or early prototyping
> where you should be able to avoid anything server specific. PHP modules
> are not a problem -- you can add those in the usual way.
>
No, it's main value is for you to develop in an environment as close to
identical on the server as possible. Everything I do server-wise is
tested on my development systems first.
>> It isn't all that hard to set up a development server pretty much
>> identical to the production server. And a lot more accurate in
>> duplicating the environment. Even for simple stuff it is invaluable.
>
> Actually I've found it to be frustratingly difficult. I help out with
> several sites with different PHP versions, each with a sightly different
> sets of PHP modules and configurations. The server types and loaded
> modules also vary a lot, and at least one site uses a module that I'd
> have to buy if I wanted accurate duplication. Rather than have multiple
> installs or virtual machines all over the place I've opted for a single
> "typical" set-up that is probably not the same as any of the live ones.
>
I have a standard setup that I use on all my servers. If I need a
different setup for a client, I'll either create a separate
configuration file for my test systems or I create a new virtual
machine. It doesn't take me more than about 30 minutes to go from
nothing to a working virtual machine.
As far as paid modules go - if it's necessary for proper operation of
the website, I get it. It's a cost of doing business.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|