ipng/ipng.ch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add note on Skylight and S3
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Pim van Pelt
2025-08-10 17:50:05 +02:00
parent d9066aa241
commit f4ed332b18
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/articles/2025-08-10-ctlog-2.md
View File

@@ -629,6 +629,10 @@ current write-load (which is about 250/s).
precaution - but also using ports in those prefixes (other than the standard 443) rendered precaution - but also using ports in those prefixes (other than the standard 443) rendered
Sunlight and Skylight unusable for me. Sunlight and Skylight unusable for me.
* Skylight only serves from local directory, it does not have support for S3. For operators using S3,
an alternative could be to use NGINX in the serving path, similar to TesseraCT. Skylight does have
a few things to teach me though, notably on proper compression, content type and other headers.
* TesseraCT does not have a configuration file, and will run exactly one log per binary * TesseraCT does not have a configuration file, and will run exactly one log per binary
instance. It uses flags to construct the environment, and is much more forgiving for creative instance. It uses flags to construct the environment, and is much more forgiving for creative
`origin` (log name), and submission- and monitoring URLs. It's happy to use regular 'http://' `origin` (log name), and submission- and monitoring URLs. It's happy to use regular 'http://'