Dotcom (#109)

questdb · Dec 23, 2024 · 0b4b1a1 · 0b4b1a1
1 parent 9dfddcc
commit 0b4b1a1
Show file tree

Hide file tree

Showing 16 changed files with 22 additions and 22 deletions.
diff --git a/.github/workflows/preview.yml b/.github/workflows/preview.yml
@@ -15,7 +15,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - name: Checkout questdb.io repository
+      - name: Checkout questdb.com repository
         uses: actions/checkout@v3
         with:
           ref: ${{ github.event.pull_request.head.sha }}

diff --git a/documentation/clients/date-to-timestamp-conversion.md b/documentation/clients/date-to-timestamp-conversion.md
@@ -14,7 +14,7 @@ QuestDB offers clients for Python, Go, Java, C, C++, Rust, C#/.NET, and JavaScri
 can directly use a `Timestamp` type when using the client, while others need to convert the timestamp into a
 long representing the epoch time in microseconds. We add such required conversions into the snippets.
 
-Please refer to the [ingestion overview](https://questdb.io/docs/ingestion-overview/) to learn more about the details of the client library for your language.
+Please refer to the [ingestion overview](/docs/ingestion-overview/) to learn more about the details of the client library for your language.
 
 ## Date to Timestamp in Python
 

diff --git a/documentation/clients/ingest-dotnet.md b/documentation/clients/ingest-dotnet.md
@@ -571,7 +571,7 @@ using var sender =
 using var sender =
     Sender.New(
         "tcps::addr=localhost:9009;tls_verify=unsafe_off;username=admin;token=NgdiOWDoQNUP18WOnb1xkkEG5TzPYMda5SiUOvT1K0U=;");
-// See: https://questdb.io/docs/reference/api/ilp/authenticate
+// See: /docs/reference/api/ilp/authenticate
 
 ```
 

diff --git a/documentation/concept/interval-scan.md b/documentation/concept/interval-scan.md
@@ -49,7 +49,7 @@ returned from a sub-query is not guaranteed to be in timestamp order.
 ## EXPLAIN Interval Scan
 
 You can determine whether an **Interval Scan** is used to execute a query using
-the [EXPLAIN](https://questdb.io/docs/reference/sql/explain/) command.
+the [EXPLAIN](/docs/reference/sql/explain/) command.
 
 For example, consider the `trades` table with a `timestamp` designated
 timestamp. The following query:

diff --git a/documentation/deployment/capacity-planning.md b/documentation/deployment/capacity-planning.md
@@ -356,7 +356,7 @@ sysctl fs.file-max
 
 If you are running the QuestDB using `systemd`, you will also need to set the `LimitNOFILE` property in your service file.
 
-If you have followed the [setup guide](https://questdb.io/docs/deployment/systemd/), then the file should be called `questdb.service` and be located at `~/.config/systemd/user/questdb.service`.
+If you have followed the [setup guide](/docs/deployment/systemd/), then the file should be called `questdb.service` and be located at `~/.config/systemd/user/questdb.service`.
 
 Add this property to the `[Service]` section, setting it to at least `1048576`, or higher if you have set higher OS-wide limits.
 
@@ -381,7 +381,7 @@ sysctl -a | grep kern.maxf
 The database relies on memory mapping to read and write data to its files. If
 the host machine has low limits on virtual memory mapping areas, this can cause
 out-of-memory exceptions
-([errno=12](https://questdb.io/docs/troubleshooting/os-error-codes/)). To
+([errno=12](/docs/troubleshooting/os-error-codes/)). To
 increase this setting and persist this configuration change, mapped memory area
 limits can be amended in `/etc/sysctl.conf`:
 

diff --git a/documentation/deployment/microsoft-azure-ubuntu.md b/documentation/deployment/microsoft-azure-ubuntu.md
@@ -102,7 +102,7 @@ ssh -i ~/download/questdb_key.pem azureuser@$YOUR_INSTANCE_IP
 ```
 
 Once we've connected to the instance, we will be following the
-[binary installation method](https://questdb.io/download/). Here, we use `wget`
+[binary installation method](/download/). Here, we use `wget`
 to download the latest QuestDB binary, extract it, and run the start script.
 
 ```bash

diff --git a/documentation/deployment/systemd.md b/documentation/deployment/systemd.md
@@ -67,7 +67,7 @@ open the `questdb.service` file and add the following:
 ```shell
 [Unit]
 Description=QuestDB
-Documentation=https://www.questdb.io/docs/
+Documentation=https://www.questdb.com/docs/
 After=network.target
 
 [Service]

diff --git a/documentation/guides/enterprise-quick-start.md b/documentation/guides/enterprise-quick-start.md
@@ -102,7 +102,7 @@ SELECT reload_tls();
 TLS is now active.
 
 For more details on TLS see the
-[TLS operations documentation](https://questdb.io/docs/operations/tls/).
+[TLS operations documentation](/docs/operations/tls/).
 
 ## 2. Setup a database administrator
 
@@ -396,7 +396,7 @@ Next, we will enable Enterprise-specific features.
 
 ## 7. Setup replication
 
-[Replication](https://questdb.io/docs/concept/replication/) consists of:
+[Replication](/docs/concept/replication/) consists of:
 
 - a primary database instance
 - an object storage

diff --git a/documentation/operations/replication.md b/documentation/operations/replication.md
@@ -23,7 +23,7 @@ If the cluster is already running, enabling replication requires minimal steps:
    [Write Ahead Log (WAL)](/docs/concept/write-ahead-log/) files in AWS, Azure,
    or NFS
 2. Enable a **primary** node and upload WAL files to the object storage
-3. Take a data [Snapshot](https://questdb.io/docs/operations/backup/) of the
+3. Take a data [Snapshot](/docs/operations/backup/) of the
    **primary** node
 4. Configure a **replica** node or and restore via snapshot or allow sync via
    WAL files

diff --git a/documentation/operations/tls.md b/documentation/operations/tls.md
@@ -9,7 +9,7 @@ Transport Layer Security (TLS) encryption is available on all supported network
 interfaces and protocols:
 
 - [InfluxDB Line Protocol over TCP](/docs/reference/api/ilp/overview/)
-- [PGWire](https://questdb.io/docs/reference/api/postgres/)
+- [PGWire](/docs/reference/api/postgres/)
 - [HTTP](/docs/reference/api/rest/) (REST API)
 
 It's possible to configure encryption on all interfaces at once or individually.

diff --git a/documentation/reference/sql/sample-by.md b/documentation/reference/sql/sample-by.md
@@ -330,7 +330,7 @@ Gives the following result:
 In this case, the timestamps are floored to the nearest UTC day, and grouped. The counts correspond
 to the number of entries occurring within each UTC day.
 
-This is particularly useful for summarising data for charting purposes; see the [candlestick chart](https://dashboard.demo.questdb.io/d-solo/fb13b4ab-b1c9-4a54-a920-b60c5fb0363f/public-dashboard-questdb-io-use-cases-crypto?orgId=1&refresh=750ms&panelId=6) from the example [crypto dashboard](https://questdb.io/dashboards/crypto/)/
+This is particularly useful for summarising data for charting purposes; see the [candlestick chart](https://dashboard.demo.questdb.io/d-solo/fb13b4ab-b1c9-4a54-a920-b60c5fb0363f/public-dashboard-questdb-io-use-cases-crypto?orgId=1&refresh=750ms&panelId=6) from the example [crypto dashboard](https://questdb.com/dashboards/crypto/)/
 
 ### TIME ZONE
 

diff --git a/documentation/third-party-tools/kafka.md b/documentation/third-party-tools/kafka.md
@@ -354,7 +354,7 @@ using `key.converter` and `value.converter` options, both are included in the
 ### Designated timestamps
 
 The connector supports
-[designated timestamps](https://questdb.io/docs/concept/designated-timestamp/).
+[designated timestamps](/docs/concept/designated-timestamp/).
 
 There are three distinct strategies for designated timestamp handling:
 
@@ -508,7 +508,7 @@ for more information.
 ### Symbol type
 
 QuestDB supports a special type called
-[symbol](https://questdb.io/docs/concept/symbol/). Use the `symbols`
+[symbol](/docs/concept/symbol/). Use the `symbols`
 configuration option to specify which columns should be created as the `symbol`
 type.
 
@@ -594,7 +594,7 @@ When a target table does not exist in QuestDB, it will be created automatically.
 This is the recommended approach for development and testing.
 
 In production, it's recommended to use the SQL
-[CREATE TABLE](https://questdb.io/docs/reference/sql/create-table/) keyword,
+[CREATE TABLE](/docs/reference/sql/create-table/) keyword,
 because it gives you more control over the table schema, allowing per-table
 [partitioning](/glossary/database-partitioning/), creating indexes, etc.
 

diff --git a/netlify.toml b/netlify.toml
@@ -634,7 +634,7 @@ for = "/*"
 X-Frame-Options = "SAMEORIGIN"
 X-XSS-Protection = "0"
 X-Content-Type-Options = "nosniff"
-Content-Security-Policy = "frame-src 'self' app.netlify.com *.demo.questdb.io *.questdb.io www.youtube.com www.slideshare.net forms.hsforms.com;"
+Content-Security-Policy = "frame-src 'self' app.netlify.com *.demo.questdb.com *.questdb.com www.youtube.com www.slideshare.net forms.hsforms.com;"
 
 [[headers]]
 for = "/static/*"

diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
-  "name": "questdb.io",
-  "version": "0.0.1",
+  "name": "documentation",
+  "version": "2.0.0",
   "private": true,
   "license": "Apache-2.0",
   "scripts": {

diff --git a/src/config/customFields.js b/src/config/customFields.js
@@ -1,5 +1,5 @@
 const githubOrgUrl = "https://github.com/questdb"
-const domain = "questdb.io"
+const domain = "questdb.com"
 
 module.exports = {
   trailingSlash: undefined,

diff --git a/static/robots.txt b/static/robots.txt
@@ -3,5 +3,5 @@ Disallow: /search/
 
 Allow: /sitemap.xml
 Disallow: /__unused/
-Sitemap: https://questdb.io/sitemap.xml
-Host: https://questdb.io
+Sitemap: https://questdb.com/sitemap.xml
+Host: https://questdb.com