github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-23 08:01:19 -05:00
Code Issues 140 Packages Projects Releases 100 Wiki Activity

[PR #194] [MERGED] nix: fix runtime wrapper paths and startup script packaging #3013

New Issue
Closed
opened 2026-05-20 14:50:20 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-20 14:50:20 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/194
Author: @arunavo4
Created: 2/26/2026
Status: ✅ Merged
Merged: 2/26/2026
Merged by: @arunavo4

Base: main ← Head: codex/fix-nix-setup-v2

📝 Commits (2)

  • 9f11cb7 nix: fix flake module and runtime scripts
  • 6722084 docs: refresh readme and docs links/examples

📊 Changes

6 files changed (+27 additions, -22 deletions)

View changed files

📝 NIX.md (+1 -1)
📝 README.md (+3 -3)
📝 docs/DEVELOPMENT_WORKFLOW.md (+5 -5)
📝 docs/NIX_DISTRIBUTION.md (+8 -8)
📝 docs/README.md (+3 -3)
📝 flake.nix (+7 -2)

📄 Description

Summary

  • fix runtime wrapper paths to avoid using $out at runtime and resolve app dir from script location
  • include src/, drizzle/, and tsconfig.json in the Nix package so startup TypeScript scripts can resolve imports

Docker verification

  • docker run ... nix flake check ✅
  • docker run ... nix build .#gitea-mirror ✅
  • docker run ... timeout 15s ./result/bin/gitea-mirror ✅
    • startup recovery/config scripts ran successfully
    • app booted and listened on port 4321

Context

This is a follow-up after the earlier Nix PR merge, fixing the remaining runtime issues discovered during containerized verification.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/RayLabsHQ/gitea-mirror/pull/194 **Author:** [@arunavo4](https://github.com/arunavo4) **Created:** 2/26/2026 **Status:** ✅ Merged **Merged:** 2/26/2026 **Merged by:** [@arunavo4](https://github.com/arunavo4) **Base:** `main` ← **Head:** `codex/fix-nix-setup-v2` --- ### 📝 Commits (2) - [`9f11cb7`](https://github.com/RayLabsHQ/gitea-mirror/commit/9f11cb7d6b29fe5af6a7c7802df6214e8545d5ac) nix: fix flake module and runtime scripts - [`6722084`](https://github.com/RayLabsHQ/gitea-mirror/commit/67220843bd8a8b2cc975dfaa3d95464ecb01d69e) docs: refresh readme and docs links/examples ### 📊 Changes **6 files changed** (+27 additions, -22 deletions) <details> <summary>View changed files</summary> 📝 `NIX.md` (+1 -1) 📝 `README.md` (+3 -3) 📝 `docs/DEVELOPMENT_WORKFLOW.md` (+5 -5) 📝 `docs/NIX_DISTRIBUTION.md` (+8 -8) 📝 `docs/README.md` (+3 -3) 📝 `flake.nix` (+7 -2) </details> ### 📄 Description ## Summary - fix runtime wrapper paths to avoid using `$out` at runtime and resolve app dir from script location - include `src/`, `drizzle/`, and `tsconfig.json` in the Nix package so startup TypeScript scripts can resolve imports ## Docker verification - `docker run ... nix flake check` ✅ - `docker run ... nix build .#gitea-mirror` ✅ - `docker run ... timeout 15s ./result/bin/gitea-mirror` ✅ - startup recovery/config scripts ran successfully - app booted and listened on port 4321 ## Context This is a follow-up after the earlier Nix PR merge, fixing the remaining runtime issues discovered during containerized verification. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-20 14:50:20 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#3013
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?