Simon Willison

It looks like you do this using the `flyctl scale vm` command - but the docs at https://fly.io/docs/flyctl/scale-vm/ are missing some details. Filed a documentation bug with Fly about that...

I can get the list of available sizes like so: ``` ~ $ flyctl platform vm-sizes NAME CPU CORES MEMORY PRICE (SECOND) PRICE (MONTH) micro-1x 0.12 128 MB $0.000001 $2.670000...

`flyctl platform vm-sizes --json` ```json [ { "Name": "micro-1x", "CPUCores": 0.125, "MemoryGB": 0.125, "MemoryMB": 128, "PriceMonth": 2.67, "PriceSecond": 0.000001015 }, { "Name": "micro-2x", "CPUCores": 0.25, "MemoryGB": 0.5, "MemoryMB": 512, "PriceMonth":...

That's disappointing: I tried this command again today and it doesn't return accurate pricing information any more: ``` ~ % flyctl platform vm-sizes --json [ { "Name": "shared-cpu-1x", "CPUCores": 1,...

I haven't done this with any of my other `datasette publish` tools, but I do think it's a good idea. Being able to publish the entire directory - with templates...

Filed that as a bug: https://github.com/superfly/flyctl/issues/339

Today the command returns this: ```json [ { "Name": "shared-cpu-1x", "CPUCores": 1, "MemoryGB": 0.25, "MemoryMB": 256, "PriceMonth": 1.94, "PriceSecond": 7.5e-7, "MemoryIncrementsMB": [ 256, 1024, 2048 ] }, { "Name": "dedicated-cpu-1x",...

The command for this is: flyctl scale vm dedicated-cpu-1x You can pass an optional `--memory` option: flyctl scale vm dedicated-cpu-1x --memory=2048 The docs are at https://fly.io/docs/flyctl/scale-vm/ Valid memory values aren't...

Posted a question about this here: https://github.com/superfly/flyctl/issues/478

I'm inclined to add this as a feature - maybe `datasette publish fly ... --scale-to-zero 5m`. Or `--sleep-after 5m` perhaps?