例如，你大概會看到同一個瀏覽器（Firefox、Chrome、Edge 等）會有多個行程在執行。它們通常每個分頁一個行程，外加其他一些額外行程。

<img class="shadow" src="/img/deployment/concepts/image01.png">

---

現在我們知道「行程」與「程式」的差異了，繼續談部署。

## 開機自動執行 { #running-on-startup }

多數情況下，當你建立一個 Web API，你會希望它「一直在執行」，不中斷，讓客戶端隨時可用。除非你有特定理由只在某些情況下才執行，但大部分時候你會希望它持續運作並且可用。

### 在遠端伺服器上 { #in-a-remote-server }

當你設定一台遠端伺服器（雲端伺服器、虛擬機等），最簡單的作法就是像本機開發時一樣，手動使用 `fastapi run`（它使用 Uvicorn）或類似的方式。

*   `tf.data`

    * `tf.data` now has an `autotune_options.initial_parallelism` option to
      control the initial parallelism setting used by autotune before the data
      pipeline has started running. The default is 16. A lower value reduces
      initial memory usage, while a higher value improves startup time.

## Keras

*  `keras.layers.experimental.DynamicEmbedding`
    * Added `DynamicEmbedding` Keras layer

### Bug or Regression

- Fixed a regression since 1.27.0 in scheduler framework when running score plugins. 
  The `skippedScorePlugins` number might be greater than `enabledScorePlugins`, 
  so when initializing a slice the cap(len(skippedScorePlugins) - len(enabledScorePlugins)) is negative, 

- **Storage**: At least 2x your current index size
- **Network**: Access to crawl sources (web servers, file shares, databases)
- **Elasticsearch/OpenSearch**: Compatible version running

### 3. Backup Existing System

Before migration:

1. Export current search configurations
2. Backup existing indices and data
3. Document custom integrations and API endpoints

///

Now, imagine that with **many** other **packages** that all your **projects depend on**. That's very difficult to manage. And you would probably end up running some projects with some **incompatible versions** of the packages, and not knowing why something isn't working.

                if (crawler1.crawlerContext.getStatus() == CrawlerStatus.RUNNING) {
                    break;
                }
                Thread.sleep(50);
            }
            assertEquals(CrawlerStatus.RUNNING, crawler1.crawlerContext.getStatus());
            for (int i = 0; i < 100; i++) {
                if (crawler2.crawlerContext.getStatus() == CrawlerStatus.RUNNING) {
                    break;
                }

    vulnerability, OkHttp no longer offers SSLv3 when negotiation an
    HTTPS connection. If you continue to need to connect to webservers
    running SSLv3, you must manually configure your own `ConnectionSpec`.

 *  **OkHttp now offers interceptors.** Interceptors are a powerful mechanism

For more information about kubectl debug, see [Debugging Running Pods](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/) on the Kubernetes website, kubectl help debug, or reach out to SIG CLI by visiting [#sig-cli](https://kubernetes.slack.com/messages/sig-cli) or commenting on [enhancement #1441](https://features.k8s.io/1441)....

A security issue was discovered in Kubernetes where users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may only reference secrets specified in the service account's secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used...

    /** The key of the message: Does not match a confirmation password. */
    public static final String ERRORS_invalid_confirm_password = "{errors.invalid_confirm_password}";

    /** The key of the message: A crawler is running. You cannot delete documents. */
    public static final String ERRORS_cannot_delete_doc_because_of_running = "{errors.cannot_delete_doc_because_of_running}";

    /** The key of the message: Failed to delete a document. */