Skip to content

Commit ec4cb40

Browse files
committed
docs: fix alerts
1 parent 4e9facb commit ec4cb40

File tree

4 files changed

+10
-19
lines changed

4 files changed

+10
-19
lines changed

docs/content/1.getting-started/1.index.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -55,16 +55,14 @@ The database driver to use for storing cache metadata. For more information, see
5555

5656
If set to `true`, will send a signed URL to the runner. The runner can then download the cache directly from the storage provider. This is useful if you have a large cache and don't want to proxy the download through the cache server.
5757

58-
## ::u-alert
59-
58+
::u-alert
59+
---
6060
icon: 'tabler:alert-triangle'
6161
class: ring-amber-400
6262
color: amber
6363
description: The actions runner needs to be able to reach the storage provider directly to use direct downloads.
6464
variant: subtle
65-
6665
---
67-
6866
::
6967

7068
#### `CLEANUP_OLDER_THAN_DAYS`
@@ -89,16 +87,14 @@ To leverage the GitHub Actions Cache Server with your self-hosted runners, you'l
8987

9088
For example, if your cache server's `API_BASE_URL` is `http://localhost:3000` and your `URL_ACCESS_TOKEN` is `random_token`, you would set `ACTIONS_CACHE_URL` to `http://localhost:3000/random_token/`.
9189

92-
## ::u-alert
93-
90+
::u-alert
91+
---
9492
icon: 'tabler:alert-triangle'
9593
class: ring-amber-400
9694
color: amber
9795
description: Make sure to add a trailing slash to the ACTIONS_CACHE_URL environment variable.
9896
variant: subtle
99-
10097
---
101-
10298
::
10399

104100
### Getting the Actions Runner to Use the Cache Server

docs/content/2.storage-drivers/gcs.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,16 +7,14 @@ Driver: `gcs`
77

88
This storage driver stores the cache in a GCS bucket.
99

10-
## ::u-alert
11-
10+
::u-alert
11+
---
1212
icon: 'tabler:alert-triangle'
1313
class: ring-amber-400
1414
color: amber
1515
description: Because GCS doesn't support out-of-order multipart uploads (as of November 2024), the cache server will upload the parts into a temporary folder. To combine the parts into a single object, it will download all the parts and re-upload the combined object. This means using GCS as your storage driver will use 3x the bandwidth compared to other storage drivers.
1616
variant: subtle
17-
1817
---
19-
2018
::
2119

2220
## Configuration

docs/content/3.database-drivers/sqlite.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,14 @@ description:
55

66
Driver: `sqlite`
77

8-
## ::u-alert
9-
8+
::u-alert
9+
---
1010
icon: 'tabler:alert-triangle'
1111
class: ring-amber-400
1212
color: amber
1313
description: It is recommended to use a more robust database driver for production use.
1414
variant: subtle
15-
1615
---
17-
1816
::
1917

2018
## Configuration

docs/nuxt.config.ts

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
import wasm from 'vite-plugin-wasm'
22

33
export default defineNuxtConfig({
4+
compatibilityDate: '2024-11-20',
45
extends: ['@nuxt/ui-pro'],
56
modules: ['@nuxt/content', '@nuxt/ui', '@nuxt/fonts', '@nuxthq/studio'],
67
hooks: {
@@ -41,9 +42,7 @@ export default defineNuxtConfig({
4142
routes: ['/'],
4243
},
4344
},
44-
ui: {
45-
icons: ['ph', 'simple-icons'],
46-
},
45+
ui: {},
4746
content: {
4847
highlight: {
4948
langs: [

0 commit comments

Comments
 (0)