Skip to content

Commit 2ddf31b

Browse files
committed
TCE-4760 feat(byoc): update directory and wordings
2 parents c7c85d9 + 2d82244 commit 2ddf31b

File tree

484 files changed

+7197
-2390
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

484 files changed

+7197
-2390
lines changed

README.adoc

+53-1
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,56 @@ This repository only contains the source files for the published documentation.
66
To view the published version, see link:https://docs.tigergraph.com/cloud[TigerGraph Cloud Documentation].
77

88
== Contribution
9-
For instructions on how to contribute to this repository, see link:https://github.com/tigergraph/doc-site/blob/main/contribution.adoc[Contribution guidelines].
9+
For instructions on how to contribute to this repository, see link:https://github.com/tigergraph/doc-site/blob/main/contribution.adoc[Contribution guidelines].
10+
11+
== Install dependencies
12+
To install dependencies, navigate to this repository and run:
13+
[,console]
14+
----
15+
npm install
16+
----
17+
18+
== Build site locally
19+
To build the site locally, run:
20+
[,console]
21+
----
22+
npm run build
23+
----
24+
The build will be available in the `build/` folder in the root directory.
25+
26+
IMPORTANT: Though the files are all in the `/build` folder, you won't be able to access other pages through the links if the files are not served by a server.
27+
To preview locally, you can <<Run a local server to view the build>>. If you really don't want to use a local server, edit the `antora-playbook.yml` file in your local environment, and change the `html_extension_style` under `urls` to `default`. This allows you to open the static files and have the links work.
28+
29+
=== Build from your local content source repository
30+
To have Antora build the site from your local content source repository, change the corresponding content source in the file `antora-playbook.yml` to point to your local git repository.
31+
32+
See https://docs.antora.org/antora/2.3/playbook/content-source-url/#local-urls[Use local content repositories] on Antora's documentation.
33+
34+
== Watch Mode
35+
36+
Watch Mode launches a local web server for preview. It will continue watching your local content source repository changes and rebuild the site.
37+
38+
[,console]
39+
----
40+
npm run dev
41+
----
42+
43+
You can access the web server at http://localhost:5000[http://localhost:5000].
44+
45+
== Run a local server to view the build
46+
47+
To open the build, run:
48+
[,console]
49+
----
50+
$ npm i -g http-server
51+
$ http-server build/site -c-1
52+
----
53+
Upon launching the command, the local address of the web server will be displayed in your terminal. You should see the following output in your terminal:
54+
55+
----
56+
Starting up http-server, serving build/site
57+
Available on:
58+
http://127.0.0.1:8080
59+
http://192.168.1.8:8080
60+
Hit CTRL-C to stop the server
61+
----

antora-playbook.yml

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
site:
2+
title: "Cloud Doc Test"
3+
start_page: "cloud4:overview:index.adoc"
4+
5+
content:
6+
sources:
7+
- url: .
8+
branches: HEAD
9+
start_paths: [modules/cloud4, modules/cloud]
10+
11+
output:
12+
dir: ./build/site
13+
14+
ui:
15+
bundle:
16+
url: https://github.com/tigergraph/antora-ui/blob/main/build/ui-bundle.zip?raw=true
17+
snapshot: true

