thalassa/doc/generic_files.html
2026-03-19 06:23:52 +05:00

71 lines
3.8 KiB
HTML

<?xml version="1.0" encoding="us-ascii"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<link type="text/CSS" rel="stylesheet" href="style.css" />
<link type="image/x-icon" rel="shortcut icon" href="favicon.png" />
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>Thalassa CMS official documentation</title>
</head><body>
<div class="theheader">
<a href="index.html"><img src="logo.png"
alt="thalassa cms logo" class="logo" /></a>
<h1><a href="index.html">Thalassa CMS official documentation</a></h1>
</div>
<div class="clear_both"></div>
<div class="navbar" id="uppernavbar"> <a href="verbatim_publishing.html#uppernavbar" title="previous" class="navlnk">&lArr;</a> &nbsp;&nbsp; <a href="userdoc.html#generic_files" title="up" class="navlnk">&uArr;</a> &nbsp;&nbsp; <a href="page_sets.html#uppernavbar" title="next" class="navlnk">&rArr;</a> </div>
<div class="page_content">
<h1 class="page_title"><a href="">Generic files (outside the web tree)</a></h1>
<div class="page_body">
<p>Generic files are perhaps the simplest kind of objects generated by
Thalassa: actually, it's just an (almost arbitrary) text file placed
wherever you want, not within your site's tree (for files within the tree,
the <a href="simple_pages.html#page_section">page section group</a> should
be used). These files are not intended to be HTML pages, their real
purpose is to communicate with third-party software, e.g., you can create a
configuration file for something external, or even a shell script (well,
think carefully before you do). However, you <strong>can</strong> generate
an HTML page this way if you really want so. Well, if you do, please
contact the authors of Thalassa and share your experience, as we've got no
idea why the heck anyone might need to create web pages in this manner.
</p>
<p>To create a generic file, use an ini file section
<code>[genfile&nbsp;<em>NAME</em>]</code>. Three parameters are
recognized: <code>path</code>, <code>content</code> and <code>chmod</code>.
</p>
<p>The <code>path</code> parameter is just a file name, either absolute or a
relative (to the working directory of Thalassa, <strong>not</strong> to your
site's root!). The value defaults to the <em>NAME</em> of the section.
Please note that if you do specify this parameter, its value is passed
throught the macroprocessor (primarily to give one access to the
<a href="general_configuration.html#options">options</a>), but if you omit
the parameter, the default value (<em>NAME</em>) is used without any
processing.
</p>
<p>The <code>content</code> parameter's value defines what to write to that
file; the exact content of the file will be the macroprocessing result of
the value.
</p>
<p>As usual (see <a href="simple_pages.html#chmod">here</a> and
<a href="verbatim_publishing.html#chmod">here</a>), the <code>chmod</code>
parameter must contain an octal number specifying the access mode to set
for the file. If this parameter is not specified, no <code>fchmod</code>
call will be performed, so the file will have default permissions as
determined by your active umask. The value of this parameter is
<strong>not</strong> passed through the macroprocessor.
</p>
</div>
</div>
<div class="navbar" id="bottomnavbar"> <a href="verbatim_publishing.html#bottomnavbar" title="previous" class="navlnk">&lArr;</a> &nbsp;&nbsp; <a href="userdoc.html#generic_files" title="up" class="navlnk">&uArr;</a> &nbsp;&nbsp; <a href="page_sets.html#bottomnavbar" title="next" class="navlnk">&rArr;</a> </div>
<div class="bottomref"><a href="map.html">site map</a></div>
<div class="clear_both"></div>
<div class="thefooter">
<p>&copy; Andrey Vikt. Stolyarov, 2023-2026</p>
</div>
</body></html>