Anope Services can be extended through the use of 3rd party modules, this enables extra utilities and commands, such as the extended BotServ commands many people like, and the ability to have more then one channel owner (~) at a time.

We recommend you use modules listed on the Official Anope modules site at http://modules.anope.org. Modules from other sites may not be relevant to your version, and could cause your services to crash.

When you have found a module make sure you download the right version, modules listed as being suitable for 1.7.x through to 1.8.3 should work on your version, unless you have Anope-1.9.1 and higher, in which case you need modules specific for your version. Also make sure you read the module page properly for any mention of extra steps you may need to carry out to make the module work.

1. Download the module file (.c / .cpp), and put it in your Anope source folder using your ftp program eg. WinSCP. The file needs to go in /src/modules of your Anope source, not straight into services/modules. This will either be Anope-1.8.x/src/modules or services/src/src/modules if your services was installed using the AutoInstaller.

2. Log into SSH and change directory to your Anope folder, again this depends on how your Anope was installed, one of the following:
cd anope-1.8.x replacing the x with your version (If services was installed by yourself or another human.)
OR
cd services/src if your services was installed automatically

3. Run the following commands making sure there are no error messages after each has completed:
make modules (this compiles the modules into a .so file which anope can load.)
and then:
make install (this moves the .so file into your services/modules folder so it can be loaded.)

4. Before you attempt to load the module, now is the time to add any extra information that the module requires to be in services.conf, some modules for example ircd_vhostserv and bs_fantasy_ext require this. Most modules do not require this, but ones that do will most likely fail to load, or load, and then problems appear later.

5. You can now attempt to load the module by turning on superadmin (/os set superadmin on) and typing the following on IRC:
/operserv modload MODULENAME
The module name should be the same as the file you downloaded, without the extension.
eg. /operserv modload ircd_vhostserv

6. If services is restarted the module would be unloaded, so we need to add it into services.conf to get it loaded automatically on startup.
Using WinSCP or whatever ftp program you use, open services.conf located in the /services directory.
Look near the bottom for ModuleDelayedAutoload, here is where you list modules that are to be loaded automatically, it is space separated. Add the name of the module eg. ircd_vhostserv, to the list.

Read more...

Installation

First, download Anope v1.8.7 here. After downloading the TAR archive, extract it by typing:

 tar xzvf anope-1.8.7.tar.gz

After extracting the archive, navigate to the folder by typing:

 cd anope-1.8.7

Type

 ./Config

You will now be answering some basic questions.

 Question 1: In what directory do you want the binaries to be installed?

The default answer, /home/<user>/services is fine. Just press Enter. (Note: If asked to create /home/<user>/services, just press Enter)

 Question 2: Where do you want the data files to be installed?

The default answer, /home/<user>/services is fine. Just press Enter.

 Question 3: Which group should all Services data files be owned by?

Just press Enter.

 Question 4: What should the default umask for data files be (in octal)?

Just press Enter.

 Question 5: Allow anope to automatically check for mysql libraries?

Just press Enter.
Anope will now be configured. When prompted, type make.
When prompted, type make install.
Anope has now been successfully installed. It is now safe to delete the anope-1.8.7 folder and the TAR archive.

Configuration

You should now have a services folder in the current user's home folder. To navigate to it, type:

 cd services

Download our example Anope configuration file here. Move it to the services folder, then open it with your favourite editor such as nano or pico.
Step 1 Find the line that starts with RemoteServer. If UnrealIRCd is running on the same computer that you are installing Anope on, keep 127.0.0.1 intact. Change Sup3rSERViCE to the connection password defined in your UnrealIRCd configuration file in the password-receive line.
Step 2 Find the line that starts with ServerName. Edit in your IRC network's name instead of TestIRC.
Step 3 Find the ServerDesc line. Edit it with the description of the services server that will be on your network. This will show up in a /WHOIS on any network bot, in a line that looks like this:

 ChanServ using services.TestIRC.net TestIRC Network Services

Step 4 Edit the ServiceUser line and add your network's name instead of TestIRC.
Step 5 You can edit the HelpChannel and LogChannel lines if you want, but the defaults are fine.
Step 6 Insert your network's name instead of TestIRC into the NetworkName line.
Step 7 Change the UserKey1, UserKey2, and UserKey3 lines each into random seven-digit numbers. None of the lines can start with a zero.
Step 8 Change TestIRC in the NSEnforcerUser line to your network's name.
Step 9 In the ServicesRoot line, add your nickname in. This will allow you to add and remove other services admins.

Final Editing

If you have been following since the previous Installing UnrealIRCd on Linux article, you now need to open up your unrealircd.conf file, located in your Unreal3.2 directory.
Locate the services link block.
Change TestIRC in the first line of the block to your network's name. This must match what you have in the ServerName line in services.conf.
If Anope and UnrealIRCd are both being hosted on the same computer, do not change the hostname line. If Anope is being hosted on a different system, change 127.0.0.1 to the IP of the system that Anope will be running on.
Now, you must uncomment the services link block. To do this, locate the /* that is right above the first line of the block. Remove it. Go to the end of the services link block and remove the */ that is found there.
The final step is to edit the ulines block in unrealircd.conf. Change TestIRC in the ulines block to your network's name. This must match what you have in services.conf. After that is done, save any changes that were made in the configuration files and close them.
If UnrealIRCd is already running, rehash it. If it is not running, start it.

It is now time to start Anope. Type the following commands:

 cd
 cd services
 ./services

Check to see that services have linked (An easy way to check is to /WHOIS ChanServ).

Congratulations, you now have working services on your IRC network!

Read more...