gulpfile.js

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
'use strict'
2+
3+
const connect = require('gulp-connect')
4+
const fs = require('fs')
5+
const generator = require('@antora/site-generator-default')
6+
const { reload: livereload } = process.env.LIVERELOAD === 'true' ? require('gulp-connect') : {}
7+
const { series, src, watch } = require('gulp')
8+
const yaml = require('js-yaml')
9+
10+
const playbookFilename = 'antora-playbook.yml'
11+
const playbook = yaml.load(fs.readFileSync(playbookFilename, 'utf8'))
12+
const outputDir = (playbook.output || {}).dir || './build/site'
13+
const serverConfig = { name: 'Preview Site', livereload, port: 5000, root: outputDir }
14+
const antoraArgs = ['--playbook', playbookFilename]
15+
const watchPatterns = playbook.content.sources.filter((source) => !source.url.includes(':')).reduce((accum, source) => {
16+
accum.push(`${source.url}/${source.start_path ? source.start_path + '/' : ''}antora.yml`)
17+
accum.push(`${source.url}/${source.start_path ? source.start_path + '/' : ''}**/*.adoc`)
18+
return accum
19+
}, [])
20+
21+
function generate (done) {
22+
generator(antoraArgs, process.env)
23+
.then(() => done())
24+
.catch((err) => {
25+
console.log(err)
26+
done()
27+
})
28+
}
29+
30+
function serve (done) {
31+
connect.server(serverConfig, function () {
32+
this.server.on('close', done)
33+
watch(watchPatterns, generate)
34+
if (livereload) watch(this.root).on('change', (filepath) => src(filepath, { read: false }).pipe(livereload()))
35+
})
36+
}
37+
38+
module.exports = { serve, generate, default: series(generate, serve) }

modules/cloud/antora.yml

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
name: cloud
2-
title: TigerGraph Cloud
3-
version: master
4-
display_version: default
2+
title: TigerGraph Cloud Classic
53
start_page: start:overview.adoc
4+
version: main
5+
display_version: default
66

77
nav:
88
- modules/start/nav.adoc

modules/cloud/modules/solutions/pages/access-solution/graphstudio.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,6 @@ image::full-cluster-actions-dropdown.png[]
1616

1717
== Use GraphStudio
1818

19-
To learn how to use GraphStudio, read our xref:gui:graphstudio:overview.adoc[GraphStudio UI Guide].
19+
To learn how to use the GraphStudio™ design interface, read our xref:gui:graphstudio:overview.adoc[GraphStudio UI Guide].
2020

2121

modules/cloud/modules/start/pages/get_started.adoc

+17-67
Original file line numberDiff line numberDiff line change
@@ -54,71 +54,21 @@ For advanced OS-level commands, submit a support ticket for more information.
5454
|===
5555
| Topic | TigerGraph Enterprise Server | TigerGraph Cloud
5656

