Install Mailscanner Webmin Modules
MailWatch for MailScanner is a web-based front-end to MailScanner written in PHP, MySQL and JpGraph. It comes with a CustomConfig module for MailScanner which causes MailScanner to log all message data (excluding body text) to a MySQL database which is then queried by MailWatch for reporting and statistics.
Administering a Linux server is not the most glamorous job in the world. If you haven't automated mundane tasks,...
it can entail repeating the same tasks over and over. The job gets interesting when you must administer multiple Linux servers in different locations. In the past, you had to be a command line expert who knew how to set up an SSH server on each machine that needed to be managed. However, Webmin brings virtually every administration task under one easy-to-use Web-based interface.
Webmin's real power comes from its versatility and the ability to manage virtually any Linux-based system as well as Solaris and Windows. Webmin installation is relatively painless. It does use Java for some functions, so you'll need Java installed on the workstation that will serve as your main management console. Once you have the basic Webmin package running, you’ll want to customize it to meet your specific needs. For the most part, that means installing and configuring modules.
Configuring Webmin modules
Webmin makes it possible to add more functionality through the use of modules. The standard download automatically comes with a large number of modules as part of the core system. These modules cover a wide range of management tasks, but you still might not find the tool you're looking for. At that point, you have two basic options: Find a third-party module that meets your need or write your own. You'll need to know Perl if you want to roll out your own, so hopefully someone else has already written it.
Use the Webmin administration page to install a module. Selecting Configuration under the Webmin section on the left side of the homepage will present a page of icons with labels for each option available.
Click here for a larger image
Clicking on the Webmin Modules icon will take you to another page where you can install, clone, delete or export modules. The most common task is to install a new module, and it's the default tab presented to you. Options abound for module packages -- from a local drive on the server, from a file you upload from your workstation or from a location on the Web. You can also browse a list of either standard or third-party modules by clicking the ellipsis button. Be sure you check the radio button next to the option you wish to use, as the default is set to use a local file on the server.
Click here for a larger image
Once you have your source selected, simply click on the Install Module button, and the rest will be done for you. Choosing a third-party module will download the appropriate files and install them on your target server. A 'download complete' message will let you know that all files were downloaded and should be followed by a line indicating that the module has been successfully installed and added to your access control list.
Click here for a larger image
Some modules will require additional configuration after you install them. It's even possible that you might need to have different configurations for the same module. That's where the clone tool comes in handy. Using the clone tab on the Webmin Modules page, select the module you wish to copy and give it a new name. This is especially useful for managing different databases where you want to keep your admin credentials separate.
Click here for a larger image
Webmin administration: The bottom line
Webmin is a great tool for taking the pain out of Linux administration. With a little work, you can configure it to address the majority of admin tasks you will need to do. About the only thing it can't do is turn the power back on to your server, but even that can be done remotely with the right hardware.
Next time we'll take a look at accomplishing a number of specific tasks using Webmin. We'll get a few extra modules loaded up and look at the steps needed to make it work. Once you use Webmin, you'll rarely, if ever, go back to command line administration again.
ABOUT THE AUTHOR:Paul Ferrill has a BS and MS in electrical engineering and has been writing about computers for over twenty years. He's had articles published in PC Magazine, PC Computing, InfoWorld, Computer World, Network World, Network Computing, Federal Computer Week, Information Week, and multiple Web sites.
I want to install a module in webmin by command line (bash). How do you do this?
Example:
inside this .gz: text-editor.wbm
The module (in this case text-editor) when installed via GUI:
It sends the files to several places. Example:
To /usr/share/webmin/text-editor
To : /etc/webmin/text-editor
To: /var/webmin/modules/text-editor (empty):
Important:
Install Webmin Ubuntu
Webmin installation methods used in my test:
Method 1:
Method 2:
I asked the author (Jamie Cameron) no response to the date, because he is the author of webmin and the author of the module that I try to install
Update:
I have managed to make a script that installs the text-editor module. It is not very 'elegant', but it works:
sudo chmod +x text-editor.sh && sudo ./text-editor.sh
However, there should be a better method to install any webmin module by command line
Update:
Jamie Cameron replied.
So, In my case it would be:
I hope this answer serves all interested parties
Install Webmin Ubuntu 18
The theme is closed. You can vote for the closing of the question
1 Answer
Introduction --------- Webmin is designed to allow the easy addition of new modules without changing any of the existing code. A module can be thought of as something like a Photoshop plugin or iPhone application - it can be written by someone other than the developers of Webmin and distributed under a license the developer chooses.
A module should be written to administer one service or server, such as the Unix password file or the Apache web server. Some complex system functions may even be split over several modules - for example, disk partitioning, mounting disks, and disk quota management are 3 separate modules in the standard Webmin distribution.
Modules can theoretically be written in any language. However, to make use of the Webmin API Perl version 5.8 or above should be used. A module should be written entirely in Perl, with no C functions or external binary programs. The aim is for modules to be as portable as possible across different Unix systems and CPU types.
Modules written in other languages will not be displayed using the standard Webmin UI and will not be able to call its API. For these reasons, using Perl is strongly recommended.
At their simplest, modules are really just directories of CGI programs that Webmin's web server runs. However, there are certain rules that should be followed to make sure that they work with the Webmin API, main menu, and access control system. Even though you can just stick any existing CGI script into a module directory, this is not a good idea.
Required Files
Every module has its own directory under the Webmin base directory, in which all the module's CGI programs and configuration files must be stored. For example, if the Webmin base was /usr/libexec/webmin, a module called foobar would be created or installed in /usr/libexec/webmin/foobar.
You can find this base directory by looking at the root line in your /etc/webmin/miniserv.conf file. It will differ depending on which operating system Webmin is installed.
For a module to be displayed on the main Webmin menu, it should contain at least the following files. Only module.info is mandatory though.
module.info This file contains information about the module and the operating systems it runs under. See below for details on its format. images/icon.gif The icon displayed on the main menu for this module. The icon should be 48x48 pixels and should use the same colour scheme as the other icons on the main menu. lang/en The text strings used by this module, as explained in the Internationalization section of this documentation. install_check.pl Program that checks to see if the service or program is installed and usable, returning a non-zero value if so.
Each module name on Webmin's left menu is a link to the module directory. Thus you must have an index.cgi file to be displayed when the user clicks on the link. A typical module contains many .cgi programs that are linked to from index.cgi, each of which performs some function such as displaying a form or saving inputs from a form.
When you first create a new module, it will not be in the allowed list of any Webmin user and so you will not be able to see it in the main menu. To fix this, you must first delete the file /etc/webmin/module.infos.cache to clear the cache of known modules. Then to make your module visible, either edit the file /etc/webmin/webmin.acl or use the Webmin Users module to grant yourself access.
I found a guide to the webmin module installation and removal like you are trying:
and here:
Here is a module download page:
here are all third party modules:
Use a prebuilt rpm or deb package:
The current Webmin distribution is available in various package formats for download from:
If you want to use the apt command for deb files, use it like this:
If you want to use dpkg command for installing deb packages, here’s how to do it:
In both commands, you should replace the path_to_deb_file with the path and name of the deb file you have downloaded.
From the github page:
Requirements
Perl 5.10 or higher. Installation
Best Webmin Modules
Webmin can be installed in two different ways:
By downloading a pre-built package, available for different distributions (CentOS, Fedora, SuSE, Mandriva, Debian, Ubuntu, Solaris and other) from our download page;
Note: It is highly recommended to add repository to your system for having automatic updates.
By downloading, extracting source file, and running setup.sh script, with no arguments, which will setup to run it directly from this directory, or with a command-line argument, such as targeted directory.
Note: If you are installing Webmin on Windows system, you must run the command perl setup.pl instead. The Windows version depends on several programs, and modules that may not be part of the standard distribution. You will need process.exe commmand, sc.exe command, and Win32::Daemon Perl module.
somethingSomethingsomethingSomething