fix: gitea direct port access, push to registry, no PROXY_APPS
Gitea image pushed to Archipelago registry. PROXY_APPS stays empty per user preference - direct port only. Gitea config uses INSTALL_LOCK + dark theme. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
61e251b8ca
commit
c520109108
@ -51,9 +51,7 @@ export const APP_PORTS: Record<string, number> = {
|
|||||||
/** Apps that need nginx proxy for iframe embedding.
|
/** Apps that need nginx proxy for iframe embedding.
|
||||||
* IndeedHub loads via /app/indeedhub/ proxy for nostr-provider.js injection
|
* IndeedHub loads via /app/indeedhub/ proxy for nostr-provider.js injection
|
||||||
* from the container's internal nginx so iframe works on all servers. */
|
* from the container's internal nginx so iframe works on all servers. */
|
||||||
export const PROXY_APPS: Record<string, string> = {
|
export const PROXY_APPS: Record<string, string> = {}
|
||||||
'gitea': '/app/gitea/',
|
|
||||||
}
|
|
||||||
|
|
||||||
/** Nginx proxy paths -- used on HTTPS to avoid mixed content (HTTPS parent + HTTP port iframe).
|
/** Nginx proxy paths -- used on HTTPS to avoid mixed content (HTTPS parent + HTTP port iframe).
|
||||||
* On HTTP, direct port access is used instead (faster, no proxy). */
|
* On HTTP, direct port access is used instead (faster, no proxy). */
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user