You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -243,6 +245,11 @@ This works by monitoring the project for changes, running the `preview:build` ta
243
245
244
246
Press kbd:[Ctrl+C] to stop the preview server and end the continuous build.
245
247
248
+
[NOTE]
249
+
====
250
+
Opening or updating a pull request against the `main` branch triggers an automatic `gulp preview` deployment to GitHub Pages so that reviewers can view your latest changes without having to run the preview locally.
251
+
====
252
+
246
253
[#create-bundle]
247
254
=== Package for use with Antora
248
255
@@ -267,6 +274,12 @@ gulp bundle:pack
267
274
268
275
The UI bundle will again be available at [.path]_build/ui-bundle.zip_.
269
276
277
+
[NOTE]
278
+
====
279
+
UI bundles for the DataStax documentation site are automatically published via automation.
280
+
See <<automatic-ui-release>>.
281
+
====
282
+
270
283
==== Source maps
271
284
272
285
The build consolidates all the CSS and client-side JavaScript into combined files, [.path]_site.css_ and [.path]_site.js_, respectively, in order to reduce the size of the bundle.
@@ -288,67 +301,28 @@ In this case, the bundle will include the source maps, which can be used for deb
288
301
289
302
==== Using TailwindCSS
290
303
291
-
This project uses TailwindCSS. To learn more see xref:{url-tailwind-readme}[TailwindCSS README].
304
+
This project uses TailwindCSS.
305
+
To learn more see xref:{url-tailwind-readme}[TailwindCSS README].
292
306
293
-
== Release the UI bundle
307
+
[#automatic-ui-release]
308
+
== Automatic UI bundle release
294
309
295
310
Once you're satisfied with the changes you've made to the UI, you'll need to open a pull request to merge your changes into the `main` branch.
296
-
After your changes have been reviewed and merged, you can then choose to make those changes available in the production UI by publishing a new release to this repository and attaching the latest `ui-bundle.zip` file.
311
+
Upon merging a pull request into `main`, the following automation occurs:
297
312
298
-
=== Bundle release procedure
313
+
. A new UI bundle is built using `gulp bundle` (linting also occurs during this step).
299
314
300
-
. Start by making sure you've completed the <<prerequisites>>.
315
+
. Assuming a successful build, a new tag is applied to the latest commit (incremented from the previous `prod-#` tag).
301
316
302
-
. Create the release commit.
303
-
+
304
-
Edit https://github.com/riptano/docs-ui/blob/bdf6484e46f41cff17238a7ef5aeae5368622d2c/README.adoc?plain=1#L3[README.adoc] directly in GitHub and increment the `:current-release:` attribute to the next version number.
305
-
+
306
-
[source,asciidoc]
307
-
----
308
-
:current-release: prod-* <.>
309
-
----
310
-
<.> Add +1 to the version number
311
-
+
312
-
This should be the only change in the commit, and the commit message should take the form of *Release prod-*.
313
-
If you have Admin privileges to the repository, you can commit the changes directly to `main`.
314
-
Otherwise, you'll need to open a PR.
317
+
. A new `prod-#` {url-project}/releases[release] is published with auto-generated release notes and the UI bundle release asset.
315
318
316
-
. Once the release commit is merged, open your local copy of the repository in a terminal and retrieve the latest changes from `main`.
317
-
+
318
-
[source,shell]
319
-
----
320
-
git switch main && git pull
321
-
----
322
-
323
-
. Pack the UI bundle as described in <<create-bundle>>.
324
-
+
325
-
[source,shell]
326
-
----
327
-
gulp bundle
328
-
----
329
-
330
-
. Create a new release (see {url-create-release}[GitHub documentation]).
331
-
.. Create a new tag named after the new version (e.g., `prod-2`).
332
-
The tag needs to target the `main` branch.
333
-
.. Make sure the *Title* of the release is the same name as the tag.
334
-
(The release title and the tag name should always be made the same, as it makes releases easier to identify.)
335
-
.. Instead of manually adding a description for the release, just click *Generate release notes*.
336
-
This automatically adds a description that highlights the functional changes that have been added since the last release.
337
-
.. Attach the UI bundle (`ui-bundle.zip`) as a release asset.
338
-
.. (Optional) Check the box labeled *This is a pre-release* if you don't want the release to be generally available.
339
-
+
340
-
Selecting this option is helpful if you want to publish a new UI bundle for testing purposes.
341
-
You can edit the release later to remove the *Pre-release* label if desired.
342
-
.. When you're ready, publish the release.
343
-
344
-
Once the new release is published, the attached bundle can then be downloaded from the repository using a unique URL found on the {url-project}/releases[releases page].
345
-
346
-
[IMPORTANT]
319
+
[TIP]
347
320
====
348
-
All production builds of the DataStax docs are configured to pull the latest, _non-pre-release_ UI bundle.
349
-
Once you've publish a new release, all subsequent site builds that use the configuration described in <<use-the-ui>> will consume the new UI bundle.
321
+
If you don't want your pull request to trigger an automatic release, e.g. you're only making updates to the README or `preview-src` files, you can skip the automation by including `[no-release]` in the commit message.
350
322
====
351
323
324
+
Once the release is published, you can apply it by updating your Antora playbook to point to the new UI bundle URL.
325
+
To apply it to the DataStax documentation site, you'll need to update the playbook in the {url-datastax-docs-repo}[datastax-docs-site] repository.
Monospace text formatting is typically used to represent text shown in `computer terminals` or `code editors` (often referred to as a codespan).
@@ -93,13 +95,17 @@ Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor i
93
95
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
94
96
----
95
97
96
-
=== Text formatting
98
+
=== Text formatting (variables)
97
99
98
-
[source,bash,subs="quotes"]
100
+
[source,sql,subs="verbatim,quotes"]
99
101
----
100
-
cd /Users/*_your-name_*/repos/astra-vector-docs/build/site
102
+
DESCRIBE **KEYSPACE_NAME**.**TABLE_NAME**
101
103
----
102
104
105
+
Replace the following:
106
+
107
+
* *`KEYSPACE_NAME`*: The name of the keyspace that contains the table you want to migrate.
108
+
* *`TABLE_NAME`*: The name of the table that contains the data you want to migrate.
DataStax Astra is a cutting-edge cloud-native database platform designed to empower developers.
6
8
Harnessing the strengths of vector databases, serverless computing, and real-time streaming, Astra propels application development into the next generation.
0 commit comments