chore(release): prepare for v0.98.0

This commit is contained in:
Elian Doran
2025-08-17 22:46:16 +03:00
parent 87878dd6a7
commit 2e0f606a7a
14 changed files with 177 additions and 88 deletions

View File

@@ -1,6 +1,6 @@
<p>Trilium supports configuration via a file named <code>config.ini</code> and
environment variables. Please review the file named <a href="https://github.com/TriliumNext/Trilium/blob/develop/apps/server/src/assets/config-sample.ini">config-sample.ini</a> in
the <a href="https://github.com/TriliumNext/Trilium">Notes</a> repository
environment variables. Please review the file named <a href="https://github.com/TriliumNext/Trilium/blob/main/apps/server/src/assets/config-sample.ini">config-sample.ini</a> in
the <a href="https://github.com/TriliumNext/Trilium">Trilium</a> repository
to see what values are supported.</p>
<p>You can provide the same values via environment variables instead of the <code>config.ini</code> file,
and these environment variables use the following format:</p>

View File

@@ -231,23 +231,17 @@
first, then adds fuzzy matching when needed.</p>
<h3>How Progressive Search Works</h3>
<ol>
<li>
<p><strong>Phase 1 - Exact Matching</strong>: When you search, Trilium first
looks for exact matches of your search terms. This handles the vast majority
of searches (90%+) and returns results almost instantly.</p>
</li>
<li>
<p><strong>Phase 2 - Fuzzy Fallback</strong>: If Phase 1 doesn't find enough
high-quality results (fewer than 5 results with good relevance scores),
Trilium automatically adds fuzzy matching to find results with typos or
spelling variations.</p>
</li>
<li>
<p><strong>Result Ordering</strong>: Exact matches always appear before fuzzy
matches, regardless of individual scores. This ensures that when you search
for "project", notes containing the exact word "project" will appear before
notes containing similar words like "projects" or "projection".</p>
</li>
<li><strong>Phase 1 - Exact Matching</strong>: When you search, Trilium first
looks for exact matches of your search terms. This handles the vast majority
of searches (90%+) and returns results almost instantly.</li>
<li><strong>Phase 2 - Fuzzy Fallback</strong>: If Phase 1 doesn't find enough
high-quality results (fewer than 5 results with good relevance scores),
Trilium automatically adds fuzzy matching to find results with typos or
spelling variations.</li>
<li><strong>Result Ordering</strong>: Exact matches always appear before fuzzy
matches, regardless of individual scores. This ensures that when you search
for "project", notes containing the exact word "project" will appear before
notes containing similar words like "projects" or "projection".</li>
</ol>
<h3>Progressive Search Behavior</h3>
<ul>

View File

@@ -2,9 +2,9 @@
<p>There are two types of error logs, both of which are useful when reporting
bugs.</p>
<ul>
<li data-list-item-id="e5d891396e04bcb9d78ea10421e8ee6be"><a class="reference-link" href="#root/pOsGYCXsbNQG/BgmBlOIl72jZ/qzNzp9LYQyPT/_help_bnyigUA2UK7s">Backend (server) logs</a>
<li><a class="reference-link" href="#root/_help_bnyigUA2UK7s">Backend (server) logs</a>
</li>
<li data-list-item-id="e94ecb76c9af944e47bf8b5c5dabf027a"><a class="reference-link" href="#root/pOsGYCXsbNQG/BgmBlOIl72jZ/qzNzp9LYQyPT/_help_9yEHzMyFirZR">Frontend logs</a>
<li><a class="reference-link" href="#root/_help_9yEHzMyFirZR">Frontend logs</a>
</li>
</ul>
<h2>Providing sensitive data</h2>

View File

@@ -1,10 +1,10 @@
<h2>Accessing via the backend log</h2>
<p>In the&nbsp;<a class="reference-link" href="#root/pOsGYCXsbNQG/gh7bpGYxajRS/Vc8PjrjAGuOp/_help_x3i7MxGccDuM">Global menu</a>,
<p>In the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>,
go to Advanced → Show backend log</p>
<h2>Location on the disk</h2>
<p>Backend logs are stored on the file system. To find them, open the&nbsp;
<a
class="reference-link" href="#root/pOsGYCXsbNQG/Otzi9La2YAUX/_help_tAassRL4RSQL">Data directory</a>, go to the <code>log</code> subdirectory and find the
class="reference-link" href="#root/_help_tAassRL4RSQL">Data directory</a>, go to the <code>log</code> subdirectory and find the
latest log file, e.g. <code>trilium-2022-12-14.log</code>.&nbsp;</p>
<h2>Reporting backend bugs</h2>
<p>You can attach the whole file to the bug report (preferable) or open it
@@ -15,12 +15,18 @@
in order to reduce the space consumption.</p>
<p>It's possible to change the retention period by modifying the&nbsp;
<a
class="reference-link" href="#root/pOsGYCXsbNQG/tC7s2alapj8V/_help_Gzjqa934BdH4">Configuration (config.ini or environment variables)</a>&nbsp;via the <code>.ini</code> file:</p><pre><code class="language-text-x-trilium-auto">[Logging]
class="reference-link" href="#root/_help_Gzjqa934BdH4">Configuration (config.ini or environment variables)</a>&nbsp;via the <code>.ini</code> file:</p><pre><code class="language-text-x-trilium-auto">[Logging]
retentionDays=7</code></pre>
<p>Or via the environment variable <code>TRILIUM_LOGGING_RETENTION_DAYS</code>.</p>
<aside
class="admonition note">
<p>Special cases:</p>
<ul>
<li>Positive values indicate the number of days worth of logs to keep</li>
<li>A value of 0 results with the default value (90 days) to be used</li>
<li>Negative values (e.g. <code>-1</code>) result with all logs to be kept,
irrespective how ancient and numerous (and</li>
</ul>
<aside class="admonition note">
<p>If you set the retention days to a low number, you might notice that not
all the log files are being deleted. This is because a minimum number of
logs (7 at the time of writing) is maintained at all times.</p>
</aside>
</aside>

View File

@@ -5,9 +5,9 @@
console is cleared on app restart.</p>
<p>If that doesn't work, then:</p>
<ul>
<li data-list-item-id="e1f836ac8425c0d56072614c40c996bbd">in Trilium desktop app, go to top-left menu button -&gt; Advanced -&gt;
<li>in Trilium desktop app, go to top-left menu button -&gt; Advanced -&gt;
Open Dev Tools</li>
<li data-list-item-id="e8bd27605bedefe884b826a1899413a6d">In Firefox/Chrome right-click anywhere in the page and click Inspect:</li>
<li>In Firefox/Chrome right-click anywhere in the page and click Inspect:</li>
</ul>
<p>
<img src="Frontend logs_error-logs-f.png">