koziavin
00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
280 lines
26 KiB
HTML
280 lines
26 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Enable network encryption (TLS) in BRIX Enterprise</title>
|
||
<meta name="generator" content="Help+Manual" />
|
||
<meta name="keywords" content="" />
|
||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<meta name="description" content="BRIX Enterprise supports Transport Layer Security (TLS) 1.2+ for incoming and outgoing traffic. To automatically switch the application to work over the secure HTTPS protocol,..." />
|
||
<meta name="picture" content="" />
|
||
<meta property="og:type" content="website" />
|
||
<meta property="og:title" content="Full documentation for BRIX365 platform. Low-code developer guide. User guide. Admin guide. Developer guide." />
|
||
<meta property="og:url" content="https://brix365.com/en/help" />
|
||
<meta property="og:image" content="" />
|
||
<link rel="icon" href="favicon.png" type="image/png" />
|
||
|
||
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
|
||
<link rel="stylesheet" href="./jquery-ui.min.css" />
|
||
<link rel="stylesheet" href="default.css" />
|
||
<link rel="stylesheet" href="./search-yandex.css" />
|
||
<link rel="stylesheet" href="./article.css" />
|
||
<link rel="stylesheet" href="./glossary.css" />
|
||
<link rel="stylesheet" href="./theme.css" />
|
||
<script type="text/javascript" src="jquery.js"></script>
|
||
<script type="text/javascript" src="helpman_settings.js"></script>
|
||
<script type="text/javascript" src="helpman_topicinit.js"></script>
|
||
|
||
<script type="text/javascript" src="highlight.js"></script>
|
||
<script type="text/javascript">
|
||
$(document).ready(function(){highlight();});
|
||
</script>
|
||
</head>
|
||
|
||
<body>
|
||
|
||
<script>!function(e,t,c,n,r,a,m){e.ym=e.ym||function(){(e.ym.a=e.ym.a||[]).push(arguments)},e.ym.l=1*new Date;for(var s=0;s<document.scripts.length;s++)if(document.scripts[s].src===n)return;a=t.createElement(c),m=t.getElementsByTagName(c)[0],a.async=1,a.src=n,m.parentNode.insertBefore(a,m)}(window,document,"script","https://mc.yandex.ru/metrika/tag.js"),ym(83179930,"init",{clickmap:!0,trackLinks:!0,accurateTrackBounce:!0,webvisor:!0})</script><noscript><div><img alt=""src=https://mc.yandex.ru/watch/83179930 style=position:absolute;left:-9999px></div></noscript>
|
||
|
||
<header class="header elma-365">
|
||
<div class="container">
|
||
<a class="header__logo" href="https://brix365.com/en/help">
|
||
<img src="./logo-en.svg" alt="header logo">
|
||
</a>
|
||
<!-- <div class="hero__search-form" id="search-panel">
|
||
<form class="search-form" onsubmit="ym(83180416,'reachGoal','poisk')">
|
||
<label class="search-form__label">
|
||
<span id="reset-search" class="search__icon"></span>
|
||
<input class="search-form__input" type="text">
|
||
</label>
|
||
<input class="search-form__submit" type="submit" value="Submit">
|
||
</form>
|
||
</div> -->
|
||
|
||
<div class="hero__search-form" id="search-panel"> <form class="search-form"> <label class="search-form__label"> <span id="reset-search" class="search__icon"></span> <input class="search-form__input" type="text"> </label> <input class="search-form__submit" type="submit" value="Submit"> </form> </div>
|
||
<div class="hero__search">
|
||
<a href="#" id="search-icon" class="hero__search-icon">
|
||
<img src="search-icon-white.svg" alt="search string">
|
||
</a>
|
||
<a href="#" id="side-menu-icon" class="hero__side-icon">
|
||
<img src="side_menu.svg" alt="side menu">
|
||
</a>
|
||
</div>
|
||
<div class="header__navi">
|
||
|
||
<ul class="header__list"><li><span class="solution-select"><span class="solution-select__selected"></span><svg width="7" height="4" viewBox="0 0 7 4" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M1 1L3.5 3.5L6 1" stroke="white" stroke-linecap="round" stroke-linejoin="round"/></svg><ul class="solution-select__list"><li><a class="project-link" href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a class="project-link" href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a class="project-link" href="https://brix365.com/en/help/crm/crm_overview.html">CRM</a></li><li><a class="project-link" href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a class="project-link" href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li><li><a class="project-link" href="https://brix365.com/en/help/business_solutions/-elma365-store.html">Business Solutions</a></li></ul></span></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li><li><a href="https://tssdk.brix365.com/" target="_blank">SDK</a></li></ul>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
|
||
|
||
<main class="main container">
|
||
|
||
<aside class="sidebar" id="sidebar">
|
||
<div class="sidebar__header">
|
||
<a class="header__logo" href="https://brix365.com/en/help">
|
||
<img src="./logo-light-en.svg">
|
||
</a>
|
||
<span class="sidebar__close elma-365-close" id="close"></span>
|
||
</div>
|
||
<div class="sidebar__wrapper" id="side-menu">
|
||
|
||
</div>
|
||
</aside>
|
||
|
||
<article class="article" id="article">
|
||
<div class="article-inner">
|
||
<div class="content">
|
||
<header class="article__header">
|
||
<div class="article__bread" style="display:flex; gap:10px;">
|
||
<span id="subcategory" class="search-res__item-category search-res__item-category_subcategory subcategory article__badge"></span>
|
||
|
||
<div class="topic__breadcrumbs">
|
||
<p><a href="elma365-on-premises.html">BRIX On-Premises</a> > <a href="elma365-enterprise.html">BRIX On-Premises Enterprise</a> > Administering BRIX Enterprise / Enable network encryption (TLS) in BRIX Enterprise</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">Enable network encryption (TLS) in BRIX Enterprise</span></h1>
|
||
</div>
|
||
|
||
</header>
|
||
<section class="article__content">
|
||
<div class="scroll-top-inner">
|
||
<a href="#h1-article" class="scroll-top"></a>
|
||
</div>
|
||
<!-- Placeholder for topic body. -->
|
||
<p class="p_Normal">BRIX Enterprise supports Transport Layer Security (TLS) 1.2+ for incoming and outgoing traffic. To automatically switch the application to work over the secure HTTPS protocol, enable TLS encryption support.</p>
|
||
<p class="p_Normal">Enabling TLS for the BRIX application consists of three stages:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal"><a href="enable-tls-enterprise.html#preparation-of-secret-for-work-on-https" class="topiclink">Prepare a secret with a certificate for working via HTTPS</a>.</li><li value="2" class="p_Normal"><a href="enable-tls-enterprise.html#change-config-file" class="topiclink">Make changes to the configuration file</a>.</li><li value="3" class="p_Normal"><a href="enable-tls-enterprise.html#using-tls-for-elma365-enterprise" class="topiclink">Apply TLS parameters for BRIX Enterprise</a>.</li></ol>
|
||
<h2 class="p_Heading2"><a id="preparation-of-secret-for-work-on-https" class="hmanchor"></a><span class="f_Heading2">Step 1: Prepare a secret with a certificate for working via HTTPS</span></h2>
|
||
<p class="p_Normal">For details, see <a href="preparation-secret-with-certificate-https.html" class="topiclink">Create a secret with a certificate for HTTPS operation</a>.</p>
|
||
<h2 class="p_Heading2"><a id="change-config-file" class="hmanchor"></a><span class="f_Heading2">Step 2: Make changes to the configuration file values-elma365.yaml</span></h2>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Начало внимание</span></p>
|
||
<p class="p_Normal">Before editing the <code><b>values-elma365.yaml</b></code> file, make a backup copy of it, as incorrect parameter settings may cause BRIX application malfunction.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Конец внимание</span></p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">Fill put the configuration file <code><b>values-elma365.yaml</b></code> to enable TLS.</li></ol>
|
||
<p class="p_Normal">To enable encryption support, specify <code><b>true</b></code> in the parameter <code><b>global.ingress.onpremiseTls.enabled</b></code>. In this parameter, specify the name of the certificate for working via <code><b>https</b></code>, for example, <code><b>elma365-onpremise-tls</b></code>. The certificate must be issued for the domain name FQDN in the parameter <code><b>global.host</b></code>, through which the system will be accessible, for example <code><b>example.com</b></code>.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">global:</span><br />
|
||
<span class="f_CodeExample"> ## domain (FQDN) or ip address where the system is available</span><br />
|
||
<span class="f_CodeExample"> host: 'example.com'</span><br />
|
||
<span class="f_CodeExample"> ingress:</span><br />
|
||
<span class="f_CodeExample"> ## enable host in ingress (value taken from host)</span><br />
|
||
<span class="f_CodeExample"> ## for installed s3 minio via elma365-dbs charts, specify in the minio block</span><br />
|
||
<span class="f_CodeExample"> ## the value in the hosts parameter in the values-dbs.yaml file</span><br />
|
||
<span class="f_CodeExample"> hostEnabled: </span><span class="f_CodeExample" style="font-weight: bold;">false</span><br />
|
||
<span class="f_CodeExample"> onpremiseTls:</span><br />
|
||
<span class="f_CodeExample"> ## enable https</span><br />
|
||
<span class="f_CodeExample"> enabled: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><br />
|
||
<span class="f_CodeExample"> ## name of the secret with certificates for https</span><br />
|
||
<span class="f_CodeExample"> secret: "elma365-onpremise-tls"</span></p>
|
||
<p class="p_Normal"><a class="dropdown-toggle" style="font-style: normal; font-weight: normal; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A1')">Filling in the root CA parameters for configuring trust for a custom CA certificate</a></p>
|
||
<div id="TOGGLE0186A1" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal"> <br />
|
||
You can configure trust support if you used a self-signed certificate with OpenSSL or a certificate issued by a local certificate authority when creating a secret for HTTPS operation. This can be done in two ways:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Using the Kyverno add-on module. Kyverno allows you to automatically add a volume containing custom CA certificates to containers with a specific label.</li><li class="p_Normal">In the BRIX Helm chart:</li></ul>
|
||
<ol style="list-style-type:lower-roman"><ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">In the namespace where the BRIX application is installed, create a ConfigMap from the CA certificate file:</li></ol></li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">kubectl create configmap elma365-onpremise-ca \</span><br />
|
||
<span class="f_CodeExample">--from-file=path/to/rootCA [-n namespace]</span></p>
|
||
<ol style="list-style-type:lower-roman"><ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">In the configuration file <code><b>values-elma365.yaml</b></code>, specify the following values:</li></ol></li></ol>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:circle"><ul style="list-style-type:square"><ul style="list-style-type:disc">
|
||
<li class="p_Normal"><code><b>global.ingress.onpremiseTls.enabledCA</b></code> — Enable the use of a custom CA root certificate by BRIX. Set to <code><b>true</b></code>.</li><li class="p_Normal"><code><b>global.ingress.onpremiseTls.configCA</b></code> — The name of the previously created ConfigMap. In this article, it is named <code><b>elma365-onpremise-ca</b></code>.</li></ul></li></ul></li></ul></li></ul>
|
||
<p class="p_Normal">File example:</p>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">global:</span><br />
|
||
<span class="f_CodeExample"> ...</span><br />
|
||
<span class="f_CodeExample"> ingress:</span><br />
|
||
<span class="f_CodeExample"> ## </span><span class="f_CodeExample">enable host in ingress (value taken from host</span><span class="f_CodeExample">)</span><br />
|
||
<span class="f_CodeExample"> ## </span><span class="f_CodeExample">for installed s3 minio via elma365-dbs charts, specify minio in the block</span><br />
|
||
<span class="f_CodeExample"> ## </span><span class="f_CodeExample">the value in the hosts parameter in the values-dbs.yaml file</span><br />
|
||
<span class="f_CodeExample"> hostEnabled: false</span><br />
|
||
<span class="f_CodeExample"> onpremiseTls:</span><br />
|
||
<span class="f_CodeExample"> ## enable https</span><br />
|
||
<span class="f_CodeExample"> enabled: true</span><br />
|
||
<span class="f_CodeExample"> ## </span><span class="f_CodeExample">name of the secret with certificates for</span><span class="f_CodeExample"> https</span><br />
|
||
<span class="f_CodeExample"> secret: "elma365-onpremise-tls"</span><br />
|
||
<span class="f_CodeExample"> ## </span><span class="f_CodeExample">enable certificate for root CA for working with https using a self-signed certificate</span><br />
|
||
<span class="f_CodeExample"> enabledCA: true</span><br />
|
||
<span class="f_CodeExample"> ## </span><span class="f_CodeExample">name of the configmap with the root CA certificate for working with https using a self-signed certificate</span><br />
|
||
<span class="f_CodeExample"> configCA: "elma365-onpremise-ca"</span></p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Начало внимание</span></p>
|
||
<p class="p_Normal">Before applying TLS parameters for the BRIX application, ensure that the S3 file storage operates over the HTTPS protocol (uses TLS encryption).</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Конец внимание</span></p>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" class="p_Normal" style="line-height: 1.20;">Specify in the connection parameters that the S3 storage server uses TLS encryption. To do this, set <code><b>true</b></code> in the <code><b>db.s3.ssl.enabled</b></code> parameter.</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">...</span><br />
|
||
<span class="f_CodeExample">db:</span><br />
|
||
<span class="f_CodeExample"> ... </span><br />
|
||
<span class="f_CodeExample"> ## connections settings for S3 file storage</span><br />
|
||
<span class="f_CodeExample"> s3:</span><br />
|
||
<span class="f_CodeExample"> method: PUT</span><br />
|
||
<span class="f_CodeExample"> accesskeyid: PZSF73JG72Ksd955JKU1HIA</span><br />
|
||
<span class="f_CodeExample"> secretaccesskey: aFDkj28Jbs2JKbnvJH678MNwiz88zKjsuNBHHs</span><br />
|
||
<span class="f_CodeExample"> bucket: s3elma365</span><br />
|
||
<span class="f_CodeExample"> backend:</span><br />
|
||
<span class="f_CodeExample"> address: example.com</span><br />
|
||
<span class="f_CodeExample"> region: us-east-1</span><br />
|
||
<span class="f_CodeExample"> ssl:</span><br />
|
||
<span class="f_CodeExample"> enabled: "true"</span><br />
|
||
<span class="f_CodeExample">...</span></p>
|
||
<h2 class="p_Heading2"><a id="using-tls-for-elma365-enterprise" class="hmanchor"></a><span class="f_Heading2">Step 3: Apply TLS parameters for BRIX Enterprise</span></h2>
|
||
<p class="p_Normal">You can update parameters for BRIX Enterprise in two ways: online and <a href="enable-tls-enterprise.html#update-offline" class="topiclink">offline</a>.</p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Update parameters online</span></h3>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">Determine the chart version with which the BRIX application was installed or updated:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">helm show chart elma365/elma365</span></p>
|
||
<p class="p_Normal">Example of command execution:</p>
|
||
<p class="p_Normal"><img alt="enable-tls-enterprise-1" title="enable-tls-enterprise-1" width="842" height="64" style="margin:0;width:842px;height:64px;border:none" src="enable-tls-enterprise-1.png"/></p>
|
||
<p class="p_Normal">After the command execution, you see the chart version information in the <code><b>APP VERSION</b></code> string. Save this value for the next step.</p>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" class="p_Normal">Update the parameters using the <code><b>values-elma365.yaml</b></code> configuration file. To do this, execute the following command specifying the installed chart version for the <code><b>--version</b></code> flag instead of <code><b><elma365-chart-version></b></code>:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">helm upgrade --install elma365 elma365/elma365 -f values-elma365.yaml --version <elma365-chart-version> --timeout=30m --wait [-n namespace]</span></p>
|
||
<h3 class="p_Heading3"><a id="update-offline" class="hmanchor"></a><span class="f_Heading3">Update parameters offline</span></h3>
|
||
<p class="p_Normal">Navigate to the directory with the downloaded BRIX chart and execute the command:</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">helm upgrade --install elma365 ./elma365 -f values-elma365.yaml --timeout=30m --wait [-n namespace]</span></p>
|
||
<p class="p_Normal">It takes about 10-30 minutes to update the parameters. Wait for it to complete.</p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="enable-portable-services.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">enable-portable-services.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="autoscaling-service-enterprise.html">
|
||
<span class="bottom-nav__link">autoscaling-service-enterprise.html</span> <span
|
||
class="bottom-nav__arrow bottom-nav__arrow--next"></span>
|
||
</a>
|
||
|
||
</div>
|
||
<!-- добавляет на страницу строку блок Была ли статья полезной? -->
|
||
<div class="feedback" id="feedback"><div class="feedback-help"><span><b>Was this helpful?</b></span><form action="" method="POST" class="feedback-form" id="feedback-form"><div class="feedback__popup feedback__popup-response" id="feedback__popup_thx" style="display: none;">Thanks for your feedback!</div><div class="feedback__popup" id="feedback__popup_why" style="display: none;"><div class="feedback__popup-header">Please specify why:</div><input type="radio" name="category" id="bad_recommendation" value="bad_recommendation"><label for="bad_recommendation">Recommendations did not help me</label><input type="radio" name="category" id="difficult_text" value="difficult_text"><label for="difficult_text">Article is hard to understand</label><input type="radio" name="category" id="no_answer" value="no_answer"><label for="no_answer">Didn`t answer my question</label><input type="radio" name="category" id="bad_header" value="bad_header"><label for="bad_header">Content does not match the topic</label><input type="radio" name="category" id="other_reason" value="other_reason"><label for="other_reason">Other</label></div><div class="feedback__popup" id="feedback__popup-other" style="display: none;"><div class="feedback__popup-header">How we can improve it?</div><textarea class="feedback__textarea" name="other" id=""></textarea><input type="submit" class="feedback__other-btn" value="Submit"></div><div class="feedback-form__btn-group"><input type="radio" name="useful" id="feedback__useful_yes" value="true"><label for="feedback__useful_yes"><img src="like.svg" class="small-img" alt="like"><spanclass="feedback-form__btn-group_yes-btn">Yes</spanclass="feedback-form__btn-group_yes-btn"></label><input type="radio" name="useful" id="feedback__useful_no" value="false"><label for="feedback__useful_no"><img src="dislike.svg" class="small-img" alt="dislike"><spanclass="feedback-form__btn-group_no-btn">No</spanclass="feedback-form__btn-group_no-btn"></label></div><select name="category"><option disabled="">Please specify why</option><option value="bad_recommendation" selected="">Recommendations did not help me</option><option value="difficult_text">Article is hard to understand</option><option value="no_answer">Didn`t answer my question</option><option value="bad_header">Content does not match the topic</option><option value="other_reason">Other</option></select><input type="submit"></form></div><div class="found_typo"><p style="margin: 0px; margin-top: 16px !important;"><span><b>Found a typo?</b></span> Select it and press <i>Ctrl+Enter</i> to send us feedback</p></div></div>
|
||
|
||
</section>
|
||
</div>
|
||
<aside class="article__sidebar" style="display:none">
|
||
<input type="checkbox" />
|
||
<div class="article__arrow"></div>
|
||
<div class="table-of-contents elma365-right" id="toc2Content">
|
||
<h3 class="h3-toc">In this topic</h3>
|
||
<nav id="toc2"></nav>
|
||
</div>
|
||
</aside>
|
||
</div>
|
||
</article>
|
||
</main>
|
||
<footer class="footer">
|
||
<div class="footer-container">
|
||
<div class="footer-mobile">
|
||
|
||
<ul class="footer-mobile__list"><li><a href="https://brix365.com/en/" target="_blank">BRIX</a></li><li><a href="https://tssdk.brix365.com/en/latest/" target="_blank">SDK</a></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li></ul><ul class="footer-mobile__list"><li><a href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li></ul>
|
||
|
||
|
||
</div>
|
||
<div class="footer-wrap">
|
||
|
||
<div><span class="mobile-question-popup">Send feedback</span><form method="POST" action class="question__popup question-xs" id="question__popup"><div class="question-wrap"><span class="close"></span><span class="title">Ask a question</span><label for="help_question" style="display: none;"></label><textarea name="help_question" id="help_question"></textarea><input type="submit" value="Send"></div></form><div class="hidden fade-in question-success-xs">Sent</div></div>
|
||
|
||
<div class="footer-flex-b">
|
||
<span class="footer-copy">© 2025 BRIX</span>
|
||
<ul class="footer-list">
|
||
|
||
<li class="footer-item">
|
||
<a href="#" class="arrow-top" style="display: block;"></a>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
</footer>
|
||
<iframe name="hmnavigation" style="display:none!important"></iframe>
|
||
<script src="./jquery-ui.js"></script>
|
||
<!--script src="//cdn.jsdelivr.net/npm/featherlight@1.7.14/release/featherlight.min.js" type="text/javascript" charset="utf-8"></script-->
|
||
<script src="./jquery.tocify.min.js"></script>
|
||
<script src="./TypoReporter.min.js"></script>
|
||
<script src="./google-search.js"></script>
|
||
<script src="./main.js"></script>
|
||
<script type="text/javascript">
|
||
HMInitToggle('TOGGLE0186A1','hm.type','dropdown','hm.state','0');
|
||
</script>
|
||
</body>
|
||
|
||
</html>
|