From: Alan T. DeKok <aland@freeradius.org>
Date: Fri, 23 Jan 2026 23:30:12 +0000 (-0500)
Subject: remove etc/raddb from the tutorials
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=078f658e685c4c5463dfd058a9d9fea426ac944b;p=thirdparty%2Ffreeradius-server.git

remove etc/raddb from the tutorials

we might rename the directory, and there's no real need to show
the full directory path.
---

diff --git a/doc/antora/modules/tutorials/pages/aditing_attributes.adoc b/doc/antora/modules/tutorials/pages/aditing_attributes.adoc
index 19f0708166b..f1e6a8b6246 100644
--- a/doc/antora/modules/tutorials/pages/aditing_attributes.adoc
+++ b/doc/antora/modules/tutorials/pages/aditing_attributes.adoc
@@ -6,7 +6,7 @@
 
 *File:*
 
-- `raddb/sites-available/default`
+- `sites-available/default`
 
 *Documentation pages:*
 
@@ -63,7 +63,7 @@ server default {
 ----
 
 We have defined the cleartext password for the user `bob` here,
-instead of defining it in `raddb/mods-config/files/authorize`, as
+instead of defining it in `mods-config/files/authorize`, as
 usual.
 
 Execute the following command to test this configuration:
diff --git a/doc/antora/modules/tutorials/pages/autz-type.adoc b/doc/antora/modules/tutorials/pages/autz-type.adoc
index 12a7df52988..af275afe253 100644
--- a/doc/antora/modules/tutorials/pages/autz-type.adoc
+++ b/doc/antora/modules/tutorials/pages/autz-type.adoc
@@ -9,8 +9,8 @@ include::ROOT:partial$v3_warning.adoc[]
 
 *Files:*
 
-- `etc/raddb/sites-available/default`
-- `etc/raddb/users`
+- `sites-available/default`
+- `mods-config/files/authorize`
 
 This exercise is a follow-up to the previous one in
 xref:multiple_modules.adoc[Multiple Modules], and it uses the `byname` and `bydate` modules
@@ -31,7 +31,7 @@ DEFAULT  Autz-Type := byname
          Fall-Through = 1
 ----------------------------
 
-In the `raddb/sites-available/default` file, edit the `authorize` section entries for
+In the `sites-available/default` file, edit the `authorize` section entries for
 the `byname` and `bydate` modules to be as follows:
 
 ----------------------
diff --git a/doc/antora/modules/tutorials/pages/dynamic-translation.adoc b/doc/antora/modules/tutorials/pages/dynamic-translation.adoc
index 09dd7872d5f..995856fe8fe 100644
--- a/doc/antora/modules/tutorials/pages/dynamic-translation.adoc
+++ b/doc/antora/modules/tutorials/pages/dynamic-translation.adoc
@@ -7,8 +7,8 @@ references.
 
 *Files:*
 
-- `etc/raddb/radiusd.conf`
-- `etc/raddb/users`
+- `radiusd.conf`
+- `mods-config/files/authorize`
 
 Run-time variables in the server may include more than simple references to
 attributes in packets. The server supports the ability to perform complex
@@ -16,7 +16,7 @@ inter-module queries, which significantly extends its usefulness. In this
 exercise, we will work through a number of different examples of configuring
 inter-module calls.
 
-To start, open `raddb/mods-available/exec` and read the sample configuration for
+To start, open `mods-available/exec` and read the sample configuration for
 the `exec` module. Then, edit the users file to add the following entry at the
 top:
 
diff --git a/doc/antora/modules/tutorials/pages/eap-md5.adoc b/doc/antora/modules/tutorials/pages/eap-md5.adoc
index 3d66769c1d9..044adcc316f 100644
--- a/doc/antora/modules/tutorials/pages/eap-md5.adoc
+++ b/doc/antora/modules/tutorials/pages/eap-md5.adoc
@@ -7,7 +7,7 @@ protocol and to send and receive test packets.
 
 *File:*
 
-- `etc/raddb/mods-available/eap`
+- `mods-available/eap`
 
 *Diagram:*
 
@@ -31,12 +31,12 @@ therefore has a more limited application. One of the most common uses for
 EAP is for wireless authentication. In this exercise, we will configure
 and test the EAP-MD5 sub-type of EAP.
 
-`raddb/mods-available/eap` has a configuration section for the `eap`
+`mods-available/eap` has a configuration section for the `eap`
 module. The EAP sub-types are configured inside of that section. By
 default, the server ships with the EAP-MD5 module enabled, and with the
 EAP module initiating EAP-MD5 for all RADIUS requests containing EAP.
 
-You should now read the appropriate section of the `raddb/mods-available/eap`
+You should now read the appropriate section of the `mods-available/eap`
 file, to verify that the `eap` module is configured and that the `md5`
 sub-module of the `eap` module is configured.
 
diff --git a/doc/antora/modules/tutorials/pages/eap-peap.adoc b/doc/antora/modules/tutorials/pages/eap-peap.adoc
index 37b999ef665..5db8cab2c0c 100644
--- a/doc/antora/modules/tutorials/pages/eap-peap.adoc
+++ b/doc/antora/modules/tutorials/pages/eap-peap.adoc
@@ -7,7 +7,7 @@ protocol and to send and receive test packets.
 
 *File:*
 
-- `etc/raddb/mods-available/eap`
+- `mods-available/eap`
 
 *Diagram:*
 
@@ -28,9 +28,9 @@ wireless client software for details on this process.
 For the initial testing of EAP-PEAP, we recommend using
 `EAP-MSCHAPv2` on the wireless client as the tunneled authentication
 protocol. You should check that the `mschap` module is configured in the
-`raddb/modules` directory. The `mschapv2` module performs EAP-MSCHAPv2
+`modules` directory. The `mschapv2` module performs EAP-MSCHAPv2
 authentication and is contained in the `eap` section of the
-`raddb/eap.conf`. While these authentication methods are similar, they
+`eap.conf`. While these authentication methods are similar, they
 are not identical. Both modules need to be configured for EAP-PEAP to
 work.
 
diff --git a/doc/antora/modules/tutorials/pages/eap-tls.adoc b/doc/antora/modules/tutorials/pages/eap-tls.adoc
index ed228157210..ac4bacfa0fd 100644
--- a/doc/antora/modules/tutorials/pages/eap-tls.adoc
+++ b/doc/antora/modules/tutorials/pages/eap-tls.adoc
@@ -9,9 +9,9 @@ protocol and to send and receive test packets.
 
 *Files:*
 
-- `etc/raddb/mods-available/eap`
+- `mods-available/eap`
 - `scripts/certs.sh`
-- `etc/raddb/certs/`
+- `certs/`
 
 EAP-TLS is an authentication protocol that uses a TLS session, along
 with client and server certificates, to authenticate a user. You
@@ -50,7 +50,7 @@ and client certificates, along with a demonstration certificate
 authority. These certificates may be used for this exercise, but should
 not be used in any live deployment of the server.
 
-You now edit the `etc/raddb/mods-available/eap` file to enable
+You now edit the `mods-available/eap` file to enable
 the `tls`. You should also set the configuration entry `default_eap_type`
 to `tls`.
 
@@ -63,7 +63,7 @@ suggest that the you consult the documentation for your wireless
 client software for details on this process.
 
 The wireless client will require the client certificate from the
-`raddb/certs` directory.
+`certs` directory.
 
 Once the wireless client has been configured to enable EAP-TLS,
 you should perform a test authentication to the server. If all goes well,
diff --git a/doc/antora/modules/tutorials/pages/eap-ttls.adoc b/doc/antora/modules/tutorials/pages/eap-ttls.adoc
index d4b186936f5..977d158b6b2 100644
--- a/doc/antora/modules/tutorials/pages/eap-ttls.adoc
+++ b/doc/antora/modules/tutorials/pages/eap-ttls.adoc
@@ -9,7 +9,7 @@ protocol and to send and receive test packets.
 
 *File:*
 
-- `etc/raddb/sites-available/default`
+- `sites-available/default`
 
 *Diagram:*
 
diff --git a/doc/antora/modules/tutorials/pages/final_group_project.adoc b/doc/antora/modules/tutorials/pages/final_group_project.adoc
index ab5d5451143..d7269aa17db 100644
--- a/doc/antora/modules/tutorials/pages/final_group_project.adoc
+++ b/doc/antora/modules/tutorials/pages/final_group_project.adoc
@@ -68,9 +68,9 @@ multiple upstream home servers.
 
 *Files:*
 
-- xref:reference:raddb/mods-available/radius.adoc[`etc/raddb/mods-available/radius`]
-- xref:reference:raddb/sites-available/default.adoc[`etc/raddb/sites-available/default`] (optionally)
-- xref:reference:raddb/mods-available/linelog.adoc[`etc/raddb/mods-available/linelog`] (optionally)
+- xref:reference:raddb/mods-available/radius.adoc[`mods-available/radius`]
+- xref:reference:raddb/sites-available/default.adoc[`sites-available/default`] (optionally)
+- xref:reference:raddb/mods-available/linelog.adoc[`mods-available/linelog`] (optionally)
 
 *Time:* 20-30 minutes
 
@@ -106,7 +106,7 @@ The local realm should not have "nostrip" set.
 
 *Files:*
 
-- xref:reference:raddb/clients.conf.adoc[`etc/raddb/clients.conf`]
+- xref:reference:raddb/clients.conf.adoc[`clients.conf`]
 
 *Time*: 15-20 minutes
 
@@ -147,13 +147,13 @@ login, retrieve the user's password and store it in
 
 *Files:*
 
-//- xref:reference:raddb/mods-available/suffix.adoc[`etc/raddb/mods-available/suffix`]
-- xref:reference:raddb/mods-available/files.adoc[`etc/raddb/mods-available/files`]
-- `etc/raddb/mods-config/files/authorize`
-- xref:reference:raddb/mods-available/ldap.adoc[`etc/raddb/mods-available/ldap`]
-- xref:reference:raddb/mods-available/redis.adoc[`etc/raddb/mods-available/redis`]
-- xref:reference:raddb/mods-available/rest.adoc[`etc/raddb/mods-available/rest`]
-- xref:reference:raddb/mods-available/sql.adoc[`etc/raddb/mods-available/sql`]
+//- xref:reference:raddb/mods-available/suffix.adoc[`mods-available/suffix`]
+- xref:reference:raddb/mods-available/files.adoc[`mods-available/files`]
+- `mods-config/files/authorize`
+- xref:reference:raddb/mods-available/ldap.adoc[`mods-available/ldap`]
+- xref:reference:raddb/mods-available/redis.adoc[`mods-available/redis`]
+- xref:reference:raddb/mods-available/rest.adoc[`mods-available/rest`]
+- xref:reference:raddb/mods-available/sql.adoc[`mods-available/sql`]
 
 *Time:* 20-60 minutes
 
diff --git a/doc/antora/modules/tutorials/pages/matching_users.adoc b/doc/antora/modules/tutorials/pages/matching_users.adoc
index 5478eb86193..bdf75f1ef60 100644
--- a/doc/antora/modules/tutorials/pages/matching_users.adoc
+++ b/doc/antora/modules/tutorials/pages/matching_users.adoc
@@ -41,7 +41,7 @@ will configure a reply message in an appropriate attribute. This
 configuration entry will cause the server to continue processing the
 file.
 
-Add the following configuration to `raddb/mods-config/files/authorize`:
+Add the following configuration to `mods-config/files/authorize`:
 
 [source,text]
 ----
@@ -90,7 +90,7 @@ appropriate attributes to the reply, to allow "bob" to use PPP and to
 assign him the IP address 192.168.10.12. This entry should also cause
 the server to continue processing the file.
 
-Update `raddb/mods-config/files/authorize` with this additional entry:
+Update `mods-config/files/authorize` with this additional entry:
 
 [source,text]
 ----
@@ -145,7 +145,7 @@ The last entry will configure any user asking for "framed" service,
 and will assign them a default route of 192.168.10.1 with netmask of
 255.255.255.0.
 
-Add this final entry to `raddb/mods-config/files/authorize`:
+Add this final entry to `mods-config/files/authorize`:
 
 [source,text]
 ----
diff --git a/doc/antora/modules/tutorials/pages/module_fail_over.adoc b/doc/antora/modules/tutorials/pages/module_fail_over.adoc
index 657a40b4aff..ecd265b4e28 100644
--- a/doc/antora/modules/tutorials/pages/module_fail_over.adoc
+++ b/doc/antora/modules/tutorials/pages/module_fail_over.adoc
@@ -9,7 +9,7 @@ include::ROOT:partial$v3_warning.adoc[]
 
 *Files:*
 
-- `etc/raddb/mods-available/detail`
+- `mods-available/detail`
 - `usr/share/doc/freeradius*/configurable_failover`
 - `/var/log/radius/radacct/detail1`
 - `/var/log/radius/radacct/detail2`
@@ -29,7 +29,7 @@ second detail file.
 
 The first step is to configure the server to have two instances of the
 `detail` module. The following information should be added to the
-`etc/raddb/mods-available/detail` file:
+`mods-available/detail` file:
 
 --------------------------------------------------
 detail detail1 {
@@ -45,10 +45,10 @@ detail detail2 {
 
 In the file `configurable_failover` in the documentation directory,
 there is a section titled "More Complex Configurations". This section contains a
-sample entry for the "accounting" section of `etc/raddb/sites-available/default`.
+sample entry for the "accounting" section of `sites-available/default`.
 The sample entry is a "group" with configurable fail-over between two modules named
 `detail1` and `detail2`. Copy the "group" section to the start of the
-`accounting` section in your `etc/raddb/sites-available/default` file.
+`accounting` section in your `sites-available/default` file.
 
 Now start the server and verify that it is `Ready to process requests.`
 
diff --git a/doc/antora/modules/tutorials/pages/new_client.adoc b/doc/antora/modules/tutorials/pages/new_client.adoc
index bb955783c06..94b4ebf5894 100644
--- a/doc/antora/modules/tutorials/pages/new_client.adoc
+++ b/doc/antora/modules/tutorials/pages/new_client.adoc
@@ -7,7 +7,7 @@ server.
 
 *File:*
 
-- `etc/raddb/clients.conf`
+- `clients.conf`
 
 The RADIUS server will only communicate with known clients. This
 restriction is for security, so that unknown machines on the Internet
diff --git a/doc/antora/modules/tutorials/pages/prepaid.adoc b/doc/antora/modules/tutorials/pages/prepaid.adoc
index 999e89bbb1b..42bb99978df 100644
--- a/doc/antora/modules/tutorials/pages/prepaid.adoc
+++ b/doc/antora/modules/tutorials/pages/prepaid.adoc
@@ -9,16 +9,16 @@ include::ROOT:partial$v3_warning.adoc[]
 
 *Files:*
 
-- `etc/raddb/mods-available/counter`
+- `mods-available/counter`
 
 Many system administrators wish to implement "prepaid" billing for
 their systems. In this exercise, we will configure the server to use a
 simple "prepaid" scheme, wherein all users will be permitted to log in
 for only one hour a day.
 
-Read `etc/raddb/mods-available/counter` and look for the `counter daily` instance
+Read `mods-available/counter` and look for the `counter daily` instance
 The documentation for the module consists solely of the comments in
-`etc/raddb/mods-available/counter`, so those comments should be read carefully.
+`mods-available/counter`, so those comments should be read carefully.
 Search the rest of the configuration file for references to the `daily` module
 and un-comment any references you find.
 
diff --git a/doc/antora/modules/tutorials/pages/proxy.adoc b/doc/antora/modules/tutorials/pages/proxy.adoc
index eaaffe31b10..3184e04aa49 100644
--- a/doc/antora/modules/tutorials/pages/proxy.adoc
+++ b/doc/antora/modules/tutorials/pages/proxy.adoc
@@ -10,7 +10,7 @@ proxy server and the home server.
 
 *File:*
 
-- `etc/raddb/proxy.conf`
+- `proxy.conf`
 
 *Diagram:*
 
@@ -21,7 +21,7 @@ requests to a home RADIUS server that is run by another user
 (the uber user)).
 
 You will configure a realm, called "realm1" in the
-`raddb/proxy.conf` file. This realm will be proxied to the RADIUS server
+`proxy.conf` file. This realm will be proxied to the RADIUS server
 administered by the uber user, who will supply the IP address, port,
 and shared secret used by their RADIUS server. The entry for the home
 server in `proxy.conf` will be configured to "strip" the realm name
diff --git a/doc/antora/modules/tutorials/pages/proxy_failover.adoc b/doc/antora/modules/tutorials/pages/proxy_failover.adoc
index 794208aeccf..69061cd635f 100644
--- a/doc/antora/modules/tutorials/pages/proxy_failover.adoc
+++ b/doc/antora/modules/tutorials/pages/proxy_failover.adoc
@@ -9,8 +9,8 @@ include::ROOT:partial$v3_warning.adoc[]
 
 *Files:*
 
-- `etc/raddb/proxy.conf`
-- `etc/raddb/clients.conf`
+- `proxy.conf`
+- `clients.conf`
 
 *Diagram:*
 
diff --git a/doc/antora/modules/tutorials/pages/proxy_load_balance.adoc b/doc/antora/modules/tutorials/pages/proxy_load_balance.adoc
index b54ea49e6f4..1d3d617ed1b 100644
--- a/doc/antora/modules/tutorials/pages/proxy_load_balance.adoc
+++ b/doc/antora/modules/tutorials/pages/proxy_load_balance.adoc
@@ -9,7 +9,7 @@ multiple home servers.
 
 *File:*
 
-- `etc/raddb/proxy.conf`
+- `proxy.conf`
 
 *Diagram:*
 
diff --git a/doc/antora/modules/tutorials/pages/proxy_receive.adoc b/doc/antora/modules/tutorials/pages/proxy_receive.adoc
index d08b074f039..6e574392d2e 100644
--- a/doc/antora/modules/tutorials/pages/proxy_receive.adoc
+++ b/doc/antora/modules/tutorials/pages/proxy_receive.adoc
@@ -9,8 +9,8 @@ RADIUS server and to receive packets from another proxy server.
 
 *Files:*
 
-- `etc/raddb/proxy.conf`
-- `etc/raddb/clients.conf`
+- `proxy.conf`
+- `clients.conf`
 
 For this exercise, the users will be divided into groups of two. One
 user will be named "realm1" and the other will be named
diff --git a/doc/antora/modules/tutorials/pages/radmin.adoc b/doc/antora/modules/tutorials/pages/radmin.adoc
index 8bf775a3c13..1d7a7fc0cf2 100644
--- a/doc/antora/modules/tutorials/pages/radmin.adoc
+++ b/doc/antora/modules/tutorials/pages/radmin.adoc
@@ -6,7 +6,7 @@
 
 *File:*
 
-- `etc/raddb/sites-enabled/control-socket`
+- `sites-enabled/control-socket`
 
 *`man` page:* radmin, raddebug
 
diff --git a/doc/antora/modules/tutorials/pages/simultaneous_use.adoc b/doc/antora/modules/tutorials/pages/simultaneous_use.adoc
index 859a6197a41..89ec2d7ae77 100644
--- a/doc/antora/modules/tutorials/pages/simultaneous_use.adoc
+++ b/doc/antora/modules/tutorials/pages/simultaneous_use.adoc
@@ -8,7 +8,7 @@ time.
 
 *Files:*
 
-- `etc/raddb/users`
+- `mods-config/files/authorize`
 
 For this exercise, you are assumed to have previously worked
 through, and be familiar with, the accounting exercise from
diff --git a/doc/antora/modules/tutorials/pages/sql.adoc b/doc/antora/modules/tutorials/pages/sql.adoc
index 149b8f9db92..7aced32b783 100644
--- a/doc/antora/modules/tutorials/pages/sql.adoc
+++ b/doc/antora/modules/tutorials/pages/sql.adoc
@@ -8,8 +8,8 @@ include::ROOT:partial$v3_warning.adoc[]
 
 *File:*
 
-- `etc/raddb/mods-available/sql`
-- `etc/raddb/mods-config/sql/main/*`
+- `mods-available/sql`
+- `mods-config/sql/main/*`
 
 In addition to the file, the server may obtain user configuration
 information from an SQL database. In this exercise, you will
@@ -28,12 +28,12 @@ maintaining and updating the databases.
 
 The SQL schema used by FreeRADIUS is designed to mirror the users file.
 Each SQL dialect has its own set of schema and configuration files.
-They are located in the `raddb/mods-config/sql/main/<dialect>` directory.
+They are located in the `mods-config/sql/main/<dialect>` directory.
 
 The schema is defined by the "schema.sql" file, and the queries are
 defined by the `queries.conf` file.
 
-The main configuration for the SQL module is `raddb/mods-available/sql`
+The main configuration for the SQL module is `mods-available/sql`
 it will `$INCLUDE` the appropriate "queries.conf" file for the dialect
 chosen.
 
@@ -44,7 +44,7 @@ use.
 ========================================================================
 Unless there is a pre-configured database available we recommend the
 sqlite driver be used. If the sqlite specific stanzas are uncommented
-in `raddb/mods-available/sql` it will automatically bootstrap a new
+in `mods-available/sql` it will automatically bootstrap a new
 database using the bundled schema.
 ========================================================================
 
@@ -66,7 +66,7 @@ in to process any authentication requests, or accounting requests. For
 now, we are interested solely in making the FreeRADIUS server
 communicate with the SQL server.
 
-Open `raddb/mods-available/sql` verify that the first few configuration
+Open `mods-available/sql` verify that the first few configuration
 entries are correct. That is, the "server", "login", and "password"
 entries should be set up correctly for your local SQL database.
 
@@ -104,8 +104,8 @@ the remainder of this exercise, we will assume that the driver is
 installed in the appropriate library directory.
 
 Once you have verified that the SQL driver exists, have enabled the module
-by creating a symlink from `raddb/mods-available/sql` to
-`raddb/mods-enabled/sql` and you have configured the appropriate sql dialect,
+by creating a symlink from `mods-available/sql` to
+`mods-enabled/sql` and you have configured the appropriate sql dialect,
 you should start the server as usual:
 
 ------------
diff --git a/doc/antora/modules/tutorials/pages/sql_user.adoc b/doc/antora/modules/tutorials/pages/sql_user.adoc
index ec55b2257bc..609dc222644 100644
--- a/doc/antora/modules/tutorials/pages/sql_user.adoc
+++ b/doc/antora/modules/tutorials/pages/sql_user.adoc
@@ -7,8 +7,8 @@ to send test packets as that user, and to receive a reply.
 
 *File:*
 
-- `etc/raddb/mods-available/sql`
-- `etc/raddb/mods-config/sql/main/*`
+- `mods-available/sql`
+- `mods-config/sql/main/*`
 
 Now that we have verified in the previous exercise,
 xref:sql.adoc[SQL] that the server can communicate with
@@ -44,7 +44,7 @@ are now in the database.
 As the previous exercise in xref:sql.adoc[SQL]
 did not tell the server to query the database, but only to connect to it,
 we must now configure FreeRADIUS to query the database. This may be done
-by editing `etc/raddb/sites-available/default`, and listing the `sql`
+by editing `sites-available/default`, and listing the `sql`
 module in the "authorize" section.
 
 There should already be a commented-out entry for `sql` in the
@@ -71,7 +71,7 @@ requests." Verify that the file entry for "bob" has not matched the
 request. Verify that the SQL module returns "ok", rather than
 "notfound".
 
-If necessary, edit the `etc/raddb/mods-enabled/sql` file, and enable
+If necessary, edit the `mods-enabled/sql` file, and enable
 additional debugging of SQL statements via the `sqltrace` and `sqltracefile`
 configuration options. If the SQL queries are performed by the server and
 logged to the file, but the request for user "bob" is still rejected, then
@@ -86,7 +86,7 @@ the queries, then send the access request again.
 3.  Why is there no "Fall-Through" entry in an SQL database?
 4.  Does that DEFAULT entry differ from its use in the file? If so, why,
 and how? If not, why not?
-5.  What other configuration entries in `etc/raddb/sites-available/default`
+5.  What other configuration entries in `sites-available/default`
     exist for the `sql` module, and why?
 
 // Copyright (C) 2021 Network RADIUS SAS.  Licenced under CC-by-NC 4.0.
diff --git a/doc/antora/modules/tutorials/pages/unlang_policies.adoc b/doc/antora/modules/tutorials/pages/unlang_policies.adoc
index 0496726ed16..fb56c242a06 100644
--- a/doc/antora/modules/tutorials/pages/unlang_policies.adoc
+++ b/doc/antora/modules/tutorials/pages/unlang_policies.adoc
@@ -6,8 +6,8 @@
 
 *Files / Directories:*
 
-- `etc/raddb/policy.d/*`   (policy.d where we create and define policies)
-- `etc/raddb/sites-available/default`  (virtual server where we call the policy)
+- `policy.d/*`   (policy.d where we create and define policies)
+- `sites-available/default`  (virtual server where we call the policy)
 
 == Preparation
 
diff --git a/doc/antora/modules/tutorials/pages/unlang_return_codes.adoc b/doc/antora/modules/tutorials/pages/unlang_return_codes.adoc
index 101d8f17c47..a12702c25e1 100644
--- a/doc/antora/modules/tutorials/pages/unlang_return_codes.adoc
+++ b/doc/antora/modules/tutorials/pages/unlang_return_codes.adoc
@@ -6,7 +6,7 @@
 
 *File:*
 
-- `etc/raddb/policy.d/*`
+- `policy.d/*`
 
 *`man` page:* unlang
 
diff --git a/doc/antora/modules/tutorials/pages/unlang_splitting_strings.adoc b/doc/antora/modules/tutorials/pages/unlang_splitting_strings.adoc
index 6d1b20fccda..cb64d560c45 100644
--- a/doc/antora/modules/tutorials/pages/unlang_splitting_strings.adoc
+++ b/doc/antora/modules/tutorials/pages/unlang_splitting_strings.adoc
@@ -4,7 +4,7 @@
 *Time:* 10-20 minutes
 
 *File:*
-- `etc/raddb/policy.d/*`
+- `policy.d/*`
 
 *`man` page:* `unlang`
 
@@ -79,7 +79,7 @@ realm-split {
 }
 ----
 
-Add the above created policy into `raddb/sites-available/default`:
+Add the above created policy into `sites-available/default`:
 
 [source,unlang]
 ----
@@ -91,7 +91,7 @@ server default {
 }
 ----
 
-Also make sure our testing user "bob" exists in `raddb/mods-config/files/authorize`:
+Also make sure our testing user "bob" exists in `mods-config/files/authorize`:
 
 [source,unlang]
 ----
diff --git a/doc/antora/modules/tutorials/pages/variables.adoc b/doc/antora/modules/tutorials/pages/variables.adoc
index d3e104f34e2..e24f9548c04 100644
--- a/doc/antora/modules/tutorials/pages/variables.adoc
+++ b/doc/antora/modules/tutorials/pages/variables.adoc
@@ -6,9 +6,9 @@
 
 *Files:*
 
-- `etc/raddb/radiusd.conf`
+- `radiusd.conf`
 - `etc/mods-config/files/authorize`
-- `etc/raddb/mods-available/detail`
+- `mods-available/detail`
 
 *`man` page:* `radiusd.conf`
 
@@ -53,7 +53,7 @@ properties of the run-time variables.
 
 The main configuration file `radiusd.conf` and the module configuration
 files contains a number of examples of the use of variables. For example,
-the `detail` module (configured in `etc/raddb/mods-enabled/detail`)
+the `detail` module (configured in `mods-enabled/detail`)
 has a configuration entry named "filename", which by default has the
 following value:
 
@@ -105,7 +105,7 @@ configuration. You should see something like this:
 
 If you don't see any configuration printed for the `detail` file module
 ensure it is uncommented in the `accounting {}` section of the
-`raddb/sites-available/default` virtual server.
+`sites-available/default` virtual server.
 
 [source]
 ----
diff --git a/doc/antora/modules/tutorials/pages/virtual.adoc b/doc/antora/modules/tutorials/pages/virtual.adoc
index e20975a941d..9bf50e66764 100644
--- a/doc/antora/modules/tutorials/pages/virtual.adoc
+++ b/doc/antora/modules/tutorials/pages/virtual.adoc
@@ -8,7 +8,7 @@ include::ROOT:partial$v3_warning.adoc[]
 
 *File:*
 
-- `etc/raddb/sites-enabled/virtual`
+- `sites-enabled/virtual`
 
 *documentation page:* raddb/sites-available/README
 
@@ -24,7 +24,7 @@ following sections:
 - *preacct* The pre-accounting section
 - *accounting* The accounting section
 
-Create a new file `raddb/sites-enabled/virtual`. Put the following text
+Create a new file `sites-enabled/virtual`. Put the following text
 into it:
 
 -----------------------------------------------