> For the complete documentation index, see [llms.txt](https://docs.mapsindoors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapsindoors.com/products/fast-track-maptemplate/deploying-map-template-to-a-cloud-storage-provider.md).

# Deploying Map Template to a cloud storage provider

This page will guide you through the process of deploying the Map Template to a cloud storage provider.

We often use Google Cloud Storage (GCS) to deploy small useful apps for demo purposes. This guide refers to GCS, but many steps are identical for AWS, Azure Blob, and others.

Running the regular build command (`npm run build`), it's assumed that all links refer to the root of a domain. When you deploy to a storage bucket, you must build the app with the bucket name prepended to all links. Vite has a build option to take care of this:

```bash
vite build --base=/YOUR_BUCKET_NAME
```

You can upload the files manually to your bucket or use the helpful CLI [`gsutil`](https://cloud.google.com/storage/docs/gsutil). This command uploads the complete `build` folder and prevents the files from being cached:

```bash
gsutil -m -h "Cache-Control:public, max-age=0, no-store, no-cache" cp -r build gs://YOUR_BUCKET_NAME
```


---

# 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://docs.mapsindoors.com/products/fast-track-maptemplate/deploying-map-template-to-a-cloud-storage-provider.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.