Kitten is now using the new versioning/deployments system hosted on https://kittens.small-web.org
This is going to allow us to handle automatic updates of Small Web places rather elegantly.
Installation is also now much faster.
You can find out more about Kitten at https://codeberg.org/kitten/app#kitten
Known issue: commit links on the Kittens site are 404ing right now. I just opened an issue to see if @forgejo can add support for 6-digit git hashes*
PS. Like everything else I do, the Kittens site¹ is free and open source and written in Kitten itself.
So if you’d like to see a real-world example of simple site created in Kitten, head over to:
https://codeberg.org/kitten/kittens.small-web.org
What you’ll likely notice is just how little code there is for an app with a database + authentication that handles uploads.
(I also just added a View Source link to the bottom of the Kittens site.)
Also, if you are looking at the code, notice how I’m persisting and retrieving custom JavaScript objects from the database and generally interacting with the database as I would with any JavaScript object.
e.g., https://codeberg.org/kitten/kittens.small-web.org/src/branch/main/upload.post.js#L80
That’s thanks to the built-in JavaScript Database (JSDB) that Kitten uses:
https://codeberg.org/small-tech/jsdb#javascript-database-jsdb
To see how the custom classes are created, see the database app module:
e.g., https://codeberg.org/kitten/kittens.small-web.org/src/branch/main/app_modules/database
Just published a userstyle for the Stylus Firefox extension¹ that removes the ambiguous Unicode character warnings on @Codeberg code listings (for example, when you use proper curly quotes in comments and strings, etc.)
Should work with any @forgejo install if you tweak the domain it pertains to.
https://userstyles.world/style/13057/remove-ambiguous-character-warnings-on-codeberg
@aral @Codeberg @forgejo it's possible this is related to CVEs like this one: https://blog.rust-lang.org/2021/11/01/cve-2021-42574.html
But, it's certainly annoying to see warnings that a compiler/interpreter will trip over anyway (e.g. quote symbols), because that's what CI is for
Really should only see warnings/errors for text that is both valid to the compiler, and also conceals code from human review (per the CVE)
@jokeyrhyme In this case, we ’re seeing warnings for curly quotes in comments and strings ;)