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

WIP: FILE_NAME in the configuration file defaults to forgejo.log #2018

Draft
limiting-factor wants to merge 1 commit from limiting-factor/docs:wip-log into next
pull from: limiting-factor/docs:wip-log
merge into: forgejo:next
forgejo:next
forgejo:v15.0
forgejo:v16.0
forgejo:bp-v15.0-a25e0a3
forgejo:v11.0
forgejo:bp-v15.0-c7697f2
forgejo:actions-remove-non-existing-strategy-options
forgejo:v14.0
forgejo:v13.0
forgejo:v12.0
forgejo:v7.0
forgejo:v10.0
forgejo:v9.0
forgejo:v8.0
forgejo:v1.21
forgejo:v1.20
forgejo:v1.19

This must not be merged before forgejo/forgejo!13035 is merged 🙏

This must not be merged before forgejo/forgejo!13035 is merged 🙏
FILE_NAME in the configuration file defaults to forgejo.log
All checks were successful
pr / preview (pull_request) Successful in 1m24s
e060170875
 
Refs forgejo/forgejo!13035
Preview ready:
<!--PR-PREVIEW-MARKER-->Preview ready: - https://forgejo.preview.codeberg.page/docs@2018/docs/next/admin/troubleshooting/logging/#set-different-log-levels-for-different-modes - https://forgejo.preview.codeberg.page/docs@2018/docs/next/admin/config-cheat-sheet/#file-log-mode-logfile-or-modefile
Author
Member
Copy link

@clouds666 as suggested in the pull request. It also fixes a bug: the current documentation claims forgejo.log is the default although it really is gitea.log.

@clouds666 as suggested in the pull request. It also fixes a bug: the current documentation claims `forgejo.log` is the default although it really is `gitea.log`.
@ -937,1 +937,3 @@
- `FILE_NAME`: Set the file name for this logger. Defaults to `forgejo.log` (exception: access log defaults to `access.log`). If relative, it will be relative to the `ROOT_PATH`.
See the [file mode section in the logging documentation](../troubleshooting/logging/#file-mode).
- `FILE_NAME`: Set the file name for this logger. Defaults to `forgejo.log`.
Member
Copy link

good catch. I would have missed it by just searching the docs for occurrences ^^

The link is a nice addition. I like how it is similar to the section above on the journald mode

good catch. I would have missed it by just searching the docs for occurrences ^^ The link is a nice addition. I like how it is similar to the section above on the journald mode
Author
Member
Copy link

I copy/pasted it 😊

I copy/pasted it 😊
limiting-factor marked this conversation as resolved
All checks were successful
pr / preview (pull_request) Successful in 1m24s
Required
Details
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u wip-log:limiting-factor-wip-log
git switch limiting-factor-wip-log
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
3 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!2018
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "limiting-factor/docs:wip-log"

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?