T3 only detects a Gitea on a custom domain through a matching tea or fj login, so creating a change request failed with "No unknown source control provider is registered". Put tea on T3's PATH with an m3ta-chiron login built at runtime from the hermes-gitea-token agenix secret. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 lines
640 B
Nix
27 lines
640 B
Nix
{
|
|
age = {
|
|
secrets = {
|
|
hermes-gitea-token = {
|
|
file = ../../secrets/hermes-gitea-token.age;
|
|
owner = "m3tam3re";
|
|
};
|
|
hermes-env = {
|
|
file = ../../secrets/hermes-env.age;
|
|
};
|
|
hermes-cloud-env = {
|
|
file = ../../secrets/hermes-cloud-env.age;
|
|
};
|
|
hermes-api-server-key = {
|
|
file = ../../secrets/hermes-api-server-key.age;
|
|
};
|
|
ai-memory-server-env = {
|
|
file = ../../secrets/ai-memory-server-env.age;
|
|
};
|
|
ai-memory-hermes-token = {
|
|
file = ../../secrets/ai-memory-hermes-token.age;
|
|
owner = "hermes";
|
|
};
|
|
};
|
|
};
|
|
}
|