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

[PR #2568] [MERGED] snap-packaging for gitea #16473

New Issue
Closed
opened 2025-11-02 12:11:27 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 12:11:27 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/2568
Author: @tbraeutigam
Created: 9/21/2017
Status: ✅ Merged
Merged: 5/9/2018
Merged by: @lunny

Base: master ← Head: master

📝 Commits (9)

  • f9211d5 Modify tbraeutigam/gogs-snap for gitea
  • 7ebfe93 Fix building on 16.04 (manually build go-bindata).
  • 412e695 Streamline Snap packaging:
  • 6ebf2e0 Merge remote-tracking branch 'upstream/master'
  • 82629f3 Move to using Snap Hooks for configuration
  • 68f7545 Missed re-adding daemon statement
  • 182651a Merge branch 'master' into master
  • 06982ca Fix two warnings from Codacy.
  • 34071af Merge branch 'master' into master

📊 Changes

7 files changed (+394 additions, -0 deletions)

View changed files

📝 .gitignore (+10 -0)
➕ snap/helpers/app.ini (+66 -0)
➕ snap/helpers/configuration.sh (+126 -0)
➕ snap/helpers/simple_launcher.sh (+23 -0)
➕ snap/hooks/configure (+3 -0)
➕ snap/hooks/install (+45 -0)
➕ snap/snapcraft.yaml (+121 -0)

📄 Description

As per @kwill 's request in https://github.com/tbraeutigam/gogs-snap/issues/1 and #2539, I modified my gogs-snap to fit with gitea.

Changes to Gitea Code:

  • None for actual code
  • .gitignore:
    Adding a couple of exceptions for snapcraft files that might come up during compilation.

New Files:

  • snap/snapcraft.yaml
    The snap package instructions
  • snap/helpers/simple_launcher.sh
    A simplistic wrapper for gitea, to fit with the snap environment
  • snap/helpers/directorySetup.sh
    Sets up the directories/copied data from r/o $SNAP to $SNAP_DATA and $SNAP_COMMON
  • snap/helpers/snapApp.ini
    A few default settings (really 99% of changes are to adjust the paths properly for the Snap environment).

Rationale:
A snap version allows for quick testing and/or easy local hosting on your own machine/own network.
The snap does not restrict you from using any of the database options. It defaults to Sqlite3 on the setup page as that is what can be immediately used without further issues from within the snap.

Tested Scenarios:

  • Ran through a couple of coming use cases (create repo, issues, clone/pull/push, PR, etc)
  • Builds fine from current master (Tested on Ubuntu 17.04 and 16.04 LTS)

If you do accept the pull-request it would be great if you could set up gitea to be automatically build via https://build.snapcraft.io -- it will allow it to be built on any commit to the master branch (or any other branch you specify).

🔄 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/go-gitea/gitea/pull/2568 **Author:** [@tbraeutigam](https://github.com/tbraeutigam) **Created:** 9/21/2017 **Status:** ✅ Merged **Merged:** 5/9/2018 **Merged by:** [@lunny](https://github.com/lunny) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (9) - [`f9211d5`](https://github.com/go-gitea/gitea/commit/f9211d56d75238269d353b034793714eddf04ff5) Modify tbraeutigam/gogs-snap for gitea - [`7ebfe93`](https://github.com/go-gitea/gitea/commit/7ebfe93fb73c08e69ef8f4211ce38fd4482ac64a) Fix building on 16.04 (manually build go-bindata). - [`412e695`](https://github.com/go-gitea/gitea/commit/412e6951111b449c319f089401084cc7f55853bc) Streamline Snap packaging: - [`6ebf2e0`](https://github.com/go-gitea/gitea/commit/6ebf2e0212da31c4179507a103928ceb8a482029) Merge remote-tracking branch 'upstream/master' - [`82629f3`](https://github.com/go-gitea/gitea/commit/82629f37ada74a601e29f04918a7294fc08514f4) Move to using Snap Hooks for configuration - [`68f7545`](https://github.com/go-gitea/gitea/commit/68f7545faa09215f915dfd5d67b37d0c6fd932d1) Missed re-adding daemon statement - [`182651a`](https://github.com/go-gitea/gitea/commit/182651afee65a0477e8caed420c9ceca8bc1aeff) Merge branch 'master' into master - [`06982ca`](https://github.com/go-gitea/gitea/commit/06982cac7781ff2f33cb00f7e33901b96e4e9a05) Fix two warnings from Codacy. - [`34071af`](https://github.com/go-gitea/gitea/commit/34071af9b3eb10f3c61a65b4b9905746fca2af4b) Merge branch 'master' into master ### 📊 Changes **7 files changed** (+394 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.gitignore` (+10 -0) ➕ `snap/helpers/app.ini` (+66 -0) ➕ `snap/helpers/configuration.sh` (+126 -0) ➕ `snap/helpers/simple_launcher.sh` (+23 -0) ➕ `snap/hooks/configure` (+3 -0) ➕ `snap/hooks/install` (+45 -0) ➕ `snap/snapcraft.yaml` (+121 -0) </details> ### 📄 Description As per @kwill 's request in https://github.com/tbraeutigam/gogs-snap/issues/1 and #2539, I modified my gogs-snap to fit with gitea. **Changes to Gitea Code**: * None for actual code * `.gitignore`: Adding a couple of exceptions for snapcraft files that might come up during compilation. **New Files**: * `snap/snapcraft.yaml` The snap package instructions * snap/helpers/simple_launcher.sh A simplistic wrapper for gitea, to fit with the snap environment * snap/helpers/directorySetup.sh Sets up the directories/copied data from r/o `$SNAP` to `$SNAP_DATA` and `$SNAP_COMMON` * snap/helpers/snapApp.ini A few default settings (really 99% of changes are to adjust the paths properly for the Snap environment). **Rationale**: A snap version allows for quick testing and/or easy local hosting on your own machine/own network. The snap does not restrict you from using any of the database options. It defaults to Sqlite3 on the setup page as that is what can be immediately used without further issues from within the snap. **Tested Scenarios**: * Ran through a couple of coming use cases (create repo, issues, clone/pull/push, PR, etc) * Builds fine from current master (Tested on Ubuntu 17.04 and 16.04 LTS) If you do accept the pull-request it would be great if you could set up gitea to be automatically build via https://build.snapcraft.io -- it will allow it to be built on any commit to the master branch (or any other branch you specify). --- <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 2025-11-02 12:11:27 -06:00
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 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#16473
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?