- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for Slough (0.14 sec)
-
docs/en/docs/advanced/behind-a-proxy.md
In this case, the original path `/app` would actually be served at `/api/v1/app`. Even though all your code is written assuming there's just `/app`. ```Python hl_lines="6" {!../../../docs_src/behind_a_proxy/tutorial001.py!} ```
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 11.6K bytes - Viewed (2) -
docs/en/docs/deployment/concepts.md
In this case, it would be better to get **one extra server** and run some processes on it so that they all have **enough RAM and CPU time**.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 18K bytes - Viewed (0) -
docs/en/docs/advanced/settings.md
If you have many settings that possibly change a lot, maybe in different environments, it might be useful to put them on a file and then read them from it as if they were environment variables. This practice is common enough that it has a name, these environment variables are commonly placed in a file `.env`, and the file is called a "dotenv". !!! tip A file starting with a dot (`.`) is a hidden file in Unix-like systems, like Linux and macOS.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 15.7K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
Here are some examples of when that could make sense: #### A Simple App You could want a process manager in the container if your application is **simple enough** that you don't need (at least not yet) to fine-tune the number of processes too much, and you can just use an automated default (with the official Docker image), and you are running it on a **single server**, not a cluster.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 34K bytes - Viewed (0)