CHAPTER 15 ■ AN INTRODUCTION TO PEAR AND PYRUS
There’s enough in place now to for me to run a browser test. Figure 15.1 shows the default page that
PEAR2_SimpleChannelFrontend-0.1.0.phar generates.
Figure 15–1. The Channel Frontend Default Page
This means I already have my own channel. I can confirm this on a remote command line.pear channel-discover pear.appulsus.com
Adding Channel "pear.appulsus.com" succeeded
Discovery of channel "pear.appulsus.com" succeeded
Notice I'm using PEAR on the client side. I‘m hoping to demonstrate that these Pyrus tools can
provide service to a user running with a traditional PEAR setup. So far so good!
Managing a Package
Now that pear.appulsus.com can be recognized as a channel, I can alter the package.xml for Dialekt so
that it belongs there: