Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitd52d239

Browse files
authored
docs: fix link to CODER_QUIET_HOURS_DEFAULT_SCHEDULE in schedule doc (#16545)
Corrects incorrect reference to env variable`CODER_DEFAULT_QUIET_HOURS_SCHEDULE`. Changes to`CODER_QUIET_HOURS_DEFAULT_SCHEDULE`. Also hyperlinks to the server flag(similar to `CODER_ALLOW_CUSTOM_QUIET_HOURS`)
1 parentea1358c commitd52d239

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎docs/admin/templates/managing-templates/schedule.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ stopped due to the policy at the start of the user's quiet hours.
122122
![User schedule settings](../../../images/admin/templates/schedule/user-quiet-hours.png)
123123

124124
Admins can define the default quiet hours for all users with the
125-
`--default-quiet-hours-schedule` flag or`CODER_DEFAULT_QUIET_HOURS_SCHEDULE`
125+
[CODER_QUIET_HOURS_DEFAULT_SCHEDULE](../../../reference/cli/server.md#--default-quiet-hours-schedule)
126126
environment variable. The value should be a cron expression such as
127127
`CRON_TZ=America/Chicago 30 2 * * *` which would set the default quiet hours to
128128
2:30 AM in the America/Chicago timezone. The cron schedule can only have a

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp