There are many options you can chnage into the file passed as first argument of application. File is recognized when launching sgrun.py with option --build and a directory name, the name is dirname/site/site.conf, and can be created with option --createconf
Date when this file is created.
Name, as you like.
Path of the site on the server: needed for security options.
If this option is set to ok, when application finds a processed file like a php file, it creates an html file that contains a redirecting script
Languages used in the site, first is default.
Set a directory where graphics files are backupped before editing. If parameter is not set, any file will be saved. In the choosed directory, if there is alread a file with the same name, new file will be name with a number at the end (for example, name.jpg and name.jpg.1)
Directories where documents are stored
A command line, where the position of the actual file name is defined like in Python templates (ie $file or ${file}), that is executed on the produced final html file.
A command line, where the position of the actual text file name is defined like in Python templates (ie $file or ${file}), that is executed on the text file, only the first time that is read, when def :> date is still not present.
The destination directory, where final site is created.
Name of the file where
The list of directories that are not showed in the map of the site. Names are divided by a pipe.
If a directory is configured with this instruction, a file .txt and a jpg image is considered to be a new post, and will be moved to current date directory in the posts tree.
Set the directory where a kind of permalinks will be stored. Default is l. Files are simply a slim html file with either html and javascript redirections, with the meaning of give a short and not subject to change link.
Set the directory where posts will be stored. Default is posts
Directory where temporary files are stored.
The extensions of the image files, with the point excluded. So extensions are only the literal part at the right of the file name, divided by a pipe ("|")
Jpg compression (a number from 1 to 100, generally greater than 70) used when resizing or creating thumbnails. Default is 95.
Resolution in dpi for images. Should be at least greater than 90, resolution for old monitors. Default is 200.
Dimensions in pixels of thumbnails, default is 150.
The x dimension (width) of the resized images into galleries, default is 800 pixels.
The x dimension (width) of the resized images into documents directories, default is 400 pixels.
The x dimension of images automatically added to posts, in pixels. Default is 400 pixels.
With this ok, tags in images will be striped
This value is used to decide if html pages containing lists of categories and tags will be created. Default is no.
With this as ok, files that are in the duplicated extensions are copied on the destination, in the other way they are symlinked. Default is ok, at least until application will be tested on Windows. The file extensions that are affected, tipically images or archives, is set in setduplicatefileextensions
Files that should be symlinked rather than copied.
Name of the default file showed when opening directory, generally (also default) index.
Default name for password file.
When an huge site is processed, remember that I would use g.static via cron, times grow. It's not so dramatic for me (processing takes 6 second on a slow i7 notebook with a slow hard disk, and 3 seconds on a g3220 machine with a ssd disc, with 1500 pages), but due most part of work is processing pages, and not composing indexes or other stuff, it can be an help to set this value to a small value, due it means the max age in days of the files: default is 0, and all files will be processed.
Default extensios
When passed with ok, default is No, it will look for a /site/replace.conf file that will contains all items to be replaced in the new processed text files. An example: you would change all your abc with aaabbbccc in your text, you must put a line in this file with the double points in the middle: abc:aaabbbccc
For 'salt' used hashing passwords (for private directories): if you think to secure relatively the process you can set in action file the string, or put in it the value 'random' or simply nothing, to make prefix always changing. Back consideration is that you need to upload always the hashed password files. This is not generally a problem, due they are often small files.
Creates a map of the site, addressed at /site/map/
Show or hide most of the messages during execution. Default is ok.
Name of the author of the rss feed: it must be set only if rss is used, obviously.
Description for rss feed
The length of the list in the rss.xml file about last changes in the site. Default is 10.
Names, of directories or files, that must not be added to the rss.xml file.
At the end of operations, run the procedure that create a /posts/rss.xml file, a feed of the blog part of site in RSS 2.0 format. Only ok is useful for one site, due it's enabling the creation of feed.
A directory that will be access-controlled on server, if a file (set by setpasswdfile, default is pw.pw) with a list of user and password is present.
This directive is important to set extensions or file names that should be deployed, so you need to put them near the beginning of the actions file.
If this value is set, a log file will be created.
The name of the file used in a directory to define the security access options. Default, if it is not set, is pw.pw.
The title for pages that are used as indexes.
Makes a simple check on file names, principally to avoid use of apostrophe and other characters or word that urls names don't like. Command must be inserted after setting of the start directory, and, if used, after setting of new post directory.
Removes all directories in the final destination dir that aren't also in the starting directory (they're renamed or deleted), in order to keep clear the final tree.
This deletes, in the start directory, all files that contains in the name the [part of file name]. This is case sensitive, and can be placed everywhere in the action file, but generally should be at the beginning (it was born to remove some files that made conflicts with synchronization services). You can also use more than one instruction in an action file.
The command that will be executed to obtain the row user:password_hash for the .htpassword file in a site directory. Default is htpwasswd -nb $user $w
Last update: 2024-08-21 18:32