> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/getting-started/running-on-linux.md).

# Manage the Linux service

Once WriteBackExtreme is installed and registered as a service on Linux, this is how you start, stop and check it. For the installation itself, see [Linux](https://docs.infotopics.com/getting-started/getting-started/linux.md).

The application binary lives at `/usr/local/share/writebackextreme/writebackextreme-amd64` and is **not** on your `PATH`, so every command below uses the full path. The service itself is registered as **WriteBackExtreme**.

### Start, stop and check the service

WriteBackExtreme wraps your service manager, so you can use either its own commands or the service manager directly. They do the same thing.

{% tabs %}
{% tab title="Via WriteBackExtreme" %}
**Service status**

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 service status
```

**Start the service**

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 service start
```

**Stop the service**

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 service stop
```

**Restart the service**

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 service restart
```

{% endtab %}

{% tab title="systemd" %}
**Service status**

```bash
sudo systemctl status WriteBackExtreme
```

**Start the service**

```bash
sudo systemctl start WriteBackExtreme
```

**Stop the service**

```bash
sudo systemctl stop WriteBackExtreme
```

**Restart the service**

```bash
sudo systemctl restart WriteBackExtreme
```

{% endtab %}

{% tab title="SysVinit" %}
**Service status**

```bash
sudo service WriteBackExtreme status
```

**Start the service**

```bash
sudo service WriteBackExtreme start
```

**Stop the service**

```bash
sudo service WriteBackExtreme stop
```

**Restart the service**

```bash
sudo service WriteBackExtreme restart
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
The service name is spelled **WriteBackExtreme**, with capitals. On a case-sensitive system a lower-case name will not be found.
{% endhint %}

### Register and remove the service

The post-install script registers the service for you during a first install. These commands let you do it by hand, for example after moving an installation to another server.

Check whether the service is registered:

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 service status
```

Register the service:

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 service install
```

Remove the service registration:

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 service uninstall
```

### Where to find the logs

| Log             | Path                                                                              |
| --------------- | --------------------------------------------------------------------------------- |
| Application log | `/usr/local/share/writebackextreme/.wbe-runtime/storage/logs/wbe-application.log` |
| Server log      | `/usr/local/share/writebackextreme/logs/`                                         |

### Change configuration after installation

Configuration such as the domain, the SSL certificate, the license and the repository database credentials lives in `/usr/local/share/writebackextreme/wbe.config.toml`. Rather than editing the file, open the configuration panel for 15 minutes and change it there:

{% content-ref url="/pages/0aNfQR8JbAGmIZ66DZG6" %}
[Configuration panel](https://docs.infotopics.com/configuration/configuration-panel.md)
{% endcontent-ref %}


---

# 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://docs.infotopics.com/getting-started/running-on-linux.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.
