> For the complete documentation index, see [llms.txt](https://docs.tomatophp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomatophp.com/plugins/tomato-eddy.md).

# Tomato Eddy

<figure><img src="/files/DTVxfYGSIq9kEx5Aq21x" alt=""><figcaption></figcaption></figure>

before installation, you can check the main repo of [Eddy](https://github.com/protonemedia/eddy-server-management), we do a lot of updates and make Eddy work on the version of Ubuntu and Hetzner API, with fine UI by Tomato Admin and it's components.

### Installation

```
composer require tomatophp/tomato-eddy
```

after installing your package please run this command

```
php artisan tomato-eddy:install
```

### Changelog

Please see [CHANGELOG](https://github.com/tomatophp/tomato-eddy/blob/master/CHANGELOG.md) for more information on what has changed recently.

### Security

Please see [SECURITY](https://github.com/tomatophp/tomato-eddy/blob/master/SECURITY.md) for more security information.

### Credits

* [Fady Mondy](https://3x1.io)

### License

The MIT License (MIT). Please see [License File](https://github.com/tomatophp/tomato-eddy/blob/master/LICENSE.md) for more information.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tomatophp.com/plugins/tomato-eddy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.