In the docs for the rootless image, there is mentioned that you can mount two paths, one for data and one for config mounted at etc/gitea:
docs/blame@d0908137c2/docs/admin/installation/docker.md (L270). Looking at the docs and the container itself, this is the legacy path for configuration which is being removed in the future. So the docs shouldn't give an outdated example.
Wrong example for config path in rootless image #1598
Open
opened 2025年11月22日 18:29:16 +01:00 by micxer
·
2 comments
micxer
commented 2025年11月22日 18:29:16 +01:00
In the docs for the rootless image, there is mentioned that you can mount two paths, one for data and one for config mounted at `etc/gitea`:
https://codeberg.org/forgejo/docs/blame/commit/d0908137c25c9e172fe6af7874987e73c862d8cf/docs/admin/installation/docker.md#L270. Looking at the docs and the container itself, this is the legacy path for configuration which is being removed in the future. So the docs shouldn't give an outdated example.
Gusted
added the 2025年11月28日 07:32:28 +01:00
good first issue
label
Gusted
commented 2025年11月28日 07:33:46 +01:00
The new path is /var/lib/gitea/custom/conf/
The new path is `/var/lib/gitea/custom/conf/`
micxer
commented 2025年12月04日 22:34:16 +01:00
Will send a PR soon.
Will send a PR soon.
Sign in to join this conversation.
No Branch/Tag specified
Labels
Clear labels
Broken links or missing content
Changes which should be backported to the v1.19 docs
Changes which should be backported to the v1.20 docs
Changes which should be backported to the v1.21 docs
Automated backport to v10.0
Automated backport to v11.0
Automated backport to v12.0
Automated backport to v13.0
Automated backport to v14.0
Automated backport to the v7.0 docs
Automated backport to the v8.0 docs
Automated backport to the v9.0 docs
This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
Tooling and processes for maintaining the docs
Content to be added to the documentation
Requires input about accessibility features, likely involves user testing.
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
Instance-wide configuration, authentication and other admin-only needs.
How to deal with errors in the application and write helpful error messages.
How filter and search is being worked with.
The issue might be inspiring for future design work.
AGit, fork-based and new Git workflow, PR creation etc
Active research about Labels
Moderation Featuers for Admins are undergoing active User Research
Use this label to let the User Research team know their input is requested.
Research on how users should know what to do next.
Text rendering, markup languages etc
Active research about the New Repo dialog.
The repo sections, disabling them and the "Add more" button.
How to structure in-app settings in the future?
404
Broken links or missing content
backport/v1.19
Changes which should be backported to the v1.19 docs
Archived
backport/v1.20
Changes which should be backported to the v1.20 docs
Archived
backport/v1.21
Changes which should be backported to the v1.21 docs
Archived
backport/v10.0
Automated backport to v10.0
Archived
backport/v11.0
Automated backport to v11.0
backport/v12.0
Automated backport to v12.0
Archived
backport/v13.0
Automated backport to v13.0
backport/v14.0
Automated backport to v14.0
backport/v7.0
Automated backport to the v7.0 docs
Archived
backport/v8.0
Automated backport to the v8.0 docs
Archived
backport/v9.0
Automated backport to the v9.0 docs
Archived
good first issue
This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta
Tooling and processes for maintaining the docs
new docs
Content to be added to the documentation
Archived
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
No labels
404
backport/v1.19
backport/v1.20
backport/v1.21
backport/v10.0
backport/v11.0
backport/v12.0
backport/v13.0
backport/v14.0
backport/v7.0
backport/v8.0
backport/v9.0
good first issue
meta
new docs
User research - Accessibility
User research - Blocked
User research - Community
User research - Config (instance)
User research - Errors
User research - Filters
User research - Future backlog
User research - Git workflow
User research - Labels
User research - Moderation
User research - Needs input
User research - Notifications/Dashboard
User research - Rendering
User research - Repo creation
User research - Repo units
User research - Security
User research - Settings (in-app)
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
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
forgejo/docs#1598
Loading...
Add table
Add a link
Reference in a new issue
No description provided.
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?