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

Create subdirectory on install process #229

New Issue
Closed
opened 2025-11-02 03:14:45 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 03:14:45 -06:00
Owner
Copy Link

Originally created by @camlafit on GitHub (Jan 13, 2017).

  • Gitea version (or commit ref): 1.0.1
  • Can you reproduce the bug at https://try.gitea.io:
    • [x ] Not relevant
  • Log gist:

Description

During installation, if repository path is two level depth or more, gitea can't create repositories directory. A workaround is to create it before install process.

Should be usefull to allow a recursive mkdir to all directories creation during installation step.

Originally created by @camlafit on GitHub (Jan 13, 2017). - Gitea version (or commit ref): 1.0.1 - Can you reproduce the bug at https://try.gitea.io: - [x ] Not relevant - Log gist: ## Description During installation, if repository path is two level depth or more, gitea can't create repositories directory. A workaround is to create it before install process. Should be usefull to allow a recursive mkdir to all directories creation during installation step.
GiteaMirror added the issue/not-a-bug label 2025-11-02 03:14:45 -06:00
GiteaMirror commented 2025-11-02 03:14:46 -06:00
Author
Owner
Copy Link

@shyim commented on GitHub (Jan 14, 2017):

Gitea creates currently recrusive. https://github.com/go-gitea/gitea/blob/master/routers/install.go#L183
Which os have you tested it?
I have tried on windows and it works correctly.

@shyim commented on GitHub (Jan 14, 2017): Gitea creates currently recrusive. https://github.com/go-gitea/gitea/blob/master/routers/install.go#L183 Which os have you tested it? I have tried on windows and it works correctly.
GiteaMirror commented 2025-11-02 03:14:46 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Jan 16, 2017):

Can somebody verify that it works on linux as expected?

@tboerger commented on GitHub (Jan 16, 2017): Can somebody verify that it works on linux as expected?
GiteaMirror commented 2025-11-02 03:14:46 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Jan 16, 2017):

I would really like to see the logs for this, I'm guessing it's a permission-error.

@bkcsoft commented on GitHub (Jan 16, 2017): I would really like to see the logs for this, I'm guessing it's a permission-error.
GiteaMirror commented 2025-11-02 03:14:46 -06:00
Author
Owner
Copy Link

@camlafit commented on GitHub (Jan 17, 2017):

Hi

I can do a test tomorrow. I use 386 linux binary on jessie.

@camlafit commented on GitHub (Jan 17, 2017): Hi I can do a test tomorrow. I use 386 linux binary on jessie.
GiteaMirror commented 2025-11-02 03:14:47 -06:00
Author
Owner
Copy Link

@Bwko commented on GitHub (Jan 17, 2017):

@tboerger it works as expected on linux. The Gitea installer created this repository path /home/bwko/multiple/levels/deep/some/more/levels/this/works

@Bwko commented on GitHub (Jan 17, 2017): @tboerger it works as expected on linux. The Gitea installer created this repository path `/home/bwko/multiple/levels/deep/some/more/levels/this/works`
GiteaMirror commented 2025-11-02 03:14:47 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Jan 17, 2017):

So maybe it's really just a permission issue?!

@tboerger commented on GitHub (Jan 17, 2017): So maybe it's really just a permission issue?!
GiteaMirror commented 2025-11-02 03:14:47 -06:00
Author
Owner
Copy Link

@camlafit commented on GitHub (Jan 21, 2017):

Hi

Then I redo test following these options.

  • binary path : /var/opt/gitea/gitea
  • execution : su -l git -s /bin/bash -c "/var/opt/gitea/gitea web --config /var/opt/gitea/test/custom/conf/app.ini"
  • repositories path asked : /var/opt/gitea/test/repositories
  • log path asked : /var/opt/gitea/test/log

version 1.0.1
debian jessie 386

And yes looks ok, probaly a mistake from mine, sorry. Maybe as presumed by @tboerger a permission issue on mine previous test.

@camlafit commented on GitHub (Jan 21, 2017): Hi Then I redo test following these options. - binary path : **/var/opt/gitea/gitea** - execution : **su -l git -s /bin/bash -c "/var/opt/gitea/gitea web --config /var/opt/gitea/test/custom/conf/app.ini"** - repositories path asked : **/var/opt/gitea/test/repositories** - log path asked : **/var/opt/gitea/test/log** version 1.0.1 debian jessie 386 And yes looks ok, probaly a mistake from mine, sorry. Maybe as presumed by @tboerger a permission issue on mine previous test.
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 issue/not-a-bug
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#229
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?