> For the complete documentation index, see [llms.txt](https://pwa.spomky-labs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pwa.spomky-labs.com/1.3.x/deployment.md).

# Deployment

## With Asset Mapper

In the `dev` environment, the resources are automactilly handled and returned by a dedicated request listener.

For the `prod` environment all the assets shall be compiled. This means the favicons, the manifests, the service worker and all dependencoes (IndexDB, Workbox...) will be stored as pure assets.

Before deploy, you should run:

```sh
symfony console asset-map:compile
```

## Without Asset Mapper

If you do not want to compile PWA assets with asset mapper, set `false` to the configuration option `pwa.asset_compiler` .

{% code title="config/packages/pwa.yaml" lineNumbers="true" %}

```yaml
pwa:
    asset_compiler: false
```

{% endcode %}

{% hint style="info" %}
Note that `true` is the default value in `1.x`, but will be set to `false` in `2.x`.
{% endhint %}

Then execute the following command to compile ALL assets exactly in the same manner as with Asset Mapper.

```sh
symfony console pwa:compile
```

If you have defined paths or URIs that depend on the application context, especially those relying on the `default_uri` parameter, make sure the context is set **before** running the command.\
Otherwise, generated URLs may default to something like `http://localhost/...` instead of the expected `https://acme.com/...`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://pwa.spomky-labs.com/1.3.x/deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.