> For the complete documentation index, see [llms.txt](https://docs.dyrector.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dyrector.io/features/templates/linkace.md).

# LinkAce

[**LinkAce**](https://github.com/Kovah/LinkAce/) **is a self-hosted archive to collect links of your favorite websites. You can quickly set it up on your infrastructure. Template consists of MariaDB (10.7) and LinkAce image with `simple` tag.**&#x20;

After the Node where you'd like to run LinkAce is [**registered**](https://docs.dyrector.io/tutorials/register-your-node.md), you can set it up by following the steps of deployments as documented [**here**](https://docs.dyrector.io/tutorials/deploy-your-product.md).

Requirements:

1. `APP_KEY` environment variable must be 32 characters long.
2. After deployment, exec in the linkace-app container and add `chmod 777` privileges to the `\app\.env` file.

Once the deployment is successful, LinkAce is ready to use at [**localhost:6780**](http://localhost:6780/) by default, as seen below.

<figure><img src="https://315393028-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCNvxW8k55ZlpJfMk8Oep%2Fuploads%2FkMWiYlsGMM9hGydwv5fs%2Fdyrector-io-linkace-setup-01.png?alt=media&amp;token=2e06accb-5659-420c-a964-cd7c0ef7da69" alt=""><figcaption></figcaption></figure>


---

# 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.dyrector.io/features/templates/linkace.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.
