32
41
Fork
You've already forked website
53

admin: Database Preparation #167

Merged
Ghost merged 3 commits from :wip-database into main 2023年03月09日 10:29:31 +01:00
No description provided.
Collaborator
Copy link

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

Preview ready: https://forgejo.codeberg.page/@pull_167/
earl-warren left a comment
Copy link

https://forgejo.codeberg.page/@pull_167/docs/v1.19/admin/database-preparation/ looks ok and is linked from the TOC

https://forgejo.codeberg.page/@pull_167/docs/v1.19/admin/database-preparation/ looks ok and is linked from the TOC
@ -0,0 +27,4 @@
Enter the password as prompted.
3. Create database user which will be used by Forgejo, authenticated by password. This example uses `'forgejo'` as password. Please use a secure password for your instance.
Contributor
Copy link

By choosing this password it is not obvious which value represents the user and which the password in the code examples below.

By choosing this password it is not obvious which value represents the user and which the password in the code examples below.
@ -0,0 +167,4 @@
- You need two valid TLS certificates, one for the database instance (database server) and one for the Forgejo instance (database client). Both certificates must be signed by a trusted CA.
- The database certificate must contain `TLS Web Server Authentication` in the `X509v3 Extended Key Usage` extension attribute, while the client certificate needs `TLS Web Client Authentication` in the corresponding attribute.
- On the database server certificate, one of `Subject Alternative Name` or `Common Name` entries must be the fully-qualified domain name (FQDN) of the database instance (e.g. `db.example.com`). On the database client certificate, one of the entries mentioned above must contain the database username that Forgejo will be using to connect.
Contributor
Copy link

Isn't the dot at the end required for a FQDN?
I fail to see it in the example.

Isn't the dot at the end required for a FQDN? I fail to see it in the example.

It is not required.

It is not required.
Ghost marked this conversation as resolved
@ -0,0 +205,4 @@
hostssl forgejodb forgejo 192.0.2.10/32 scram-sha-256 clientcert=verify-full
```
For PostgreSQL 11 and earlier:
Contributor
Copy link

Do we need that „and earlier" here?

According to https://www.postgresql.org/support/versioning/ only v11 is still supported.

Do we need that „and earlier" here? According to https://www.postgresql.org/support/versioning/ only v11 is still supported.
Ryuno-Ki left a comment
Copy link

One tiny update then this should be good to go.

One tiny update then this should be good to go.
@ -0,0 +240,4 @@
### MySQL
While the MySQL driver used by Forgejo also supports two-way TLS, Forgejo currently supports only one-way TLS. See issue #10828 for details.
Contributor
Copy link

The issue link must be adapted to point to GitHub here.

The issue link must be adapted to point to GitHub here.

Good catch, fixed.

Good catch, fixed.
Ghost marked this conversation as resolved

Addressed two review comments and moved two others to a separate issue to improve the content of this page since this PR is about importing it rather than improve it.

#170

Is that ok?

Addressed two review comments and moved two others to a separate issue to improve the content of this page since this PR is about importing it rather than improve it. https://codeberg.org/forgejo/website/issues/170 Is that ok?
Ghost force-pushed wip-database from a59bbfa57e
All checks were successful
forgejo-ci/pr/woodpecker Pipeline was successful
to 6d5aba5381
All checks were successful
forgejo-ci/pr/woodpecker Pipeline was successful
2023年03月09日 07:34:11 +01:00 Compare
Ryuno-Ki left a comment
Copy link

Safe enough.

Safe enough.
Ghost deleted branch wip-database 2023年03月09日 10:29:31 +01:00
Sign in to join this conversation.
Labels
Clear labels
404
Broken links or missing content
Accessibility
Accessibility
Blog post
Documentation
Forgejo Documentation
Internationalisation
i18n and l10n
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
4 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/website!167
Reference in a new issue
forgejo/website
No description provided.
Delete branch ":wip-database"

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?