There could be a solution.

If you remember when i needed to just process part of a website, i asked 
for a switch. But then I realized it could be done with the site-dir= 
and build-dir= switches.

So let us say we needed to process a really large site, this could be 
done, if all pages were in memory, by running soupault multiple times, 
on sections of the website.

To be honest, i do like the current method, but it is about to be 
Shabbat where I am, so I will read your email in detail after Shabbat 
and respond more thoroughly.

I received the same results. But when
I went to my cellphone and switched it to
data the site showed up. A friend also
said it is working fine for her.

So i will figure out how to view it on my
laptops at some point. eventually talk to
our home internet provider.
---
Aoirthoir An Broc
The Trickster G-ds,
The G-ds oph Mischiephs.

On 2023-06-21 23:38, toastal wrote:

Is it just a temporary glitch on soupault.app?

---
Aoirthoir An Broc

>while "file" is always a path to a file.

I presume that is a lua file? In your example for tags from 
baturin.org it is a lua file? So does file = path.to.file
always mean a lua file?

Also is it the built in lua processor in Soupault?

Also is that still version 2.something?

>Lua index processors can inject new pages in the queue,
>so you can use that trick for many purposes, from pagination to 
>arbitrary taxonomies.

Question A1
====================

> when I added [file or lua_source], I'll fix that.

I see how to use a lua_source = """
   some code
"""

but how do we use a file? is it just lua_source = path.to.file or is it 
file = path.to.file

Question A2
====================

Question 1
====================

The reference manual heading "Ways to control index rendering" it says 
"There are three options you can define view rendering"then lists, 
index_item_template, index_template, index_processor, and [file or lua 
source]. Is that 4 options instead of 3?


Question 2
====================

When it comes to index.fields.something, is the something literally just

Excellent. I do not know how to help with making sure that all the
features are in the manual since  I do not know OCAML. But I would like
to help make an exhaustive manual with lots of detailed examples. How
that would go I do not know. But I am thinking something along the
lines of the depth that other manuals for systems like Joomla and
WordPress have, to show just how powerful the entire Soupault system
is.

Apologies that was actually from me, Aoirthoir.

I have altered the fish shell script add1tosoupault to use site/build
by default but to allow the options --site somedir --build somedir.

If you are in a child directory site and build will be presumed but if
you are not in a child directory, then all that will happen is soupault
will run with all of the arguments passed from the command line.. so in
that case --site and --build will not work, and the standard --site-dir
and --build-dir will be needed.

Basically if you run from a subdirectory of your site direcotry
(site/cats) than only that will be processed and site will be presumed
for the top level site and build for the top level build unless you
pass a change via --site and --build.

So now I have created a FISH SHELL script to manage this automatically
based on which directory you are in. The FISH SHELL script is named:

add1tosoupault

Since site and  build are common names I wanted to make sure that I did
not mess up some directory by mistake... so in all my soupault.toml
files I set

site = "shyte"

build = "phlushed"

Shyte is a common irish way of saying the other word but we say it with