> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/uninstaller.md).

# Uninstaller

The uninstaller removes Bloggers Bot Platform from the server. This is a dangerous operation: it affects applications, databases, uploaded files, and the shared edge component.

{% hint style="danger" %}
Before deleting, make sure the backup is truly not needed or has already been saved separately. After deletion, data can only be restored from a backup.
{% endhint %}

### Startup command

```bash
sudo /opt/bloggers_platform/uninstall.sh
```

Before removal, the utility shows a warning and asks you to enter:

```
UNINSTALL
```

Without this confirmation, removal will not start.

### What is removed

{% tabs %}
{% tab title="Applications" %}
All installed language versions and containers are removed `backend`, `bot`, `db`, the shared Caddy edge and the edge Docker network.
{% endtab %}

{% tab title="Data" %}
Databases in Docker volumes, uploaded assets, settings, cards, bot users, and administrators are removed.
{% endtab %}

{% tab title="Files" %}
The folder is removed `/opt/bloggers_platform`, local service images and the installation log `/tmp/bloggers_bot_install.log`.
{% endtab %}
{% endtabs %}

### Backup before removal

By default, an archive is created before removal:

```
/root/bloggers_platform_uninstall_backup_YYYYMMDD_HHMMSS.tar.gz
```

The archive includes the platform folder and the installation log, if they exist on the server.

{% hint style="info" %}
The archive is created in `/root`, so only the root user can open or download it.
{% endhint %}

### Useful options

| Command                                                    | What it does                             |
| ---------------------------------------------------------- | ---------------------------------------- |
| `sudo /opt/bloggers_platform/uninstall.sh --yes`           | Removes without interactive confirmation |
| `sudo /opt/bloggers_platform/uninstall.sh --no-backup`     | Removes without a preliminary archive    |
| `sudo /opt/bloggers_platform/uninstall.sh --keep-docker`   | Keeps Docker on the server               |
| `sudo /opt/bloggers_platform/uninstall.sh --keep-ufw`      | Keeps UFW on the server                  |
| `sudo /opt/bloggers_platform/uninstall.sh --remove-docker` | Forcibly removes Docker                  |
| `sudo /opt/bloggers_platform/uninstall.sh --remove-ufw`    | Forcibly removes UFW                     |

### Docker and UFW

<details>

<summary>When Docker and UFW are removed automatically</summary>

By default, Docker and UFW are removed only if the installer detected that they were not present on the server before the platform was installed.

If Docker or UFW were used for other projects, it is safer to run the uninstaller explicitly like this:

```bash
sudo /opt/bloggers_platform/uninstall.sh --keep-docker --keep-ufw
```

</details>

### What data is affected

The uninstaller affects all platform data:

* blogger cards;
* categories and tags;
* showcase settings;
* Telegram bot settings;
* bot users;
* administrators;
* uploaded images and media;
* databases of all language versions.

### Removal log

```
/tmp/bloggers_bot_uninstall.log
```

If removal did not complete fully, this file is needed for diagnostics.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/uninstaller.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.