Utilities¶
Command Line Utilities¶
WebDyne installs several command line utilities for setup, local
development and troubleshooting. Installation location will vary
depending on your distribution - most will default to /usr/local/bin,
but may be installed elsewhere in some cases, especially if you have
nominated a PREFIX option when using CPAN. The commands provide their
own help or manual output for detailed options.
wdapacheinit-
Runs the WebDyne initialization routines, which create needed directories, modify and create Apache .conf files etc.
wdcompile-
Usage:
wdcompile filename.psp. Will compile a PSP file and use Data::Dumper to display the WebDyne internal representation of the page tree structure. Useful as a troubleshooting tool to see how HTML::TreeBuilder has parsed your source file, and to show up any misplaced tags etc.
wdrender-
Usage:
wdrender filename.psp. Will attempt to render the source file to screen using WebDyne. It is useful for testing page output from the command line and can exercise fake, PSGI, PAGI and mod_perl style request backends for troubleshooting.
wddump-
Usage:
wddump filename. Where filename is a compiled WebDyne source file (usually in/var/webdyne/cache). Will dump out the saved data structure of the compiled file.
wddebug-
Usage:
wddebug --status|--enable|--disable. Enable/disable debugging in the WebDyne code. This uses some pretty ugly methods to enable debugging in already installed modules by editing the code on-disk to re-enable debug calls - do not use in a production environment !
webdyne.psgi-
Used to run WebDyne as a PSGI process- usually invoked by Plack via
plackuporstarman, but can be run directly for development purposes.
webdyne.pagi-
Used to run WebDyne as a PAGI application. It can be run directly for development or used as a PAGI application entry point, including PAGI HTTP, SSE and WebSocket request handling where supported by the server.
webdyne.apache-
Starts a temporary Apache mod_perl instance for local development and troubleshooting. It can serve a directory or a single PSP file without installing a full system Apache configuration.
wdlint-
Run
perl -c -wover code in __PERL__ sections on any PSP file to check for syntax errors. Will automatically skip HTML code. It only checks code in the __PERL__ area, and won't check syntax in in-line perl, dynamic attributes etc.