MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 5 Releases 96 Wiki Activity

tech-debt: Fix ACME/TLS setup path issues and install flow #321

New Issue
Open
opened 2026-05-31 14:22:06 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-31 14:22:06 +00:00
Owner
Copy Link
Copy Source

Summary

ACME certificate management and installation have known issues.

Locations

  • cmd/web_acme.go:46 - placeholders until settings options with warnings are added
  • cmd/web_acme.go:68 - path uses AppWorkPath incorrectly, writes into AppWorkPath/https
  • cmd/web.go:243 - should use a proper context
  • routers/install/install.go:415 - oauth2 JWT_SECRET generated regardless of oauth2 enabled state

Action Required

Fix ACME data path to use correct directory. Add proper settings UI for ACME. Fix oauth2 secret generation logic.

Created by Claude Opus 4.6

## Summary ACME certificate management and installation have known issues. ## Locations - `cmd/web_acme.go:46` - placeholders until settings options with warnings are added - `cmd/web_acme.go:68` - path uses AppWorkPath incorrectly, writes into AppWorkPath/https - `cmd/web.go:243` - should use a proper context - `routers/install/install.go:415` - oauth2 JWT_SECRET generated regardless of oauth2 enabled state ## Action Required Fix ACME data path to use correct directory. Add proper settings UI for ACME. Fix oauth2 secret generation logic. --- *Created by Claude Opus 4.6*
jmiller added the tech-debtupstream labels 2026-05-31 14:22:06 +00:00
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels tech-debt upstream
Priority Low
Type Task
Status —
Priority —
Type —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#321
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?