Re: newbie: Zend or PEAR supported on web hosting company?

Sherm Pendley wrote:

Thomas 'PointedEars' Lahn <PointedEars@xxxxxx> writes:
Sherm Pendley wrote:
Thomas 'PointedEars' Lahn <PointedEars@xxxxxx> writes:
Derek Turner wrote:
As about PEAR, just install it in your computer, upload the files and
You meant _download_, which is unnecessary manually if you use the
`pear' program (which one could, as one would have have just
*installed* it.)
No - he meant upload. Install it on *your* computer (using pear), then
upload the result to your web space.
OK, but that's crazy.

Why? As someone else (I forget who) mentioned, 'pear' may need root
access, or may not be available on one's web hosting account.

So go get them. They are not hard to come by. But good news: `pear' is
user-configurable¹ and there's go-pear, so root and shell access is not
mandatory; only PHP-CLI and downloads to the server (see below).

_____
¹ <http://pear.php.net/manual/de/guide.users.commandline.cli.php>

But the end result of running it is just a pile of PHP files,

No, it is a little bit more than just that.

so one can work around such limited access by running it locally, then
uploading the end result when it's done.

If you think about it, it's really no crazier than developing code on
one's own desktop before uploading it to a deployment server.

The difference there is that you *know* what you changed (but preferably you
would rather use SVN & Co., and then checkout the remote repository to the
localhost and the remote servers.)

By contrast, it is not easy to see which packages are downloaded by `pear'
when it resolves the dependencies for the initially needed package, and what
exactly is changed by that. Sure, that upload approach *might* work fine
the first time. But after that you either have to clear your local PEAR
directory before you start installing another package, or always upload
*everything* PEAR to be sure that you do not miss anything (OK, rsync could
help in some cases, but people who can rsync would probably have root[-like]
access already. And it was still not a complete solution).

The sane approach is to find a hoster like Derek's and install the needed
PEAR packages there *and* on one's (local) development server.

See also:
<http://pear.php.net/manual/en/guide.users.commandline.installing.php> and
<http://pear.php.net/manual/en/installation.shared.php>.


PointedEars
--
Danny Goodman's books are out of date and teach practices that are
positively harmful for cross-browser scripting.
-- Richard Cornford, cljs, <cife6q$253$1$8300dec7@xxxxxxxxxxxxxxxx> (2004)
.

Relevant Pages