Add Gitea integration; fix .env never being loaded outside Docker
Second live integration: repo list with last CI run status, and re-running
failed jobs on a workflow run — matching the "dashboard + basic actions"
depth from the plan. Adapter built directly against the real Gitea 1.27
swagger spec (fetched from the user's own instance) rather than guessing at
the API shape: GET /user/repos for the repo list, GET
/repos/{owner}/{repo}/actions/runs?limit=1 for the latest run per repo (only
for repos with Actions enabled), and POST .../rerun-failed-jobs for retrying
just the failed jobs in a run. Follows the same config-in-UI +
encrypted-credential pattern as Tailscale and DNS providers.
Since Gitea collects its own base URL as a config field (unlike Tailscale,
which always talks to a fixed api.tailscale.com), generalized the
"integrations.baseUrl" bookkeeping into resolveBaseUrl() instead of the
one-fixed-URL-per-type map used previously.
Also fixed a real gap found while setting this up: server/src/env.ts reads
process.env directly, but nothing in the app ever loaded .env into
process.env for plain `node dist/index.js` / `tsx src/index.ts` runs — only
Docker's `env_file` config populated it, by injecting vars before Node even
starts. Every local (non-Docker) run silently had every setting at its
insecure default. Added server/src/loadEnv.ts (dotenv, pointed at the
repo-root .env) as the first import in both server/src/index.ts and
server/src/db/migrate.ts's standalone entrypoint.
Verified against the user's real, reachable services — not mocks:
- Authentik (auth.labsconnect.se): full OIDC login completed by the user
through the real UI; confirmed their account landed as admin (first user).
- Gitea (gitea.labsconnect.se): the compiled adapter run directly against a
real API token correctly listed all 11 real repos; a full HTTP-layer test
against the live server (8 checks) additionally covered a real
test-connection ping, credential non-leakage in list responses, and role
gating (403) on the rerun-failed-jobs action even with a valid token
behind it. None of the real repos have any workflow run history yet, so
the success/failure status badge and the rerun action itself are
implemented per the swagger spec but not yet exercised against a real run
— worth checking once one of those repos has actual CI activity.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
069225c656
commit
79710aa7a5
12 files changed
+479
-6
No files matched your search
@@ -11,9 +11,15 @@ const WIDGETS: { type: IntegrationType; label: string }[] = [
|
||||
{ type: "dockhand", label: "Dockhand / Docker" },
|
||||
];
|
||||
|
||||
interface GiteaSummary {
|
||||
repoCount: number;
|
||||
failing: number;
|
||||
}
|
||||
|
||||
export default function Dashboard({ user }: { user: CurrentUser }) {
|
||||
const [integrations, setIntegrations] = useState<IntegrationSummary[] | null>(null);
|
||||
const [tailscaleSummary, setTailscaleSummary] = useState<TailscaleDevicesResponse["summary"] | null>(null);
|
||||
const [giteaSummary, setGiteaSummary] = useState<GiteaSummary | null>(null);
|
||||
|
||||
useEffect(() => {
|
||||
api.integrations.list().then((res) => setIntegrations(res.integrations));
|
||||
@@ -31,6 +37,23 @@ export default function Dashboard({ user }: { user: CurrentUser }) {
|
||||
.catch(() => setTailscaleSummary(null));
|
||||
}, [integrations]);
|
||||
|
||||
useEffect(() => {
|
||||
const gitea = integrations?.find((i) => i.type === "gitea" && i.enabled);
|
||||
if (!gitea) {
|
||||
setGiteaSummary(null);
|
||||
return;
|
||||
}
|
||||
api.integrations.gitea
|
||||
.repos(gitea.id)
|
||||
.then((res) =>
|
||||
setGiteaSummary({
|
||||
repoCount: res.repos.length,
|
||||
failing: res.repos.filter((r) => r.latestRun?.conclusion === "failure" || r.latestRun?.status === "failure").length,
|
||||
}),
|
||||
)
|
||||
.catch(() => setGiteaSummary(null));
|
||||
}, [integrations]);
|
||||
|
||||
return (
|
||||
<>
|
||||
<div className="row row-cards mb-3">
|
||||
@@ -46,7 +69,9 @@ export default function Dashboard({ user }: { user: CurrentUser }) {
|
||||
<div className="row row-cards">
|
||||
{WIDGETS.map(({ type, label }) => {
|
||||
const integration = integrations?.find((i) => i.type === type && i.enabled);
|
||||
const isLive = type === "tailscale" && integration && tailscaleSummary;
|
||||
const isLiveTailscale = type === "tailscale" && integration && tailscaleSummary;
|
||||
const isLiveGitea = type === "gitea" && integration && giteaSummary;
|
||||
const isLive = isLiveTailscale || isLiveGitea;
|
||||
|
||||
return (
|
||||
<div className="col-sm-6 col-lg-4" key={type}>
|
||||
@@ -64,7 +89,7 @@ export default function Dashboard({ user }: { user: CurrentUser }) {
|
||||
)}
|
||||
</div>
|
||||
</div>
|
||||
{isLive ? (
|
||||
{isLiveTailscale ? (
|
||||
<div className="mt-2">
|
||||
<div className="h3 mb-0">
|
||||
{tailscaleSummary!.online}/{tailscaleSummary!.total}
|
||||
@@ -74,6 +99,14 @@ export default function Dashboard({ user }: { user: CurrentUser }) {
|
||||
<div className="text-yellow small mt-1">{tailscaleSummary!.unauthorized} awaiting authorization</div>
|
||||
)}
|
||||
</div>
|
||||
) : isLiveGitea ? (
|
||||
<div className="mt-2">
|
||||
<div className="h3 mb-0">{giteaSummary!.repoCount}</div>
|
||||
<div className="text-secondary">repositories</div>
|
||||
{giteaSummary!.failing > 0 && (
|
||||
<div className="text-red small mt-1">{giteaSummary!.failing} with a failing build</div>
|
||||
)}
|
||||
</div>
|
||||
) : (
|
||||
<div className="text-secondary mt-2">
|
||||
{integration ? (
|
||||
|
||||
Reference in new issue
Block a user