coop-cloud/gitea
coop-cloud/gitea
5
2
Fork 4
Code Issues 2 Pull Requests 2 Releases Wiki Activity

feat: lfs server #42

Open
fauno wants to merge 2 commits from lfs into master
pull from: lfs
merge into: coop-cloud:master
Conversation 1 Commits 2 Files Changed 5 +17 -1
fauno commented 2025-02-18 18:45:29 +00:00
Owner
Copy Link
No description provided.
fauno added 1 commit 2025-02-18 18:45:29 +00:00
fauno commented 2025-02-18 18:46:38 +00:00
Author
Owner
Copy Link

also added a way to adapt the app.ini template to forgejo variables

also added a way to adapt the app.ini template to forgejo variables
decentral1se reviewed 2025-02-19 08:35:21 +00:00
app.ini.tmpl Outdated
@ -61,2 +61,4 @@
SSH_PORT = {{ env "GITEA_SSH_PORT" }}
START_SSH_SERVER = true
LFS_START_SERVER = {{ env "GITEA_LFS_START_SERVER" }}
{{ if eq (env "FORGEJO") "1" }}
decentral1se commented 2025-02-19 08:35:01 +00:00
Owner
Copy Link

Perhaps reusing the COMPOSE_FILE value with strings.Contains for "compose.forgejo.yml" is also an option? I feel like people might forget that switch (FORGEJO) or not understand what it relates to (since it is only used now for the LFS functionality. Up to you!

Perhaps reusing the `COMPOSE_FILE` value with [`strings.Contains`](https://docs.gomplate.ca/functions/strings/#examples-1) for `"compose.forgejo.yml"` is also an option? I feel like people might forget that switch (`FORGEJO`) or not understand what it relates to (since it is only used now for the LFS functionality. Up to you!
fauno commented 2025-02-19 13:17:24 +00:00
Author
Owner
Copy Link

i was thinking of setting ENVVAR=gitea for gitea and ENVVAR=forgejo, or even forking the recipe to make one exclusive for forgejo if they start being too different. i couldn't come up with a descriptive name for ENVVAR though

i was thinking of setting ENVVAR=gitea for gitea and ENVVAR=forgejo, or even forking the recipe to make one exclusive for forgejo if they start being too different. i couldn't come up with a descriptive name for ENVVAR though
decentral1se commented 2025-02-20 08:26:07 +00:00
Owner
Copy Link

@fauno tbh i think now that forgejo is a hard fork splitting up the recipe would be best (like we do for Mastodon/Hometown). but that's a bit of work... the ENVVAR approach is fine for now tho. Maybe open a ticket so we don't forget about it?

@fauno tbh i think now that forgejo is [a hard fork](https://forgejo.org/2024-02-forking-forward/) splitting up the recipe would be best (like we do for Mastodon/Hometown). but that's a bit of work... the `ENVVAR` approach is fine for now tho. Maybe open a ticket so we don't forget about it?
fauno commented 2025-02-20 12:18:29 +00:00
Author
Owner
Copy Link

done!

done!
❤️ 1
decentral1se marked this conversation as resolved
fauno added 1 commit 2025-02-20 12:18:22 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin lfs:lfs
git checkout lfs
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/gitea#42
No description provided.
Delete Branch "lfs"

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?