forgejo/docs
31
58
Fork
You've already forked docs
249

admin: installation: remote data folder (#193) #194

Merged
earl-warren merged 1 commit from pr/v1.21/admin/installation into v1.21 2023年10月15日 14:49:26 +02:00
Contributor
Copy link

Preview: https://forgejo.codeberg.page/@docs_pull_194/docs/next/admin/installation/#hosting-repository-data-on-remote-storage-systems

Documentation proposal for remote data mounting, following up from forgejo/forgejo#1590

Co-authored-by: Daniel Bischof daniel.bischof@protonmail.com
Reviewed-on: #193
Reviewed-by: Earl Warren earl-warren@noreply.codeberg.org
Co-authored-by: dbischof90 dbischof90@noreply.codeberg.org
Co-committed-by: dbischof90 dbischof90@noreply.codeberg.org
(cherry picked from commit cabb9fca11)

Preview: https://forgejo.codeberg.page/@docs_pull_194/docs/next/admin/installation/#hosting-repository-data-on-remote-storage-systems Documentation proposal for remote data mounting, following up from https://codeberg.org/forgejo/forgejo/issues/1590 Co-authored-by: Daniel Bischof <daniel.bischof@protonmail.com> Reviewed-on: https://codeberg.org/forgejo/docs/pulls/193 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: dbischof90 <dbischof90@noreply.codeberg.org> Co-committed-by: dbischof90 <dbischof90@noreply.codeberg.org> (cherry picked from commit cabb9fca11e0babcae88f365ce669d5159bc3e67)
admin: installation: remote data folder ( #193 )
All checks were successful
pr / preview (pull_request) Successful in 1m2s
backport / backport (pull_request) Successful in 2s
push / publish (push) Successful in 13s
c9ee7d39e4
Documentation proposal for remote data mounting, following up from forgejo/forgejo#1590
Co-authored-by: Daniel Bischof <daniel.bischof@protonmail.com>
Reviewed-on: #193
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: dbischof90 <dbischof90@noreply.codeberg.org>
Co-committed-by: dbischof90 <dbischof90@noreply.codeberg.org>
(cherry picked from commit cabb9fca11)
Collaborator
Copy link
Preview ready: https://forgejo.codeberg.page/@docs_pull_194/
Contributor
Copy link

Preview ready: https://forgejo.codeberg.page/@docs_pull_194/

Is your bot working correctly? This link does not contain my changes... only the one @earl-warren posted.

> Preview ready: https://forgejo.codeberg.page/@docs_pull_194/ Is your bot working correctly? This link does not contain my changes... only the one @earl-warren posted.
Author
Contributor
Copy link

https://forgejo.codeberg.page/@docs_pull_194/docs/next/admin/installation/#hosting-repository-data-on-remote-storage-systems it shows but you have to navigate to find it. The link I posted also works but is not canonical.

https://forgejo.codeberg.page/@docs_pull_194/docs/next/admin/installation/#hosting-repository-data-on-remote-storage-systems it shows but you have to navigate to find it. The link I posted also works but is not canonical.
Contributor
Copy link

I have another detail, maybe it’s faster for you to change: in the NFS server setting it has to be [...],sec=sys instead of [...],ec=sys:

Correct entry should be

[...]
/repositories	*(rw,sync,all_squash,sec=sys,anonuid=1024,anongid=100)
I have another detail, maybe it’s faster for you to change: in the NFS server setting it has to be `[...],sec=sys` instead of `[...],ec=sys`: Correct entry should be ```shell [...] /repositories *(rw,sync,all_squash,sec=sys,anonuid=1024,anongid=100) ```
rome-user left a comment
Copy link

Only one major issue, but the rest of my comments are nitpicks.

Only one major issue, but the rest of my comments are nitpicks.
@ -149,0 +195,4 @@
$ mkdir data
```
To consider in the client setup is the `hard` setting, blocking all file operations if the share is not available.
First-time contributor
Copy link

I don't understand the first part of this sentence. Does "in the client setup" mean "in-the-client setup" or something else?

I don't understand the first part of this sentence. Does "in the client setup" mean "in-the-client setup" or something else?
rome-user marked this conversation as resolved
@ -149,0 +199,4 @@
This prevents state changes in the repository which could potentially corrupt the repository data and is an NFS-specific setting.
To circumvent this, you can use the
We will use the `rootless` image, which hosts the `ssh` server for Forgejo embedded. A possible entry for a `docker-compose` file
First-time contributor
Copy link

On the rendered site, this appears as:

To circumvent this, you can use the We will use the rootless image, ...

I think we can delete line 201 given the NFS mount above.

On the rendered site, this appears as: > To circumvent this, you can use the We will use the `rootless` image, ... I think we can delete line 201 given the NFS mount above.
rome-user marked this conversation as resolved
@ -149,0 +227,4 @@
- - ./forgejo:/var/lib/gitea
+ - /mnt/repositories/data:/var/lib/gitea
+ - /mnt/repositories/conf:/etc/gitea
- /etc/timezone:/etc/timezone:ro
First-time contributor
Copy link

The diff is subtly incorrect in services.volumes. There are no whitespace changes in e.g. services.server.image, but there are here.

The diff is subtly incorrect in `services.volumes`. There are no whitespace changes in e.g. `services.server.image`, but there are here.
rome-user marked this conversation as resolved
@ -149,0 +247,4 @@
Note that this is a comparatively simple setup which does not necessarily reflect the reality of your network.
User mapping and ownership could theoretically be streamlined better with Kerberos, which is however out of scope
for this guide.
First-time contributor
Copy link

I recommend simplifying this to

Note this setup is simple and does not necessarily reflect the reality of your network. User mapping and ownership could be streamlined better with Kerberos, but that is out of the scope of this guide.

I recommend simplifying this to > Note this setup is simple and does not necessarily reflect the reality of your network. User mapping and ownership could be streamlined better with Kerberos, but that is out of the scope of this guide.
rome-user marked this conversation as resolved
Ghost approved these changes 2023年10月15日 14:41:26 +02:00
Author
Contributor
Copy link

Since this is a backport, I opened another PR at #195 with the suggested modifications, for discussion also. 👍

Since this is a backport, I opened another PR at https://codeberg.org/forgejo/docs/pulls/195 with the suggested modifications, for discussion also. 👍
earl-warren deleted branch pr/v1.21/admin/installation 2023年10月15日 14:49:26 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
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

Archived

backport/v14.0
Automated backport to v14.0

Archived

backport/v15.0
Automated backport to v15.0
backport/v16.0
Automated backport to v16.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?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 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!194
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "pr/v1.21/admin/installation"

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?