Install the complete package with local command reference and every published mode.
install xmlxml@name, and element text can be addressed as #text.
config.@env and config.application.name select different kinds of
xml <file> [key|options] · xml dump <file>xml <file>show
xml <file> <key>show one exact path or value
xml dump <file>show normalized source text
-f <text|mask> [-k|-v]find matching keys, paths or values
-w <key> : <value>write a value directly to the file
-w <key> < <file>write a value read from another file
-d <key>delete a value or path
-cvalidate the file
With the current core, a successfully opened file is immediately available as $. If this module is the highest-priority installed handler for the file extension, typing the filename by itself opens it through this command. These are core conveniences;
-f searches paths and values. Add -k for keys only or -v for values only. Queries containing * or ? are treated as masks.
-w writes immediately to the file. Use : for an inline value or < <file> to read a value from another file. -d deletes one dotted path.
Run the prepared examples directly on the page. Their results are prebuilt and shown in the browser; no terminal command is executed on the server.
Install the current compatible version. Choose Base for the complete feature set or Minimum for the reduced package; use upgrade to update a module that is already installed.
Base and Minimum are two packages of the same current module release, not separate command versions.
Install the complete package with local command reference and every published mode.
install xmlInstall the reduced package. Local reference is omitted;
install xml -mInstall exactly this published version.
install xml -v 1.1.5Ask upgrade to check compatibility and replace the installed block only when needed.
upgrade xmlRemove the extension block while leaving the core and unrelated modules intact.
install xml -uExamples are copyable command lines, not actions executed by this website. Review paths, permissions and destructive flags before running them on a real project.
cd \sandbox\config | xml app.xmlconfig.@env production
config.application.name lil-shop
config.application.debug true
config.database.host localhost
config.database.port 3306app.xmlconfig.@env production
config.application.name lil-shop
config.application.debug true
config.database.host localhost
config.database.port 3306xml $ config.application.namelil-shopxml $ config.@envproductionxml $ -f "host" -kconfig.database.host localhostxml $ -f "localhost" -vconfig.database.host localhostxml $ -w config.database.port : 3307config.database.port 3307xml $ -d config.application.debugconfig.application.name lil-shop
config.database.host localhostxml $ -cValid XMLxml dump $<?xml version="1.0" encoding="UTF-8"?>
<config env="production">…</config>xml \sandbox\config\missing.xmlFile not foundsandbox/config/app.xmlThe example uses a file or directory from the protected /sandbox/ documentation workspace.
<?xml version="1.0" encoding="UTF-8"?>
<config env="production">
<application><name>lil-shop</name><debug>true</debug></application>
<database><host>localhost</host><port>3306</port></database>
</config>
Simplifies the