Hi Beau,

Thanks, I'll add it.

One oddity, by the way: selecting text on your page is challenging 
because the selected text background color is the same as the background 
color.
Please adjust your CSS to make selected text visible.

On 11/9/23 21:24, beau@beauhilton.com wrote:
> Quite a belated response, apologies. I didn't see your email back until just now,
> as I'm making some substantial updates to the site.
>
>

Hi Raphaël,

This is an interesting question. The usual way to skip a draft page is 
to use the `settings.ignore_extentions` option,
but that's purely static and won't work for your idea.

What could work is the save hook 
(https://soupault.app/reference-manual/#hooks-save).
You could check the date from the index entry there and just do nothing 
if the date is in the future.
There's https://soupault.app/reference-manual/#Date.to_timestamp to 
convert dates to UNIX timestamps for easy comparison,
ignoring the issue of timezones (I intentionally decided not to open 
that can of worms ;).

Hey,

 >why are index views limited to index.* pages?

The practical answer is that you can make index data available to all 
pages with `index.index_first = true`
(see 
https://soupault.app/reference-manual/#making-index-data-available-to-every-page)

Now a longer answer as to why it's not the default... the reason why 
index data is only available to index pages by default
is that I wanted soupault to be able to handle websites that are larger 
than the available amount of memory.

Hi Pradeep,

There's no option to ignore a list of directories now, only an option to 
ignore specific file extensions (`settings.ignore_extensions`).
It's pretty easy to add, though, I just haven't had a use case for it 
and never thought about it before
I'll add it in the next release.

If you want to test it when I add it but don't have an OCaml setup,
I can send you a preview build if you tell me what OS you use.

On 10/9/23 17:51, Pradeep Kishore Gowda wrote:
> Specifically, I use `Obsidian.md` which saves the .obsidian directory inside the site directory and all the plugins (node_modules) inside. This considerably increases the processing time by processing all those extra directories.
>

Ok, I think I know where the root cause lies. Here's a copy of the 
investigation notes that I sent to Quod9 in my blocklist removal request.

Dear Quod9 team,

soupault.app., the domain of my project, recently got blocked. I 
appreciate your effort to keep the users safe, but in this case it's a 
false positive.

You can view the website on Netlify: https://soupault.netlify.app
It's an open-source project with a four year history of releases: 
https://github.com/PataphysicalSociety/soupault — a static site 
generator framework that is based on HTML element tree rewriting (as 
opposed to Jekyll or Hugo that treat HTML as an opaque format).

Hi Aoirthoir and toastal,

That Quod9 stuff is a complete surprise to me.
It looks like the ban is spreading — it worked with 8.8.8.8 yesterday 
but today it doesn't.

I've registered soupault.net in case it's the .app domain that caused 
the problem.
There's a backlash against those Google domains that resemble 
commonly-used file extensions (.app, .mov, and now .zip)
because malicious actors often use them to create deceptive links.

However, I'm going to wait for a response from Quad9 before setting up 
A/AAAA records

 >png = "./filters/process_png '{{source_file_path}}' 
'{{target_dir}}/{{source_file_name}}'

Yes, the problem is that you know that the output path is 
'{{target_dir}}/{{source_file_name}}' but to soupault that command is 
opaque.
To make automatic caching possible, the output path needs to be made 
explicit.

One compatible syntax I can think of it like this:

[asset_processors]
   png = { target_path_template = 
"{{target_dir}}/{{source_file_name}}.css", command_template = "sass

 >do you have any plans to add caching for asset_processors?

That's complicated. With pages, it's simple since the output path is 
decided by soupault itself.
With asset processors, the user specifies a template for generating a 
complete command.
That is required to accommodate commands with peculiar syntax that makes 
it impossible to just append the output file path,
and to allow original and processed files to have different extensions.
However, it also means that soupault doesn't actually know the output 
path and cannot replicate what  the user-given command would do.

I agree that it would be nice to cache asset processor outputs but it's 
going to require syntax design changes.

Thanks for testing it! I'm planning to make a release early next week then.

On 1/26/23 10:03, nik gaffney wrote:
>
> Thanks! that fixed it.
>
> On 2023-01-26 03:49, Daniil Baturin wrote:
>> Hi Nik,
>>
>> I fixed the problem. It was a funny case of missing parentheses that 
>> made bits of actual logic interpreted
>> as a part of a debug log function body: 
>> https://codeberg.org/PataphysicalSociety/soupault/commit/599f0f921c32b0d5daf41e5ba4fa369f55acb15c
>>

Hi Nik,

I fixed the problem. It was a funny case of missing parentheses that 
made bits of actual logic interpreted
as a part of a debug log function body: 
https://codeberg.org/PataphysicalSociety/soupault/commit/599f0f921c32b0d5daf41e5ba4fa369f55acb15c

Could you try building again and let me know if it works for you without 
debug now?

On 1/25/23 12:49, nik gaffney wrote:
>
> I took a closer look and managed to confuse myself by setting 
> debug=true which appears to avoid the problem.