> For the complete documentation index, see [llms.txt](https://ayakaleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ayakaleaf-pro.ayaka.space/on-premises/zh-cn/an-zhuang/using-the-toolkit/3.-initialize-the-configuration.md).

# 3. 初始化配置

### 初始化配置 <a href="#initializing-the-configuration" id="initializing-the-configuration"></a>

让我们通过运行 bundle 来用一些合理的默认值初始化新服务器的配置文件 `bin/init` 脚本。

{% code title="运行初始化" %}

```
bin/init
```

{% endcode %}

此脚本将 **不要** 覆盖任何现有的配置文件。

现在让我们查看 `config/` 目录的内容，使用 `ls` 命令：

{% code title="列出 config 目录" %}

```
ls config
```

{% endcode %}

如果一切都已成功初始化，你应该会看到三个配置文件： `overleaf.rc`, `variables.env` 和 `版本`。这些是主要的服务器配置文件，可让你自定义服务器的运行方式以及用户与实例交互的方式。

| 名称              | 描述                   |
| --------------- | -------------------- |
| `overleaf.rc`   | 主顶级配置文件。             |
| `variables.env` | 加载到 Docker 容器中的环境变量。 |
| `版本`            | 要使用的 Docker 镜像版本。    |

{% hint style="info" %}
目前，你只需知道这些文件存在以及可以在哪里找到它们即可。在文档后面的部分，我们会更详细地介绍每个文件，并解释如何使用它们来定制你的实例。如果你想提前了解，可以在 [文件和位置页面](/on-premises/zh-cn/pei-zhi/overleaf-toolkit/files-and-locations.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ayakaleaf-pro.ayaka.space/on-premises/zh-cn/an-zhuang/using-the-toolkit/3.-initialize-the-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.