|
| 1 | +# 🪄 Configuration |
| 2 | + |
| 3 | +To configure the Arona, you need to create a configuration file named `config.yaml` in the root directory of the project. |
| 4 | + |
| 5 | +## Configuration File |
| 6 | + |
| 7 | +The configuration file is a YAML file that contains the configuration for the Arona. |
| 8 | + |
| 9 | +```yaml |
| 10 | +deviceName: "Arona" |
| 11 | + |
| 12 | +http: |
| 13 | + bindHost: 127.0.0.1 |
| 14 | + bindPort: 3000 |
| 15 | + baseUrl: "http://example.com" |
| 16 | + |
| 17 | +bridge: |
| 18 | + public: true |
| 19 | + |
| 20 | +bridgeProvider: |
| 21 | + # OpenAI |
| 22 | + openai: |
| 23 | + enable: true |
| 24 | + # https://github.com/ai-tech-tw/openai |
| 25 | + baseUrl: "https://web-tech-tw.eu.org/openai/v1" |
| 26 | + apiKey: "YourGeminiApiKey" |
| 27 | + chatModel: "gpt-3.5-turbo" |
| 28 | + |
| 29 | + # LINE |
| 30 | + line: |
| 31 | + enable: true |
| 32 | + channelAccessToken: "YourChannelAccessToken" |
| 33 | + channelSecret: "YourChannelSecret" |
| 34 | + useNotify: true |
| 35 | + notifyClientId: "YourClientID" |
| 36 | + notifyClientSecret: "YourClientSecret" |
| 37 | + |
| 38 | + # Matrix |
| 39 | + matrix: |
| 40 | + enable: true |
| 41 | + homeserverUrl: "https://matrix.org" |
| 42 | + accessToken: "YourSecretAccessToken" |
| 43 | + |
| 44 | + # Discord |
| 45 | + discord: |
| 46 | + enable: false |
| 47 | + appId: "YourAppId" |
| 48 | + botToken: "YourBotToken" |
| 49 | + |
| 50 | + # Telegram |
| 51 | + telegram: |
| 52 | + enable: false |
| 53 | + botToken: "YourBotToken" |
| 54 | +``` |
| 55 | +
|
| 56 | +## Configuration Options |
| 57 | +
|
| 58 | +The configuration file contains the following options: |
| 59 | +
|
| 60 | +| Option | Description | |
| 61 | +| ---------------- | ---------------------------------- | |
| 62 | +| `deviceName` | The name of the device. | |
| 63 | +| `http` | The HTTP configuration. | |
| 64 | +| `bridge` | The bridge configuration. | |
| 65 | +| `bridgeProvider` | The bridge provider configuration. | |
| 66 | + |
| 67 | +### `deviceName` |
| 68 | + |
| 69 | +The `deviceName` option is used to specify the name of the device. |
| 70 | + |
| 71 | +### `http` |
| 72 | + |
| 73 | +The `http` option is used to configure the HTTP server. |
| 74 | + |
| 75 | +| Option | Description | |
| 76 | +| ---------- | ------------------------ | |
| 77 | +| `bindHost` | The host to bind to. | |
| 78 | +| `bindPort` | The port to bind to. | |
| 79 | +| `baseUrl` | The base URL of the API. | |
| 80 | + |
| 81 | +### `bridge` |
| 82 | + |
| 83 | +The `bridge` option is used to configure the bridge. |
| 84 | + |
| 85 | +| Option | Description | |
| 86 | +| -------- | ------------------------------------ | |
| 87 | +| `public` | Whether the bridge is public or not. | |
| 88 | + |
| 89 | +### `bridgeProvider` |
| 90 | + |
| 91 | +The `bridgeProvider` option is used to configure the bridge provider. |
| 92 | + |
| 93 | +#### OpenAI |
| 94 | + |
| 95 | +The `openai` option is used to configure the OpenAI provider. |
| 96 | + |
| 97 | +| Option | Description | |
| 98 | +| ----------- | --------------------------------------- | |
| 99 | +| `enable` | Whether the provider is enabled or not. | |
| 100 | +| `baseUrl` | The base URL of the OpenAI API. | |
| 101 | +| `apiKey` | The API key of the OpenAI API. | |
| 102 | +| `chatModel` | The chat model to use. | |
| 103 | + |
| 104 | +Details of OpenAI integration can be found [here](integrations/openai.md). |
| 105 | + |
| 106 | +#### LINE |
| 107 | + |
| 108 | +The `line` option is used to configure the LINE provider. |
| 109 | + |
| 110 | +| Option | Description | |
| 111 | +| -------------------- | ----------------------------------------- | |
| 112 | +| `enable` | Whether the provider is enabled or not. | |
| 113 | +| `channelAccessToken` | The channel access token of the LINE API. | |
| 114 | +| `channelSecret` | The channel secret of the LINE API. | |
| 115 | +| `useNotify` | Whether to use LINE Notify or not. | |
| 116 | +| `notifyClientId` | The client ID of the LINE Notify API. | |
| 117 | +| `notifyClientSecret` | The client secret of the LINE Notify API. | |
| 118 | + |
| 119 | +Details of LINE integration can be found [here](integrations/line.md). |
| 120 | + |
| 121 | +#### Matrix |
| 122 | + |
| 123 | +The `matrix` option is used to configure the Matrix provider. |
| 124 | + |
| 125 | +| Option | Description | |
| 126 | +| --------------- | --------------------------------------- | |
| 127 | +| `enable` | Whether the provider is enabled or not. | |
| 128 | +| `homeserverUrl` | The homeserver URL of the Matrix API | |
| 129 | +| `accessToken` | The access token of the Matrix API. | |
| 130 | + |
| 131 | +Details of Matrix integration can be found [here](integrations/matrix.md). |
| 132 | + |
| 133 | +#### Discord |
| 134 | + |
| 135 | +The `discord` option is used to configure the Discord provider. |
| 136 | + |
| 137 | +| Option | Description | |
| 138 | +| ---------- | --------------------------------------- | |
| 139 | +| `enable` | Whether the provider is enabled or not. | |
| 140 | +| `appId` | The application ID of the Discord API. | |
| 141 | +| `botToken` | The bot token of the Discord API. | |
| 142 | + |
| 143 | +Details of Discord integration can be found [here](integrations/discord.md). |
| 144 | + |
| 145 | +#### Telegram |
| 146 | + |
| 147 | +The `telegram` option is used to configure the Telegram provider. |
| 148 | + |
| 149 | +| Option | Description | |
| 150 | +| ---------- | --------------------------------------- | |
| 151 | +| `enable` | Whether the provider is enabled or not. | |
| 152 | +| `botToken` | The bot token of the Telegram API. | |
| 153 | + |
| 154 | +Details of Telegram integration can be found [here](integrations/telegram.md). |
0 commit comments