* notes on memory usage

* typo

* Update observability-with-prometheus.md

* Update running.md

* update link

---------

Co-authored-by: Luis Paolini <paoliniluis@gmail.com>

* notes

* more notes

* edits

* update app db page

* file-based db mention

* anchor link

* docs: clarify migrate down for docker

* add jar instructions

* wording

* call attention to POST

* wording

* docs: change paid to pro/enterprise

* Apply suggestions from code review

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

---------

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

* serialization update

* anchor links

* more anchor links

* correct curl call

* Apply suggestions from code review

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

* Apply suggestions from code review

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

* review feedback

* links

* Update docs/installation-and-operation/serialization.md

---------

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

* api details

* Update docs/installation-and-operation/serialization.md

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

---------

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

* add TOC to Jetty article

* add ToC for debian article

* vvariables

* Update docs/installation-and-operation/running-metabase-on-debian.md

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

---------

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

* Remove old config + fix typo

* Add new analytics for 4 new illustration settings

* surfacing docker compose

* Update docs/installation-and-operation/running-metabase-on-docker.md

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

---------

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

add a comment about enterprise version

On version 4.8 metabase version 9.4 is not supported

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

tested which is the min mysql version

* update minimum version for mysql

* format

@jeff-bruemmer pointed out that these names are redundant in #36723.

Theoretically one could argue that the settings aren't actually setting the "query row limit" - when you make a new
question, you can enter whatever limit you like. Instead, they're setting the *maximum* possible "query row limit."

That said, applying two limits is the same as applying the minimum of two limits, so calling it a "query row limit"
makes sense too, and might be more clear.

This replaces the existing setting max-results-bare-rows with two settings:

- `max-unaggregated-query-row-limit`, and
- `max-aggregated-query-row-limit`

* Update upgrading-metabase.md

added note about major version upgrades taking longer

* Update docs/installation-and-operation/upgrading-metabase.md

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

---------

Co-authored-by: Luis Paolini <paoliniluis@gmail.com>
Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

* command page

* formatting

* command updates