summaryrefslogtreecommitdiff
path: root/docs/MODULES
diff options
context:
space:
mode:
authorSadie Powell <sadie@witchery.services>2020-09-11 16:28:52 +0100
committerSadie Powell <sadie@witchery.services>2020-09-28 15:28:27 +0100
commitf430522b410e43b60eac78c66fecb37400fbac18 (patch)
tree8283030bff71ce627b15555a7e06e3988e47b89d /docs/MODULES
parent907aa603801b1d06d34b23ba9e473f4b74db28fe (diff)
Rename things from services to anope.
Diffstat (limited to 'docs/MODULES')
-rw-r--r--docs/MODULES4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/MODULES b/docs/MODULES
index 52cb3b25c..d74f4f35a 100644
--- a/docs/MODULES
+++ b/docs/MODULES
@@ -22,7 +22,7 @@ Anope Modules
1. If modules are supported by your system, they will be configured
automatically when you run ./Config. The modules will be installed
to the modules directory in your data path (by default this will
- be ~/services/data/modules).
+ be ~/anope/data/modules).
2. Compile Anope as usual using ./Config. The "make" process will now
compile module support into Anope, and compile the default sample
@@ -98,7 +98,7 @@ Anope Modules
1. Make sure you're in the main source directory. (usually anope-1.X.XX/)
2. Run ./Config to find and configure modules, then `cd build`.
3. Run `make` to compile Anope, and any modules.
- 4. Run `make install` to copy the compiled binaries to the ~/services/
+ 4. Run `make install` to copy the compiled binaries to the ~/anope/
directory.
You can now use /msg OperServ MODLOAD to load the new modules.