diff --git a/.github/workflows/cd.yml b/.github/workflows/cd.yml index 3a2cdd52..08d5de9e 100644 --- a/.github/workflows/cd.yml +++ b/.github/workflows/cd.yml @@ -1,8 +1,8 @@ -name: 'CD' +name: "CD" on: push: branches: - - 'main' + - "main" jobs: Deploy: runs-on: ubuntu-latest @@ -15,13 +15,13 @@ jobs: - name: Setup Node 18 uses: actions/setup-node@v2 with: - node-version: '18' + node-version: "18" - name: Install dependencies run: | npm i --force --unsafe-perm - name: Force installing sharp run: npm install --ignore-scripts=false --verbose sharp@0.30.7 --unsafe-perm --force - - name: 'Create env file' + - name: "Create env file" run: | rm -rf .env touch .env @@ -41,11 +41,11 @@ jobs: cat .env - name: Build run: | - PREFIX_PATHS=true npm run clean && npm run build && npm run deploy + PREFIX_PATHS=true npm run build && npm run deploy env: AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} - AWS_DEFAULT_REGION: 'us-east-1' + AWS_DEFAULT_REGION: "us-east-1" AWS_DEFAULT_OUTPUT: json TYPESENSE_HOST: ${{ secrets.TYPESENSE_HOST }} TYPESENSE_PORT: ${{ secrets.TYPESENSE_PORT }} diff --git a/.github/workflows/staging-cd.yml b/.github/workflows/staging-cd.yml index 7588ec4c..e43f9b01 100644 --- a/.github/workflows/staging-cd.yml +++ b/.github/workflows/staging-cd.yml @@ -1,8 +1,8 @@ -name: 'Staging CD' +name: "Staging CD" on: push: branches: - - 'dev' + - "dev" jobs: StagingDeploy: runs-on: ubuntu-latest @@ -15,14 +15,14 @@ jobs: - name: Setup Node 18 uses: actions/setup-node@v2 with: - node-version: '18' + node-version: "18" - name: Install dependencies run: | rm -rf .cache node_modules npm i --force --unsafe-perm - name: Force installing sharp run: npm install --ignore-scripts=false --verbose sharp@0.30.7 --unsafe-perm --force - - name: 'Create env file' + - name: "Create env file" run: | rm -rf .env touch .env @@ -44,11 +44,11 @@ jobs: run: sed -i 's/localhost/website.testsigma.com/g' src/environment.ts - name: Build run: | - PREFIX_PATHS=true npm run clean && npm run build && npm run deploy + PREFIX_PATHS=true npm run build && npm run deploy env: AWS_ACCESS_KEY_ID: ${{ secrets.WEBSITE_STAGING_AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{ secrets.WEBSITE_STAGING_AWS_SECRET_ACCESS_KEY }} - AWS_DEFAULT_REGION: 'us-east-1' + AWS_DEFAULT_REGION: "us-east-1" AWS_DEFAULT_OUTPUT: json TYPESENSE_HOST: ${{ secrets.WEBSITE_STAGING_TYPESENSE_HOST }} TYPESENSE_PORT: ${{ secrets.WEBSITE_STAGING_TYPESENSE_PORT }} diff --git a/src/pages/docs/testsigma-tunnel/intro.md b/src/pages/docs/testsigma-tunnel/intro.md index fc07cedd..c52aa6e0 100644 --- a/src/pages/docs/testsigma-tunnel/intro.md +++ b/src/pages/docs/testsigma-tunnel/intro.md @@ -1,26 +1,26 @@ --- -title: "Intro: Testsigma Tunnel" -metadesc: "Learn how Testsigma Tunnel securely tests private server URLs or locally hosted web apps on real browsers and devices. This article is an introduction for Testsigma Tunnel" +title: 'Intro: Testsigma Tunnel' +metadesc: 'Learn how Testsigma Tunnel securely tests private server URLs or locally hosted web apps on real browsers and devices. This article is an introduction for Testsigma Tunnel' noindex: false order: 32.1 -page_id: "Testsigma Tunnel" +page_id: 'Testsigma Tunnel' warning: false contextual_links: -- type: section - name: "Contents" -- type: link - name: "Getting Started" - url: "#getting-started" -- type: link - name: "Getting Help" - url: "#getting-help" + - type: section + name: 'Contents' + - type: link + name: 'Getting Started' + url: '#getting-started' + - type: link + name: 'Getting Help' + url: '#getting-help' --- --- Testsigma Tunnel allows you to securely test private server URLs or locally hosted web applications on real browsers and devices through Testsigma. Testsigma's tunnel binary can bypass the restrictions caused by corporate firewalls and proxy settings, ensuring a secure connection without IP whitelisting or public internet access. -Testsigma Tunnel establishes a secure connection between your system and Testsigma cloud servers using protocols like Web Socket, HTTPS, and SSH. This allows testing of locally hosted websites or web applications across multiple OS, browsers, and screen resolutions available on Testsigma. This article discusses key components, system requirements, and steps to execute Testsigma Tunnel for client connection. +Testsigma Tunnel establishes a secure connection between your system and Testsigma cloud servers using protocols like Web Socket, HTTPS, and SSH. This allows testing of locally hosted websites or web applications across multiple OS, browsers, and screen resolutions available on Testsigma. This article discusses key components, system requirements, and steps to execute Testsigma Tunnel for client connection. --- @@ -28,7 +28,7 @@ Testsigma Tunnel establishes a secure connection between your system and Testsig - [Key Components & System Requirements](https://testsigma.com/docs/testsigma-tunnel/key-components/) -- [Setup and Installation: Mac](https://testsigma.com//docs/testsigma-tunnel/setup-installation-mac/) +- [Setup and Installation: Mac](https://testsigma.com/docs/testsigma-tunnel/setup-installation-mac/) - [Setup and Installation: Windows](https://testsigma.com/docs/testsigma-tunnel/setup-installation-windows/) @@ -44,4 +44,4 @@ Testsigma Tunnel establishes a secure connection between your system and Testsig - For inquiries or help, reach out to Testsigma support at **support@testsigma.com**. ---- \ No newline at end of file +---