mirror of
https://github.com/netbirdio/docs.git
synced 2026-04-18 08:26:35 +00:00
Add backup and upgrade guides for self-hosted deployments (#105)
Co-authored-by: braginini <bangvalo@gmail.com>
This commit is contained in:
@@ -81,7 +81,7 @@ This can be any email address. [Let's Encrypt](https://letsencrypt.org/) will cr
|
||||
</Note>
|
||||
|
||||
<Note>
|
||||
If you want to setup netbird with your own reverse-Proxy and without using the integrated letsencrypt, follow [this step here instead](#advanced-running-netbird-behind-an-existing-reverse-proxy).
|
||||
If you want to setup NetBird with your own reverse-Proxy and without using the integrated letsencrypt, follow [this step here instead](#advanced-running-netbird-behind-an-existing-reverse-proxy).
|
||||
</Note>
|
||||
|
||||
### Step 3: Configure Identity Provider (IDP)
|
||||
@@ -137,15 +137,15 @@ docker-compose logs coturn
|
||||
docker-compose logs dashboard
|
||||
```
|
||||
|
||||
## Advanced: Running netbird behind an existing reverse-proxy
|
||||
## Advanced: Running NetBird behind an existing reverse-proxy
|
||||
|
||||
If you want to run netbird behind your own reverse-proxy, some additional configuration-steps have to be taken to [Step 2](#step-2--prepare-configuration-files).
|
||||
If you want to run NetBird behind your own reverse-proxy, some additional configuration-steps have to be taken to [Step 2](#step-2--prepare-configuration-files).
|
||||
|
||||
<Note>
|
||||
Not all reverse-proxies are supported as netbird uses *gRPC* for various components.
|
||||
Not all reverse-proxies are supported as NetBird uses *gRPC* for various components.
|
||||
</Note>
|
||||
|
||||
### Configuration for netbird
|
||||
### Configuration for NetBird
|
||||
|
||||
In `setup.env`:
|
||||
- Set ```NETBIRD_DOMAIN``` to your domain, e.g. `demo.netbird.io`
|
||||
@@ -182,6 +182,35 @@ Make sure your reverse-Proxy is setup to use the HTTP2-Protocol when forwarding.
|
||||
Simply replace the file `docker-compose.yml.tmpl` with the chosen version.
|
||||
</Note>
|
||||
|
||||
## Backup
|
||||
To backup your NetBird installation, you need to copy the configuration files, and the Management service databases.
|
||||
|
||||
The configuration files are located in the folder where you ran the installation script. To backup, copy the files to a backup location:
|
||||
```bash
|
||||
cd netbird/infrastructure_files/
|
||||
mkdir backup
|
||||
cp docker-compose.yml turnserver.conf management.json backup/
|
||||
```
|
||||
To save the Management service databases, you need to stop the Management service and copy the files from the store directory using a docker compose command as follows:
|
||||
```bash
|
||||
docker compose stop management
|
||||
docker compose cp -a management:/var/lib/netbird/ backup/
|
||||
docker compose start management
|
||||
```
|
||||
|
||||
## Upgrade
|
||||
To upgrade NetBird to the latest version, you need to review the [release notes](https://github.com/netbirdio/netbird/releases) for any breaking changes and follow the upgrade steps below:
|
||||
1. Run the backup steps described in the [backup](#backup-net-bird) section.
|
||||
2. Pull the latest NetBird docker images:
|
||||
```bash
|
||||
cd netbird/infrastructure_files/
|
||||
docker compose pull
|
||||
```
|
||||
3. Restart the NetBird containers with the new images:
|
||||
```bash
|
||||
docker compose up -d --force-recreate
|
||||
```
|
||||
|
||||
## Get in touch
|
||||
|
||||
Feel free to ping us on [Slack](https://join.slack.com/t/netbirdio/shared_invite/zt-vrahf41g-ik1v7fV8du6t0RwxSrJ96A) if you have any questions
|
||||
|
||||
Reference in New Issue
Block a user