aMule
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
- for amuleweb
/var/lib/amule/.aMule/remote.conf
At the package installation time pacman generates a simple 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 :
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:
$ sudo -u 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 ) 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).
Install with Docker
If you're using , there's a much faster way to do these. Start a container with this template
$ sudo docker run -d \ --name=amule \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Europe/London \ -p 4711:4711 \ -p 4712:4712 \ -p 4662:4662 \ -p 4665:4665/udp \ -p 4672:4672/udp \ -v <fill_amule_configuration_path>:/home/amule/.aMule \ -v <fill_amule_completed_downloads_path>:/incoming \ -v <fill_amule_incomplete_downloads_path>:/temp \ --restart unless-stopped \ ngosang/amule
Replace TZ=Europe/London with your location, replace fill_amule_configuration_path with existing amule configure path if any, or /home/you/.config/amule usually, and replace fill_amule_completed_downloads_path, fill_amule_incomplete_downloads_path with your host machine directory ( absolute path where you want to store downloaded files).
If the container successfully started, wait few seconds, it will run amuled and amuleweb inside, to view the auto generated password,
Open http://127.0.0.1:4711 and input the Web UI password in the .
See more on https://hub.docker.com/r/ngosang/amule .