57-
| GSQL Graph Algorithm Library
58-
| Yes
59-
| Yes
60-
61-
| Release Notes
62-
| Yes
63-
| TigerGraph Cloud provides database versions kept up to date with TigerGraph Server releases.
64-
65-
| GSQL 101
66-
| Yes
67-
| Basic concepts still apply, most CREATE, INSTALL, LOAD, and RUN commands are replaced with the GraphStudio GUI-based approach.
68-
69-
| GSQL 102 Pattern Matching
70-
| Yes
71-
| The same patterns can be used in queries.
72-
73-
| MultiGraph Overview
74-
| Yes
75-
| Yes
76-
77-
| Hardware and Software Requirements
78-
| Yes
79-
| N/A
80-
81-
| Installation and Configuration
82-
| Yes
83-
| N/A. There are a few simple steps to install a Starter Kit. See the TigerGraph Cloud FAQs.
84-
85-
| User Access Management
86-
| Yes
87-
| Yes
88-
89-
| Data Encryption
90-
| Yes
91-
| N/A. TigerGraph Cloud is setup already for encrypted data at rest and at motion.
92-
93-
| System Management
94-
| Yes
95-
| The Cloud Admin Portal is enhanced over the TigerGraph Server Admin Portal. Backup and Restore is done through the Cloud Admin Portal.
96-
97-
| GraphStudio UI Guide
98-
| Yes
99-
| Yes
100-
101-
| GSQL Demo Examples
102-
| Yes
103-
| Yes
104-
105-
| GSQL Language Reference, Part 1 Data Definition and Loading
106-
| Yes
107-
| Yes. GSQL Web Shell (Paid Tiers) supports Data Definition and Loading. Data files can be imported into the filesystem through GraphStudio, or submit support request to import into the filesystem. In addition, the operations can be performed through the GraphStudio user interface.
108-
109-
| GSQL Language Reference, Part 2 Querying
110-
| Yes
111-
| Yes
112-
113-
| RESTPP API User Guide
114-
| Yes
115-
| Yes. Note the URL assigned to your cluster.
116-
117-
| Transaction Processing and ACID Support
118-
| Yes
119-
| Yes
120-
121-
| Data Loader User Guides
122-
| Yes
123-
| S3 Loader can be used through the GraphStudio interface. In addition, S3 Loader and Kafka Loader can be used in GSQL Web Shell (Paid Tiers).
57+
| GSQL Graph Algorithm Library | Yes | Yes
58+
| Release Notes | Yes | TigerGraph Cloud keeps its database instances up to date with the latest TigerGraph Server releases.
59+
| GSQL 101 | Yes | Basic concepts still apply. Most CREATE, INSTALL, LOAD, and RUN commands are replaced with the GraphStudio GUI-based approach.
60+
| GSQL 102 Pattern Matching | Yes | The same patterns can be used in queries.
61+
| MultiGraph Overview | Yes | Yes
62+
| Hardware and Software Requirements | Yes | N/A
63+
| Installation and Configuration | Yes | N/A. There are a few simple steps to install a Starter Kit. See the TigerGraph Cloud FAQs.
64+
| User Access Management | Yes | Yes
65+
| Data Encryption | Yes | N/A. TigerGraph Cloud is setup already for encrypted data at rest and at motion.
66+
| System Management | Yes | The Cloud Admin Portal is enhanced over the TigerGraph Server Admin Portal. Backup and Restore is done through the Cloud Admin Portal.
67+
| GraphStudio UI Guide | Yes | Yes
68+
| GSQL Demo Examples | Yes | Yes
69+
| GSQL Language Reference, Part 1 Data Definition and Loading| Yes | Yes. GSQL Web Shell (Paid Tiers) supports Data Definition and Loading. Data files can be imported into the filesystem through GraphStudio, or submit support request to import into the filesystem. In addition, the operations can be performed through the GraphStudio user interface.
70+
| GSQL Language Reference, Part 2 Querying | Yes | Yes
71+
| RESTPP API User Guide | Yes | Yes. Note the URL assigned to your cluster.
72+
| Transaction Processing and ACID Support | Yes | Yes
73+
| Data Loader User Guides | Yes | S3 Loader can be used through the GraphStudio interface. In addition, S3 Loader and Kafka Loader can be used in GSQL Web Shell (Paid Tiers).
12474
|===

modules/cloud/modules/start/pages/overview.adoc

+10-5
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,25 @@
1-
= TigerGraph Cloud
1+
= TigerGraph Cloud Classic
22
:experimental:
33
:page-aliases: cloud-overview.adoc
44

5+
56
TigerGraph Cloud is a fully-managed cloud database built on the Enterprise Server engine and completely integrated with the full TigerGraph Suite.
67

78
Everything including xref:3.9@gui:admin-portal:overview.adoc[Admin Portal], xref:3.9@gui:graphstudio:overview.adoc[GraphStudio], xref:3.9@insights:intro:index.adoc[Insights], xref:1.4@ml-workbench:intro:index.adoc[ML Workbench], as well as,
89
handling all the complexity of deploying and managing your deployments on the cloud service provider of your choice ( xref:cloud:reference:aws.adoc[], xref:cloud:reference:azure.adoc[], and xref:cloud:reference:gcp.adoc[] ).
910

1011
[NOTE]
1112
====
12-
TigerGraph Cloud 4.0 (beta version) was released on Apr. 29th, 2024.
13+
TigerGraph Savanna Beta was released on Apr. 29, 2024.
1314
14-
Check out the new Cloud 4.0 beta at https://beta.tgcloud.io or have a look at the xref:cloudBeta:overview:index.adoc[Documentation] for more details.
15+
Check out the new Savanna at https://savanna.tgcloud.io or have a look at the xref:savanna:overview:index.adoc[Documentation] for more details.
1516
====
1617

