AMule: Difference between revisions
(→Installation: style) |
|||
(14 intermediate revisions by 4 users not shown) | |||
Line 3: | Line 3: | ||
[[ja:AMule]] | [[ja:AMule]] | ||
[[zh-hans:AMule]] | [[zh-hans:AMule]] | ||
[ | [https://www.amule.org/ aMule] is an eMule-like client for the [[w:eDonkey Network|eDonkey Network]] and [[w:Kademlia|Kademlia]] networks, supporting multiple platforms. | ||
== Installation == | == Installation == | ||
Line 9: | Line 9: | ||
[[Install]] the {{pkg|amule}} package. | [[Install]] the {{pkg|amule}} package. | ||
{{ic|amuled}} is a full featured aMule daemon, running without any user interface (GUI). It is controlled by remote access through aMuleGUI (GTK | {{ic|amuled}} is a full featured aMule daemon, running without any user interface (GUI). It is controlled by remote access through aMuleGUI (GTK), aMuleWeb, or aMuleCmd. | ||
== Services == | == Services == | ||
The package provides two ''systemd'' [[daemon|services]]: {{ic|amuled}} and {{ic|amuleweb}}. First you need to [[#Configuration|configure]] it. You need to provide passwords for external connection and admin password for {{ic|amuleweb}}. Start {{ic|amuled}} service and {{ic|amuleweb}} if you require it. Enable them to start aMule every boot. | The package provides two ''systemd'' [[daemon|services]]: {{ic|amuled}} and {{ic|amuleweb}}. First you need to [[#Configuration|configure]] it. You need to provide passwords for external connection and admin password for {{ic|amuleweb}}. [[Start]] {{ic|amuled}} service and {{ic|amuleweb}} if you require it. [[Enable]] them to start aMule every boot. | ||
Once {{ic|amulweb}} service is started, it is available at {{ic|http://127.0.0.1:4711}} (or with external address of your host). | Once {{ic|amulweb}} service is started, it is available at {{ic|http://127.0.0.1:4711}} (or with external address of your host). | ||
Line 22: | Line 22: | ||
All configuration and temporary files are kept in amule home directory {{ic|/var/lib/amule}} among them: | All configuration and temporary files are kept in amule home directory {{ic|/var/lib/amule}} among them: | ||
* | * for amuled {{ic|/var/lib/amule/.aMule/amule.conf}} | ||
* | * for amuleweb {{ic|/var/lib/amule/.aMule/remote.conf}} | ||
At the package | At the package installation time ''pacman'' generates a simple {{ic|amule.conf}} file with preset external connection password. The same password is used for ''amuleweb'' configuration file. One can use the password for connecting amule from other remote clients such as ''amule-gui''. | ||
To generate password, run: | To generate password, run: | ||
$ echo -n ''your password here'' | md5sum | cut -d ' ' -f 1 | $ echo -n ''your password here'' | md5sum | cut -d ' ' -f 1 | ||
The output of the above command is the encrypted password. Now you edit the | The output of the above command is the encrypted password. Now you edit the configuration file by adding following lines under section {{ic|[ExternalConnect]}}: | ||
{{hc|1=/var/lib/amule/.aMule/amule.conf|2= | {{hc|1=/var/lib/amule/.aMule/amule.conf|2= | ||
[ExternalConnect] | [ExternalConnect] | ||
Line 47: | Line 47: | ||
Start ''amuleweb'' too using the user you just created to create the configuration file: | Start ''amuleweb'' too using the user you just created to create the configuration file: | ||
$ | |||
[amule]$ amuleweb --write-config --password=''password here'' --admin-pass=''web password here'' | |||
Note that here, the ''password here'' is the unencrypted password you used to configure amuled. ''web password here'' is the unencrypted for the log in on the web interface. This command will write configuration file as such. | Note that here, the ''password here'' is the unencrypted password you used to configure amuled. ''web password here'' is the unencrypted for the log in on the web interface. This command will write configuration file as such. | ||
Line 55: | Line 56: | ||
== amulegui == | == amulegui == | ||
Amulegui is a GTK | Amulegui is a GTK interface for aMule. | ||
=== Configuring notifications === | === Configuring notifications === | ||
Some automatic actions settings are avaible through Settings | Some automatic actions settings are avaible through ''Settings > Events''. The core command ''notify-send'' (requires {{pkg|libnotify}}) is useful to set notifications, using some amule variables. In example, set the ''core command'' in the section ''Download completed'' for a notification when a download is complete: | ||
notify-send -i amule "%NAME completed (%SIZE bytes)" | |||
The option | $ notify-send -i amule "%NAME completed (%SIZE bytes)" | ||
The option {{ic|-i amule}} includes the amule icon (a custom file may be specified adding its path between apostrophes, instead of "amule" icon filename). | |||
== Docker == | |||
A [[Docker]] image is available, see https://hub.docker.com/r/ngosang/amule. | |||
== See also == | == See also == | ||
* [http://wiki.amule.org/wiki/Getting_Started Getting_Started at aMule wiki]. | * [http://wiki.amule.org/wiki/Getting_Started Getting_Started at aMule wiki]. |
Latest revision as of 13:23, 10 November 2023
aMule is an eMule-like client for the eDonkey Network and Kademlia networks, supporting multiple platforms.
Installation
amuled
is a full featured aMule daemon, running without any user interface (GUI). It is controlled by remote access through aMuleGUI (GTK), aMuleWeb, or aMuleCmd.
Services
The package provides two systemd services: amuled
and amuleweb
. First you need to configure it. You need to provide passwords for external connection and admin password for amuleweb
. Start amuled
service and amuleweb
if you require it. Enable them to start aMule every boot.
Once amulweb
service is started, it is available at http://127.0.0.1:4711
(or with external address of your host).
Configuration
At package installation time a new user account amule created. This account is used to run systemd services.
All configuration and temporary files are kept in amule home directory /var/lib/amule
among them:
- for amuled
/var/lib/amule/.aMule/amule.conf
- for amuleweb
/var/lib/amule/.aMule/remote.conf
At the package installation time pacman generates a simple amule.conf
file with preset external connection password. The same password is used for amuleweb configuration file. One can use the password for connecting amule from other remote clients such as amule-gui.
To generate password, run:
$ echo -n your password here | md5sum | cut -d ' ' -f 1
The output of the above command is the encrypted password. Now you edit the configuration file by adding following lines under section [ExternalConnect]
:
/var/lib/amule/.aMule/amule.conf
[ExternalConnect] AcceptExternalConnections=1 ECPassword=<encrypted password>
Do not forget that all files under /var/lib/amule
should be owned by amule user.
# chown amule:amule -R /var/lib/amule
amuleweb
Create configuration files
Start amuleweb too using the user you just created to create the configuration file:
[amule]$ amuleweb --write-config --password=password here --admin-pass=web password here
Note that here, the password here is the unencrypted password you used to configure amuled. web password here is the unencrypted for the log in on the web interface. This command will write configuration file as such.
amulegui
Amulegui is a GTK interface for aMule.
Configuring notifications
Some automatic actions settings are avaible through Settings > Events. The core command notify-send (requires libnotify) is useful to set notifications, using some amule variables. In example, set the core command in the section Download completed for a notification when a download is complete:
$ notify-send -i amule "%NAME completed (%SIZE bytes)"
The option -i amule
includes the amule icon (a custom file may be specified adding its path between apostrophes, instead of "amule" icon filename).
Docker
A Docker image is available, see https://hub.docker.com/r/ngosang/amule.