You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: getting-started/installation.md
+38-5Lines changed: 38 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
last_modified_date: 2024-01-16 20:49:17 +0100
2
+
last_modified_date: 2024-01-29 21:30:54 +0100
3
3
layout: default
4
4
title: Installation
5
5
description: How to install GatewayD and its plugins on different platforms and how to build it from source.
@@ -95,9 +95,26 @@ docker-compose up -d
95
95
96
96
## Installing plugins
97
97
98
-
Plugins are available as standalone binaries for different platforms. These binaries are available in their GitHub repositories.
98
+
Plugins are available as standalone binaries for different platforms. These binaries are available in their GitHub repositories and are distributed as archives that contain the binary and the default configuration file for the plugin. The README file and the LICENSE file might also be included in the archive.
99
99
100
-
The plugins can be installed by using the `plugin` subcommand of `gatewayd`:
100
+
There are currently four ways to install plugins using the `gatewayd plugin install` subcommand:
101
+
102
+
1. Providing the plugins configuration file with the plugins' URLs and versions.
103
+
2. Using the GitHub URL of the plugin plus the version.
104
+
3. Using the already downloaded archive of the plugin.
105
+
4. Manually downloading, extracting and placing the plugins' binaries in your desired location and updating the plugins configuration file.
106
+
107
+
### 1. Using the plugins configuration file
108
+
109
+
In the `gatewayd_plugins.yaml` configuration file, you can specify the URLs and versions of the plugins that you want to install. The `gatewayd plugin install` subcommand will download the archives of the plugins from the specified URLs and extract them to the `plugins` directory in the current working directory and will also update the `gatewayd_plugins.yaml` configuration file.
110
+
111
+
```bash
112
+
gatewayd plugin install
113
+
```
114
+
115
+
### 2. Using the GitHub URL of the plugin plus the version
116
+
117
+
You can also install plugins using the GitHub URL of the plugin plus the version. The `gatewayd plugin install` subcommand will download the archive of the plugin from the specified URL and extract it to the `plugins` directory in the current working directory.
The plugin binary will be installed in the `plugins` directory in the current working directory. For more flags, please refer to the [CLI](/using-gatewayd/CLI) page or just run `gatewayd plugin install --help`.
129
+
You can also specify that you want to pull only and you don't want to extract the archive of the plugin.
### 3. Using the already downloaded archive of the plugin
136
+
137
+
You can also install plugins using the already downloaded archive of the plugin or using the `--pull-only` flag explained above. The `gatewayd plugin install` subcommand will extract the archive of the plugin to the `plugins` directory in the current working directory. The `--name` flag is mandatory when using this method and it must be the same as the name of the plugin.
### 4. Manually downloading, extracting and placing the plugins' binaries in your desired location
144
+
145
+
You can manually download, extract and place the plugins' binaries in your desired location that is accessible to GatewayD via the plugins configuration file, aka. `gatewayd_plugins.yaml`. Then you must update the plugins configuration file with the desired plugin's configuration that is available in the plugin's repository as `gatewayd_plugin.yaml` (or inside the archive file of the plugin). Checksum files are also available in the plugin's repository as release assets and also inside the archive file of the plugin.
113
146
114
-
Alternatively you can manually download, extract and place the plugins' binaries in your desired location that is accessible to GatewayD via the plugins configuration file, aka. `gatewayd_plugins.yaml`.
147
+
For more flags, please refer to the [CLI](/using-gatewayd/CLI) page or just run `gatewayd plugin install --help`.
115
148
116
149
For more information about plugins, please refer to the [plugins configuration](/using-gatewayd/plugins-configuration/plugins-configuration) and the [plugins](/using-plugins/plugins) page.
Copy file name to clipboardExpand all lines: getting-started/welcome.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
last_modified_date: 2024-01-16 20:49:17 +0100
2
+
last_modified_date: 2024-01-29 21:04:09 +0100
3
3
layout: default
4
4
title: Welcome
5
5
description: Introduction to GatewayD and its key features
@@ -60,7 +60,8 @@ These are just a few examples and the list is not exhaustive, as new plugins are
60
60
61
61
## What GatewayD does not do
62
62
63
-
GatewayD is not a silver bullet and won't solve all your database problems overnight.
63
+
GatewayD is not a silver bullet and won't solve all your database problems overnight.
64
+
64
65
You still have to design and normalize your database schema, take and test backups, secure your database and do whatever you used to do before GatewayD. GatewayD came into existence to fix the black box mentality that surrounds databases to this very day.
65
66
66
67
Over time many plugins will be developed either by us or the community that will try to solve different issues arose from utilizing databases.
0 commit comments