todo.txt

this sucks => import {Viewer} from "/static/js/icosa-viewer.module.js?v={% now "U" %}";

Add max complexity as a search filter

orderBy is currently:
BEST, NEWEST, OLDEST. Defaults to BEST, which ranks assets
based on a combination of popularity and other features. 
We should improve this, but probably keep the existing variants working. BEST could possibly be "number of likes" or something for now.

we should accept snake_case and camelCase url params and do the translation. The openapi docs should list both as accepted styles. If we get both variants of the same param, just choose the value of whatever we got first.






Docs for potential inclusion TODO include some info on how to wrangle this with Windows:

## Seeding the database

TODO - explain what "seeding" means and why you'd want to

TODO - explain "from inside the container"

### With a .dump file

```
docker cp <db.dump> ig-db:/opt/
docker exec -it ig-db bash
```

Then from inside the container:

`pg_restore --data-only -U icosa -d icosa /opt/<db.dump>`

### With a .sql file

```
docker cp <db.sql> ig-db:/opt/
docker exec -it ig-db bash
```

Then from inside the container:

`psql -U icosa`

Then from inside the postgres shell:

Make sure you are connected to the correct database:

`\c`

You should see `You are now connected to database "icosa" as user "icosa".`

Import the sql data:

`\i /opt/db.sql`


## Running updated versions of the code

TODO - how are people meant to distinguish between 2 and 3?
Give them a single, safe default action even if it's a bit slower
Is (3) even needed? Seems to happen automatically for me.

There are 3 possible scenarios:


### 1. You've updated your own .env files

```
docker compose down
docker compose build
docker compose up
```

### 2. Incoming code has updated requirements.txt/requirements.in

```
docker compose down`
docker compose build`
docker compose up
```

### 3. Incoming code has updated anything else

`docker compose restart`