Customizable API auditing URLs via template filter (#652)

Closes #636

docs/installation/services/discord.md

@@ -29,7 +29,7 @@ This returns a code that looks like `https://discord.gg/0fmA8MyXV6qt7XAZ`. The p
 
 Navigate to the [Discord Developers site.](https://discordapp.com/developers/applications/me) Press the plus sign to create a new application.
 
-Give it a name and description relating to your auth site. Add a redirect to `https://mydomain.com/discord_callback`, substituting your domain. Press Create Application.
+Give it a name and description relating to your auth site. Add a redirect to `https://example.com/discord_callback`, substituting your domain. Press Create Application.
 
 Update settings.py, inputting this redirect address as `DISCORD_CALLBACK_URL`
 

docs/installation/services/discourse.md

@@ -71,7 +71,7 @@ Discourse must run on its own subdomain - it can't handle routing behind an alia
 And enter the following, changing the port if you used a different number:
 
     <VirtualHost *:80>
-        ServerName discourse.mydomain.com
+        ServerName discourse.example.com
         ProxyPass / http://0.0.0.0:7890/
         ProxyPassReverse / http://0.0.0.0:7890/
     </VirtualHost>
@@ -94,22 +94,22 @@ Follow prompts, being sure to answer `y` when asked to allow admin privileges.
 
 ### Create API key
 
-Navigate to `discourse.mydomain.com` and log on. Top right press the 3 lines and select `Admin`. Go to API tab and press `Generate Master API Key`.
+Navigate to `discourse.example.com` and log on. Top right press the 3 lines and select `Admin`. Go to API tab and press `Generate Master API Key`.
 
 Now go to the allianceauth folder and edit settings:
 
     nano /home/allianceserver/allianceauth/alliance_auth/settings.py
 
 Scroll down to the Discourse section and set the following:
- - `DISCOURSE_URL`: `discourse.mydomain.com`
+ - `DISCOURSE_URL`: `discourse.example.com`
  - `DISCOURSE_API_USERNAME`: the username of the admin account you generated the API key with
  - `DISCOURSE_API_KEY`: the key you just generated
 
 ### Configure SSO
 
-Navigate to `discourse.mydomain.com` and log in. Back to the admin site, scroll down to find SSO settings and set the following:
+Navigate to `discourse.example.com` and log in. Back to the admin site, scroll down to find SSO settings and set the following:
  - `enable_sso`: True
- - `sso_url`: `http://mydomain.com/discourse_sso`
+ - `sso_url`: `http://example.com/discourse_sso`
  - `sso_secret`: some secure key
 
 Save, now change settings.py and add the following:

docs/installation/services/ipboard3.md

@@ -14,7 +14,7 @@ IPBoard needs a database table. Log in to mysql and run:
 
 That’s all for SQL work. Control+D to close.
 
-Navigate to http://yourdomain.com/ipboard and proceed with the install. If it whines about permissions make sure to `chown` again. Point it at that database we just made, using the `allianceserver` MySQL user account from the full install.
+Navigate to http://example.com/ipboard and proceed with the install. If it whines about permissions make sure to `chown` again. Point it at that database we just made, using the `allianceserver` MySQL user account from the full install.
 
 Once you get everything installed we need to copy the api module folder
 
@@ -29,7 +29,7 @@ Enable the API by toggling the `XML-RPC Status` from `disabled` to `enabled` (re
 Copy the API key. Now edit your settings.py as follows:
 
  - IPBOARD_APIKEY is the key you just copied
- - IPBOARD_ENDPOINT is `http://yourdomain.com/ipboard/interface/board/index.php`
+ - IPBOARD_ENDPOINT is `http://example.com/ipboard/interface/board/index.php`
 
 Now enable IPBoard for Auth and/or Blue by editing the auth settings.
 

docs/installation/services/jacknife.md

@@ -32,14 +32,14 @@ Add the database user information:
 
 Change ownership of the directory: `sudo chown -R www-data:www-data ../eve-jacknife`
 
-Eve Jacknife can be served two ways: on its own subdomain (`jacknife.mydomain.com`) or as an alias (`mydomain.com/jacknife`)
+Eve Jacknife can be served two ways: on its own subdomain (`jacknife.example.com`) or as an alias (`example.com/jacknife`)
 
 ### Subdomain
 As its own subdomain, create a new apache config: `sudo nano /etc/apache2/sites-available/jacknife.conf` and enter the following:
 
     <VirtualHost *:80>
             DocumentRoot "/var/www/eve-jacknife"
-            ServerName jacknife.mydomain.com
+            ServerName jacknife.example.com
             <Directory "/var/www/eve-jacknife">
                     Require all granted
                     AllowOverride all
@@ -68,4 +68,4 @@ Enter your database password and press Check. If all the boxes come back green p
 
 ## Update Auth Settings
 
-Edit your aut settings file (`nano ~/allianceauth/alliance_auth/settings.py`) and replace `JACK_KNIFE_URL` with either `jacknife.mydomain.com/` or `mydomain.com/jacknife/` depending on your apache choice.
+Edit your aut settings file (`nano ~/allianceauth/alliance_auth/settings.py`) and replace `JACK_KNIFE_URL` with either `jacknife.example.com/` or `example.com/jacknife/` depending on your apache choice.

docs/installation/services/mumble.md

@@ -44,7 +44,7 @@ Now restart the server to see the changes reflected.
 
     sudo service mumble-server restart
 
-That’s it! Your server is ready to be connected to at yourdomain.com:64738
+That’s it! Your server is ready to be connected to at example.com:64738
 
 ## Configuring the Authenticator
 

docs/installation/services/openfire.md

@@ -29,11 +29,11 @@ Now install from the debian. Replace the filename with your file name (the last
     sudo dpkg -i openfire_4.1.1_all.deb
 
 ### Web Configuration
-The remainder of the setup occurs through Openfire’s web interface. Navigate to http://yourdomain.com:9090, or if you’re behind CloudFlare, go straight to your server’s IP:9090.
+The remainder of the setup occurs through Openfire’s web interface. Navigate to http://example.com:9090, or if you’re behind CloudFlare, go straight to your server’s IP:9090.
 
 Select your language. I sure hope it’s english if you’re reading this guide.
 
-Under Server Settings, set the Domain to `yourdomain.com` replacing it with your actual domain. Don’t touch the rest.
+Under Server Settings, set the Domain to `example.com` replacing it with your actual domain. Don’t touch the rest.
 
 Under Database Settings, select `Standard Database Connection`
 
@@ -78,7 +78,7 @@ Navigate to the `Server` tab, `Server Manager` subtab, and select `System Proper
    - Value: `True`
    - Do not encrypt this property value
  - Name: `plugin.broadcast.allowedUsers`
-   - Value: `broadcast@yourdomain.com`, replacing the domain name with yours
+   - Value: `broadcast@example.com`, replacing the domain name with yours
    - Do not encrypt this property value
 
 ### Group Chat

docs/installation/services/pathfinder.md

@@ -24,7 +24,7 @@ The logging and caching folders need to be created and have permission set. If u
 
 ## .htaccess Configuration
 
-In your `pathfinder` directory there are two `.htaccess` files. The default installation instructions want you to choose one for rewriting purposes, and these force you to www.pathfinder.mydomain.com. Personally I don't like that.
+In your `pathfinder` directory there are two `.htaccess` files. The default installation instructions want you to choose one for rewriting purposes, and these force you to www.pathfinder.example.com. Personally I don't like that.
 
 So we'll frankenstein our own. We'll use the HTTP one as a base: 
 
@@ -61,14 +61,14 @@ The default configuration should be fine in most cases. Edit all values with cau
 environment.ini
  - `SERVER` Should be changed to `PRODUCTION`
  - `BASE`  is the full filesystem path to the application root on your server. In our case, `/var/www/pathfinder/`
- - `URL`  Is the URL to your app (without a trailing slash). In our case, `http://pathfinder.mydomain.com`
+ - `URL`  Is the URL to your app (without a trailing slash). In our case, `http://pathfinder.example.com`
  - `DEBUG` sets the level of debugging (1,2 or 3) (check  /logs  for a more detail backtrace information) 
  - `DB_*` sets your DB connection information 
  - `SMTP_*`  are used to send out emails, you will need an SMTP server login to make this work. (not required)
  - `SSO_CCP_*` follow the [official docs](https://github.com/exodus4d/pathfinder/wiki/CREST)
 
 ## Database Setup
-This is done through the browser. Go to `pathfinder.yourdomain.com/setup` and see the [official docs](https://github.com/exodus4d/pathfinder/wiki/Database) for instructions.
+This is done through the browser. Go to `pathfinder.example.com/setup` and see the [official docs](https://github.com/exodus4d/pathfinder/wiki/Database) for instructions.
 
 ## Cron Jobs 
 Again the [official docs](https://github.com/exodus4d/pathfinder/wiki/Cronjob) do a good job here.

docs/installation/services/phpbb3.md

@@ -29,7 +29,7 @@ The web server needs read/write permission to this folder
     sudo chown -R www-data:www-data /var/www/forums
 
 ### Web Install
-Navigate to http://yourdomain.com/forums where you will be presented with an installer.
+Navigate to http://example.com/forums where you will be presented with an installer.
 
 Click on the `Install` tab.
 

docs/installation/services/smf.md

@@ -29,7 +29,7 @@ The web server needs read/write permission to this folder
     sudo chown -R www-data:www-data /var/www/forums
 
 ### Web Install
-Navigate to http://yourdomain.com/forums where you will be presented with an installer.
+Navigate to http://example.com/forums where you will be presented with an installer.
 
 Click on the `Install` tab.
 

docs/installation/services/teamspeak3.md

@@ -67,7 +67,7 @@ Click the URL provided to automatically connect to our server. It will prompt yo
 
 Now we need to make groups. AllianceAuth handles groups in teamspeak differently: instead of creating groups it creates an association between groups in TeamSpeak and groups in AllianceAuth. Go ahead and make the groups you want to associate with auth groups, keeping in mind multiple TeamSpeak groups can be associated with a single auth group.
 
-Navigate back to the AllianceAuth admin interface (yourdomain.com/admin) and under `Services`, select `Auth / TS Groups`. In the top-right corner click `Add`.
+Navigate back to the AllianceAuth admin interface (example.com/admin) and under `Services`, select `Auth / TS Groups`. In the top-right corner click `Add`.
 
 The dropdown box provides all auth groups. Select one and assign TeamSpeak groups from the panels below. If these panels are empty, wait a minute for the database update to run, or see the [troubleshooting section](#ts-group-models-not-populating-on-admin-site) below.