<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Settings on Quollix</title><link>https://quollix.org/docs/usage/settings/</link><description>Recent content in Settings on Quollix</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://quollix.org/docs/usage/settings/index.xml" rel="self" type="application/rss+xml"/><item><title>Server Host</title><link>https://quollix.org/docs/usage/settings/host/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/usage/settings/host/</guid><description>&lt;p&gt;The server host value is needed to access installed apps. For example, if you set the host to &lt;strong&gt;company.com&lt;/strong&gt; and click Open on the forgejo app on the &lt;strong&gt;Installed Apps&lt;/strong&gt; page, &lt;strong&gt;forgejo.company.com&lt;/strong&gt; will open in a new tab. For local testing, you can simply use &lt;strong&gt;localhost&lt;/strong&gt; as the host value.&lt;/p&gt;
&lt;p&gt;Note: This proxying requires that the domain (e.g. forgejo.company.com) resolves to the server where Quollix is installed, either via a DNS record or an entry in your system&amp;rsquo;s hosts file.&lt;/p&gt;</description></item><item><title>Certificate</title><link>https://quollix.org/docs/usage/settings/certificate/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/usage/settings/certificate/</guid><description>&lt;p&gt;There are multiple ways to operate certificates in Quollix.&lt;/p&gt;
&lt;h3 id="1-default-certificate"&gt;1) Default Certificate&lt;/h3&gt;
&lt;p&gt;By default, Quollix is available on port 443 via HTTPS using a universal self-signed wildcard certificate. This default certificate works for all domains or IP addresses through which you access Quollix and any host configured in the Settings. This option may be sufficient for test deployments or private LAN networks. However, for most real-world use cases, a valid, properly signed wildcard certificate is recommended.&lt;/p&gt;</description></item><item><title>Maintenance</title><link>https://quollix.org/docs/usage/settings/maintenance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/usage/settings/maintenance/</guid><description>&lt;p&gt;The features &lt;strong&gt;Automatic Updates&lt;/strong&gt; and &lt;strong&gt;Automatic Backups&lt;/strong&gt; are enabled by default and are handled by the Maintenance Agent in the background. The Maintenance Agent runs once a day.&lt;/p&gt;
&lt;p&gt;If both options are enabled, the Maintenance Agent compares the version of each locally installed app with the latest version in the App Store. If an update is available, a backup is created, then the update is applied. If the update fails, you can restore the previous version.&lt;/p&gt;</description></item><item><title>Remote Backup</title><link>https://quollix.org/docs/usage/settings/remote-backup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/usage/settings/remote-backup/</guid><description>&lt;p&gt;By default, when you create a backup of an app, Quollix will create a local backup of it. However, if remote backups are enabled, an additional remote backup is created and sent to an external SSH server.&lt;/p&gt;
&lt;div class="alert alert-warning" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note&lt;/div&gt;


We strongly recommend that you enable this feature. If your hard drive becomes irreversibly damaged, remote backup may be the only way to recover your data.
&lt;/div&gt;

&lt;p&gt;Quollix uses the &lt;strong&gt;restic&lt;/strong&gt; tool in the backend, which provides end-to-end encryption. This means that even if someone intercepts the traffic or gains access to the backup server, they cannot read your encrypted backup data.&lt;/p&gt;</description></item></channel></rss>