Skip to content

Commit 521a2f8

Browse files
authored
Merge branch 'main' into patch-2
2 parents 01ab4f7 + b644a52 commit 521a2f8

56 files changed

Lines changed: 307741 additions & 4028 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
-3.04 KB
Loading
15.7 KB
Loading
-12.8 KB
Binary file not shown.
-10.9 KB
Binary file not shown.
8.53 KB
Loading

content/admin/configuration/command-line-utilities.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,8 @@ $ ghe-config -l
7474
```
7575
Allows you to find the uuid of your node in `cluster.conf`.
7676

77-
``` shell
78-
$ ghe-config _hostname_.uuid
77+
```shell
78+
$ ghe-config <em>HOSTNAME</em>.uuid
7979
```
8080

8181
{% if currentVersion ver_gt "enterprise-server@2.21" %}
@@ -543,8 +543,8 @@ ghe-dpages status
543543
```
544544

545545
To evacuate a {% data variables.product.prodname_pages %} storage service before evacuating a cluster node:
546-
``` shell
547-
ghe-dpages evacuate pages-server-<uuid>
546+
```shell
547+
ghe-dpages evacuate pages-server-<em>UUID</em>
548548
```
549549

550550
#### ghe-spokes
@@ -569,16 +569,16 @@ ghe-spokes route
569569

570570
To evacuate storage services on a cluster node:
571571

572-
``` shell
573-
ghe-spokes server evacuate git-server-<uuid>
572+
```shell
573+
ghe-spokes server evacuate git-server-<em>UUID</em>
574574
```
575575

576576
#### ghe-storage
577577

578578
This utility allows you to evacuate all storage services before evacuating a cluster node.
579579

580-
``` shell
581-
ghe-storage evacuate storage-server-<uuid>
580+
```shell
581+
ghe-storage evacuate storage-server-<em>UUID</em>
582582
```
583583

584584
### Git

content/admin/configuration/configuring-email-for-notifications.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -44,12 +44,6 @@ settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-all
4444
- In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
4545
- In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
4646

47-
{% note %}
48-
49-
**Note:** If you select the **Send from author** checkbox in a repository’s **Services** email webhook, outbound email for that repository will send from the author and not from the no-reply email address. For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)."
50-
51-
{% endnote %}
52-
5347
6. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**.
5448
![Checkbox to discard emails addressed to the no-reply email address](/assets/images/enterprise/management-console/discard-noreply-emails.png)
5549
7. Under **Support**, choose a type of link to offer additional support to your users:

content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ versions:
1010

1111
### About high availability replication for clusters
1212

13-
You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests without data loss.
13+
You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage.
1414

1515
In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests.
1616

content/admin/overview/managing-your-github-enterprise-license.md

Lines changed: 24 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You can allocate the user licenses included in your {% data variables.product.pr
2424

2525
If your {% data variables.product.prodname_ghe_server %} license expires, you won't be able to access {% data variables.product.product_location_enterprise %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)." If you have any questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}.
2626

27-
### Uploading a new license to {% data variables.product.prodname_ghe_server %}
27+
### Uploading a new license to {% data variables.product.prodname_ghe_server %}
2828

2929
After you purchase a new license or upgrade an existing license from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file, then upload the file to {% data variables.product.prodname_ghe_server %} to unlock your new user licenses.
3030

@@ -45,7 +45,9 @@ If you'd like to renew or add user licenses to {% data variables.product.prodnam
4545
13. To select your license, click **License file**, or drag your license file onto **License file**.
4646
![Upload license file](/assets/images/enterprise/management-console/upload-license.png)
4747
14. Click **Upload**.
48-
![Begin upgrade](/assets/images/enterprise/management-console/begin-upload.png)
48+
![Begin upload](/assets/images/enterprise/management-console/begin-upload.png)
49+
50+
{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)."{% endif %}
4951

5052
### Viewing license usage
5153

@@ -77,3 +79,23 @@ You can download a JSON file from {% data variables.product.prodname_ghe_server
7779
![Upload GitHub Enterprise Servers usage link](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png)
7880
11. Upload the JSON file you downloaded from {% data variables.product.prodname_ghe_server %}.
7981
![Drag and drop or select a file to upload](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png)
82+
83+
{% if currentVersion ver_lt "enterprise-server@3.0" %}
84+
85+
### Troubleshooting
86+
87+
In some scenarios, the web UI for {% data variables.product.prodname_ghe_server %} may not immediately reflect your new license. You can force the system to detect the license by restarting two system services.
88+
89+
{% data reusables.enterprise_installation.ssh-into-instance %}
90+
1. Restart the services for Git authentication and the HTTP server.
91+
92+
{% warning %}
93+
94+
**Warning**: Running the following command will result in a few minutes of user-facing downtime for {% data variables.product.prodname_ghe_server %}. Run the command with care.
95+
96+
{% endwarning %}
97+
98+
sudo systemctl restart github-gitauth github-unicorn
99+
1. After {% data variables.product.prodname_ghe_server %} returns you to a prompt, try accessing {% data variables.product.prodname_ghe_server %} via the command line or web UI again.
100+
101+
{% endif %}

content/admin/user-management/viewing-push-logs.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,17 +22,19 @@ Push log entries show:
2222

2323
### Viewing a repository's push logs
2424

25+
1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator.
2526
1. Navigate to a repository.
26-
{% data reusables.enterprise_site_admin_settings.access-settings %}
27+
1. In the upper-right corner of the repository's page, click {% octicon "rocket" aria-label="The rocket ship" %}.
28+
![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
2729
{% data reusables.enterprise_site_admin_settings.security-tab %}
2830
4. In the left sidebar, click **Push Log**.
2931
![Push log tab](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
3032

3133
{% if enterpriseServerVersions contains currentVersion %}
3234
### Viewing a repository's push logs on the command-line
3335

34-
1. SSH into your appliance. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
35-
2. In the appropriate Git repository, open the audit log file:
36+
{% data reusables.enterprise_installation.ssh-into-instance %}
37+
1. In the appropriate Git repository, open the audit log file:
3638
```shell
3739
ghe-repo <em>owner</em>/<em>repository</em> -c "less audit_log"
3840
```

0 commit comments

Comments
 (0)