AMULEWEB(1) | aMule utilities | AMULEWEB(1) |
amuleweb - aMule web server
amuleweb [-h <host>] [-p <port>] [-P <password>] [-f <path>] [-q] [-v] [-l <lang>] [-w] [-t <name>] [-s <port>] [-u] [-U <port>] [-z] [-Z] [-A <password>] [-G <password>] [-a | -d] [-L] [--no-php] [-N]
amuleweb [--create-config-from=<path>]
amuleweb [--help]
amuleweb [--version]
amuleweb [--amule-config-file=<path>]
amuleweb manages your access to amule through a web browser. You can start amuleweb together with amule(1), or separately, any time later. Options can be specified via command-line or via config-file. Command-line options take precedence over config-file options.
For all options which take a <path> value, if the path contains no directory part (i.e. just a plain filename), then it is considered to be under the aMule configuration directory, ~/.aMule.
The <lang> parameter for the -l option has the following form: lang[_LANG][.encoding][@modifier] where lang is the primary language, LANG is a sublanguage/territory, encoding is the character set to use and modifier allows the user to select a specific instance of localization data within a single category.
For example, the following strings are valid:
Though all the above strings are accepted as valid language definitions, encoding and modifier are yet unused.
In addition to the format above, you can also specify full language names in English - so -l german is also valid and is equal to -l de_DE.
When no locale is defined, either on command-line or in config file, system default language will be used.
amuleweb is capable of displaying information in different skins. These skins are called templates, and you can make amuleweb load a specific template via the -t command line option. Templates are searched in two places: first in ~/.aMule/webserver/ and then in /usr/share/amule/webserver/ if you installed with --prefix=/usr.
Each template must be in a subdirectory of the template name, and this directory must contain all files the template needs.
~/.aMule/remote.conf
~/.aMule/webserver/
$(pkgdatadir)/webserver/
Typically amuleweb will be first run as:
amuleweb -h hostname -p ECport -P ECpassword -s HTTPport -A AdminPassword -w
or
amuleweb --create-config-from=/home/username/.aMule/amule.conf
These will save settings to $HOME/.aMule/remote.conf, and later you only need to type:
amuleweb
Of course, you may specify any more or less options on the first example line, and you may also totally omit it.
Please report bugs either on our forum (http://forum.amule.org/), or in our bugtracker (http://bugs.amule.org/). Please do not report bugs in e-mail, neither to our mailing list nor directly to any team member.
aMule and all of its related utilities are distributed under the GNU General Public License.
This manpage was written by Vollstrecker <amule@vollstreckernet.de>
September 2016 | aMule webserver v2.3.2 |