<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Customization on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/customization/</link>
    <description>Recent content in Customization on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/customization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Working Through a Proxy</title>
      <link>https://docs.mitigator.ru/v26.04/en/install/advanced/proxy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/install/advanced/proxy/</guid>
      <description>Docker If docker.mitigator.ru is accessed through a proxy, you need to configure Docker.
On systems running systemd, you need to:
Create a drop-in to the Docker service, specifying the proxy in the environment (replace the details of connecting to the proxy with the current ones):
mkdir -p /etc/systemd/system/docker.service.d &amp;amp;&amp;amp; \ cat &amp;gt;/etc/systemd/system/docker.service.d/proxy.conf &amp;lt;&amp;lt;END [Service] Environment=HTTP_PROXY=http://user:password@proxy.local:1234 Environment=HTTPS_PROXY=http://user:password@proxy.local:1234 Environment=NO_PROXY=docker.local END Add proxy certificate to Docker&amp;rsquo;s trusted ones (/path/to/proxy.crt replace with the path to the proxy certificate):</description>
    </item>
    <item>
      <title>Custom TLS Certificate</title>
      <link>https://docs.mitigator.ru/v26.04/en/install/advanced/cert/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/install/advanced/cert/</guid>
      <description>To replace the self-signed certificate cert.crt with the key cert.key with your own, you need to mount the certificate and key:
Create a YML file named docker-compose.cert.yml with the following content:
services: nginx: volumes: - ./example.com.crt:/etc/nginx/cert.crt:ro - ./example.com.key:/etc/nginx/cert.key:ro Add docker-compose.cert.yml to the COMPOSE_FILE list in the .env file:
sed -i &amp;#39;s/^COMPOSE_FILE=\(.*\)$/COMPOSE_FILE=\1:docker-compose.cert.yml/&amp;#39; .env Restart the Nginx service:
docker-compose rm -s nginx &amp;amp;&amp;amp; docker-compose up -d nginx </description>
    </item>
    <item>
      <title>Syslog Sender Hostname</title>
      <link>https://docs.mitigator.ru/v26.04/en/install/advanced/syslog-host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/install/advanced/syslog-host/</guid>
      <description>To configure the syslog sender hostname:
Create a YML file named docker-compose.syslog.yml with the following content:
services: gateway: hostname: &amp;#34;desired sender name&amp;#34; Add docker-compose.syslog.yml to the COMPOSE_FILE list in the .env file:
sed -i &amp;#39;s/^COMPOSE_FILE=\(.*\)$/COMPOSE_FILE=\1:docker-compose.syslog.yml/&amp;#39; .env Restart MITIGATOR:
docker-compose down &amp;amp;&amp;amp; docker-compose up -d Related Content Custom TLS Certificate Working Through a Proxy Ansible Blocking IP on MITIGATOR with Nginx and Fail2ban Executing Scripts on Log Events Favicon Replacement MITIGATOR Installation System Preparation Virtual Machine Web Server Log Analyzer </description>
    </item>
    <item>
      <title>Additional Settings</title>
      <link>https://docs.mitigator.ru/v26.04/en/install/advanced/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/install/advanced/</guid>
      <description> Working Through a Proxy Custom TLS Certificate Syslog Sender Hostname Favicon Replacement </description>
    </item>
    <item>
      <title>Favicon Replacement</title>
      <link>https://docs.mitigator.ru/v26.04/en/install/advanced/custom-favicon/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/install/advanced/custom-favicon/</guid>
      <description>When working with multiple MITIGATOR clusters, it can be inconvenient to navigate through open browser tabs, as all of them display the same favicon, making it difficult to quickly locate the required cluster.
To replace the default favicons, follow these steps:
Prepare three PNG icons that meet the standard favicon sizes:
icon16.png – 16×16 pixels; icon32.png – 32×32 pixels; icon192.png – 192×192 pixels. You can either download a set of SVG icons from the MITIGATOR team and convert them to PNG at the required sizes, or use your own custom images.</description>
    </item>
  </channel>
</rss>