tomd

When I'm building apps that use LLMs I'm often looking up prices from the providers' websites, sometimes copying and pasting them into prompts ('calculate and display the costs for this model using this screenshot'). I'd rather tell Claude Code 'use toktab.com to get the current prices for gemini-3-flash-preview'. And now I can! This site is built every night from the open source pricing data from LiteLLM - https://github.com/BerriAI/litellm - which was the most comprehensive data I could find. I think the main weakness is lack of fuzzy searching, which is hard to achieve with a statically generated site, but I'm very open to suggestions.

It's there now

> I'm unsure whether SQLite's extension interface is flexible enough to support this.

I think it is, if I've understood your requirements correctly. e.g. from the datasette-faiss docs:

  with related as (
    select value from json_each(
      faiss_search(
        'intranet',
        'embeddings',
        (select embedding from embeddings where id = :id),
        5
      )
    )
  )
  select id, title from articles, related
  where id = value

You might be interested in https://datasette.io/plugins/datasette-faiss, which I'm using alongside openai-to-sqlite for similarity search of embeddings, following @simonw's excellent instructions at https://simonwillison.net/2023/Jan/13/semantic-search-answer...

> It takes a while to configure a persistent database, redis, and storage on Heroku

Really? Have you actually tried this? In my experience Heroku couldn't make it any easier. You can provision a database in 60 seconds, from a Deploy to Heroku button in your Github README, or in the lovely dashboard, or on the CLI, or with two lines in heroku.yml.

We're a heavy Gitlab user and I'm a big fan of Gitlab's typically transparent communications style, but this article reflects really badly on you. I think you should take it down.

Daniele Procida - the author of this framework - is giving a talk about it at the start of Wagtail's documentation sprint on Thursday:

https://wagtail.io/docs-sprint-details

Do join if you're interested, even if it's just to hear Daniele's talk.

> there is no easy way to manage secrets with Cloud Run

See https://cloud.google.com/secret-manager/

I recommend this community-maintained FAQ on Cloud Run:

https://github.com/ahmetb/cloud-run-faq

Wagtail - https://wagtail.io - is the most popular Python CMS. It runs sites for NASA, Google, Mozilla, NHS.uk. It's open source and under very active development.

I run Torchbox, a small, private tech agency in the UK. We were commissioned by NHS Digital (the state sector organisation behind these tools) to support two related projects: moving NHS.uk to https://github.com/wagtail/wagtail and setting up https://beta.nhs.uk/service-manual/ on Wagtail.

NHS Digital's procurement processes are tight and focused. They have an expert in-house team of developers and delivery managers, and they only used us on where we could accelerate the project.

As a business owner, I would have liked a bigger contract. As a tax-payer and frequent user of the NHS, I'm very happy with their efficiency.

> 'probably smart', 'primarily a salesman'

"A child prodigy in chess, Hassabis reached master standard at the age of 13"

"graduating in 1997 with a Double First[13] from the University of Cambridge"

"obtain[ed] his PhD in cognitive neuroscience from University College London"

"[his] theoretical account of the episodic memory system [...] was listed in the top 10 scientific breakthroughs of the year in any field by the journal Science"

https://en.wikipedia.org/wiki/Demis_Hassabis

Not Flask, but still Python: Wagtail - https://github.com/wagtail/wagtail - is a popular headless CMS option. Michael Harrison from rice.edu / Openstax gave a great talk about this at last week's Wagtail Space:

https://docs.google.com/presentation/d/1ZYMogOeXKCCmr7hDZnzx...

https://www.youtube.com/watch?v=HZT14u6WwdY

Thanks timonweb!

I'm the OP, happy to answer any questions about this release or Wagtail in general.

I'm one of the Wagtail core developers. We made the mistake of spreading our support across too many channels (Google Groups, Stack Overflow, IRC, semi-private Slack) but we've made a clear decision to focus on Stack Overflow for developer-related questions:

https://stackoverflow.com/questions/tagged/wagtail

mainly as a result of this poll:

https://twitter.com/WagtailCMS/status/801384753589080064

Please feel free to contact me directly (details in profile) if you're not getting the support you need on SO.

and Chalice: https://github.com/awslabs/chalice

Note Altify also uploads each of your images to http://uploads.im (looks like an Imgur alternative), and apparently leaves them there:

https://github.com/ParhamP/altify/blob/master/altify/altify....

'the guy'? 'he'?

Most of the sites we build on Wagtail use taxonomies / categorisation, either with a foreign key to categories defined as snippets, or with custom model classes for each page type, as you describe. You're right that Wagtail has no 'native' equivalent of WP's Categories, and perhaps that's a mistake. You're also right to focus on ideas and usage over technical details; we fall into this trap too easily.

I'm very interested in talking more about this, but without derailing the topic. Please email me on my first name at torchbox.com.

This is a fascinating analysis. I'm the CTO of the agency behind the Wagtail CMS (https://wagtail.io) which you reference. People like NASA, Google, Peace Corps, PBS run sites on Wagtail but I'd use WordPress for my friend's 5 page site because:

- < 5 minutes to organise cheap hosting - automatic updates - zillions of themes - someone else can fix it when it goes wrong

I hope Daniele and his colleagues at Aldryn will help with quick cheap Django hosting (they do Wagtail too!). But I'm not sure that Wagtail or Django CMS will ever be the right choice for this use-case. Of course you _could_ build a WordPress equivalent in Django, using postmeta-style key-value tables that abuse relational database theory but allow plugins to define their own content types, and maybe someone should. Our effort is going into building a CMS which helps implementers of non-trivial sites do the 'right thing': keep their content structured, clean, related, filterable. Create once publish everywhere!

There's a lot to learn from WordPress but I don't think 'dynamic models' are the answer for situations where you have more than one developer (there's no guaranteed parity between developer and production environments) or lots of relations (postmeta-style tables have ugly joins, weak integrity checks, poor performance).