18+
// [NOTE]
19+
// ====
20+
// On December 31, 2025, we'll retire the TigerGraph Cloud Classic platform. Before that date, you’ll need to migrate your data from TigerGraph Cloud Classic to TigerGraph Savanna. For support, please contact us at [email protected].
21+
// ====
22+
1723
== Get to Know Your TigerGraph Cloud
1824

1925
[.home-card,cols="2",grid=none,frame=none, separator=¦]
@@ -36,7 +42,6 @@ image:security-homecard.png[alt=security,width=74,height=74]
3642

3743
Learn how TigerGraph Cloud can help ensure the xref:cloud:security:index.adoc[Security] of your data and network.
3844

39-
4045
¦
4146
image:billing-homecard.png[alt=billing,width=74,height=74]
4247
*Billing*
@@ -62,6 +67,6 @@ See other documents to help support your TigerGraph Cloud journey.
6267
xref:cloud:reference:index.adoc[Reference |]
6368
xref:cloud:reference:glossary.adoc[Glossary |]
6469
xref:cloud:reference:service-limits.adoc[Service Limits]
65-
¦
70+
6671
|===
6772

modules/cloud/modules/support/pages/faqs.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ In addition, for TigerGraph paid tier clusters, users can use GSQL Web Shell to
179179

180180
A: TigerGraph uses GSQL, the query language designed for fast and scalable graph operations and analytics. GSQL's similarity to SQL, high-level syntax, Turing completeness, and built-in parallelism brings faster performance, faster development and the ability to describe any algorithm.
181181

182-
You can start learning GSQL from our xref:3.5@gsql-ref:tutorials:gsql-101/index.adoc[GSQL tutorials]. We also support a RESTful API and JSON output for easy integration with application languages like Python, Java, and C{pp}.
182+
You can start learning GSQL from our xref:gsql-ref:tutorials:gsql-101/index.adoc[GSQL tutorials]. We also support a RESTful API and JSON output for easy integration with application languages like Python, Java, and C{pp}.
183183

184184
Start learning GSQL and become a TigerGraph Certified Associate today with our link:https://www.tigergraph.com/certification/[Certification Program].
185185

@@ -190,7 +190,7 @@ A: Yes. If you use V3.0.5+ in TigerGraph Cloud, MultiGraph is supported through
190190

191191
=== *Q: What methods do you support for importing data?*
192192

193-
A: We support AWS S3 import, Google Cloud Storage, and local file upload through GraphStudio. Spark loading is available through our open source JDBC Driver. See https://github.com/tigergraph/ecosys/tree/master/tools/etl[https://github.com/tigergraph/ecosys/tree/master/etl]
193+
A: We support loading data from Amazon S3, Google Cloud Storage, and local files through GraphStudio. Spark loading is available through our open-source JDBC Driver. See https://github.com/tigergraph/ecosys/tree/master/tools/etl[https://github.com/tigergraph/ecosys/tree/master/etl]
194194

195195
In addition, for TigerGraph paid tier clusters, users can use the GSQL Web Shell to write GSQL Commands in an interactive command line shell. This GSQL Web Shell opens up more data loading options such as S3 Loader (parquet format), Kafka Loader and other complex loading jobs. Users can access GSQL Web Shell through the cluster panel from their Cloud Portal.
196196

modules/cloudbeta/antora.yml

-21
This file was deleted.

modules/cloudbeta/modules/administration/nav.adoc

-10
This file was deleted.

modules/cloudbeta/modules/administration/pages/index.adoc

-22
This file was deleted.

modules/cloudbeta/modules/billing-manager/nav.adoc

-9
This file was deleted.

modules/cloudbeta/modules/billing-manager/pages/compute_price.adoc

-1
This file was deleted.

modules/cloudbeta/modules/billing-manager/pages/index.adoc

-28
This file was deleted.

0 commit comments

Comments
 (0)