github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 13:20:06 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Feature Request: Armv8 support for the DS218play Synology nas #2359

New Issue
Closed
opened 2025-11-02 04:33:48 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:33:48 -06:00
Owner
Copy Link

Originally created by @Hecatron on GitHub (Sep 26, 2018).

Hi,
would it be possible to include an armv8 version in the releases for use with the Synology nas DS218play.

I've discovered it's possible to run gitea on an rpi using the nas's maria 10 database.
By running the following on the database

set global innodb_large_prefix = `ON`
set global innodb_file_format=Barracuda
Set GLOBAL innodb_file_per_table=ON;
Originally created by @Hecatron on GitHub (Sep 26, 2018). Hi, would it be possible to include an armv8 version in the releases for use with the Synology nas DS218play. I've discovered it's possible to run gitea on an rpi using the nas's maria 10 database. By running the following on the database ``` set global innodb_large_prefix = `ON` set global innodb_file_format=Barracuda Set GLOBAL innodb_file_per_table=ON; ```
GiteaMirror added the type/proposaltopic/build labels 2025-11-02 04:33:48 -06:00
GiteaMirror commented 2025-11-02 04:33:49 -06:00
Author
Owner
Copy Link

@Hecatron commented on GitHub (Sep 28, 2018):

It turns out this does work after all, I just needed to use the arm64 build which is the same thing

@Hecatron commented on GitHub (Sep 28, 2018): It turns out this does work after all, I just needed to use the arm64 build which is the same thing
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/build type/proposal
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#2359
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?