Skip to content

Commit e509b38

Browse files
authored
Merge branch 'cloudlinux:master' into master
2 parents 64341cc + d35d28f commit e509b38

File tree

2 files changed

+46
-0
lines changed

2 files changed

+46
-0
lines changed

docs/eportal/README.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -589,6 +589,21 @@ configuration.
589589

590590
![libcare feed](/images/eportal-libcare-feed.png)
591591

592+
### Disable arbitrary patchset
593+
594+
To disable a patchset, run the following command:
595+
596+
```
597+
kc.eportal kcare unroll K20210129_02
598+
```
599+
600+
If you want to remove a patches instead of disabling them, you can use the
601+
`--delete` option:
602+
603+
```
604+
kc.eportal kcare unroll K20210129_02 --delete
605+
```
606+
592607
### CLI to install the latest patchsets
593608

594609
To update the default feed, run the following command:

docs/radar/README.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,37 @@ For running manually, you may need to set it in the user profile like so (or sim
9999
echo "export https_proxy=http://proxy.domain.com:port" > /etc/profile.d/proxy.sh
100100
```
101101

102+
## Proxying via ePortal
103+
104+
If you are an [ePortal](/eportal) user, you can proxy Radar via ePortal instead of configuring a dedicated proxy as above.
105+
106+
In /etc/tuxcare-radar/radar.yaml change the `base-url` to point to your eportal server with a trailing `/radar`, for example:
107+
108+
```text
109+
#base-url: https://radar.tuxcare.com
110+
base-url: https://eportal.example.com/radar
111+
```
112+
113+
Then on your ePortal server, update /etc/eportal/config with the following:
114+
115+
```text
116+
RADAR_PROXY_ENABLE = True
117+
```
118+
119+
Then restart ePortal:
120+
121+
```text
122+
systemctl restart eportal
123+
```
124+
125+
When it is working, you will see messages like the following, mentioning the ePortal URL in /var/log/tuxcare-radar/radar.log on your TuxCare Radar client:
126+
127+
```text
128+
radar INFO: fetching oval file from https://eportal.example.com/radar/oval/alma/9.5?fips=false&oval=0
129+
radar INFO: fetching oval file from https://eportal.example.com/radar/oval/alma/9.5?fips=false&oval=1
130+
radar INFO: sending output to https://eportal.example.com/radar
131+
```
132+
102133
## Usage
103134

104135
The installer should have created an /etc/cron.d/tuxcare-radar file that will run from a randomized time every 6 hours, it will check if a scan has been run in the last 23 hours (`time-between-runs` in radar.yaml) and if not, it will run a scan.

0 commit comments

Comments
 (0)