From def23bf41a0b9019f9b958d5c8a54bd09aaed703 Mon Sep 17 00:00:00 2001 From: Hugo Marotta Date: Tue, 18 Aug 2026 17:55:07 -0300 Subject: [PATCH] Remove zwsp characters from mdx files --- docs/cloud/cache/authenticating/index.mdx | 6 +-- docs/cloud/cache/index.mdx | 2 +- docs/cloud/cache/prebuilt-cache/index.mdx | 4 +- docs/cloud/cache/usage/index.mdx | 8 ++-- .../dashboard/creating-your-team/index.mdx | 4 +- docs/cloud/dashboard/index.mdx | 2 +- .../dashboard/inviting-members/index.mdx | 4 +- docs/cloud/deploys/custom-domains/index.mdx | 4 +- docs/cloud/deploys/index.mdx | 12 ++--- docs/cloud/deploys/integrations/s3/index.mdx | 4 +- .../deploys/integrations/supabase/index.mdx | 6 +-- .../deploys/integrations/upstash/index.mdx | 2 +- .../deploys/monitoring-deploys/index.mdx | 6 +-- docs/cloud/deploys/setup/index.mdx | 12 ++--- docs/cloud/faq/index.mdx | 12 ++--- docs/cloud/index.mdx | 2 +- .../cloud/secrets/dashboard-secrets/index.mdx | 8 ++-- docs/cloud/secrets/index.mdx | 4 +- docs/cloud/secrets/secrets-cli/index.mdx | 18 ++++---- .../devbox/cli-reference/devbox-add/index.mdx | 6 +-- .../devbox-cache-configure/index.mdx | 2 +- .../cli-reference/devbox-cache-info/index.mdx | 2 +- .../devbox-cache-upload/index.mdx | 4 +- .../cli-reference/devbox-cache/index.mdx | 4 +- .../devbox-completion-bash/index.mdx | 8 ++-- .../devbox-completion-fish/index.mdx | 4 +- .../devbox-completion-zsh/index.mdx | 8 ++-- .../cli-reference/devbox-completion/index.mdx | 6 +-- .../cli-reference/devbox-create/index.mdx | 8 ++-- .../devbox-generate-devcontainer/index.mdx | 6 +-- .../devbox-generate-direnv/index.mdx | 4 +- .../devbox-generate-dockerfile/index.mdx | 6 +-- .../devbox-generate-readme/index.mdx | 4 +- .../cli-reference/devbox-generate/index.mdx | 6 +-- .../cli-reference/devbox-global-add/index.mdx | 6 +-- .../devbox-global-install/index.mdx | 4 +- .../devbox-global-list/index.mdx | 6 +-- .../devbox-global-pull/index.mdx | 4 +- .../devbox-global-push/index.mdx | 4 +- .../cli-reference/devbox-global-rm/index.mdx | 4 +- .../cli-reference/devbox-global-run/index.mdx | 6 +-- .../devbox-global-services/index.mdx | 4 +- .../devbox-global-shellenv/index.mdx | 4 +- .../devbox-global-update/index.mdx | 6 +-- .../cli-reference/devbox-global/index.mdx | 6 +-- .../cli-reference/devbox-info/index.mdx | 6 +-- .../cli-reference/devbox-init/index.mdx | 6 +-- .../cli-reference/devbox-install/index.mdx | 4 +- docs/devbox/cli-reference/devbox-rm/index.mdx | 4 +- .../devbox/cli-reference/devbox-run/index.mdx | 6 +-- .../cli-reference/devbox-search/index.mdx | 8 ++-- .../devbox-secrets-download/index.mdx | 6 +-- .../devbox-secrets-init/index.mdx | 4 +- .../devbox-secrets-list/index.mdx | 6 +-- .../cli-reference/devbox-secrets-rm/index.mdx | 6 +-- .../devbox-secrets-set/index.mdx | 6 +-- .../devbox-secrets-upload/index.mdx | 6 +-- .../cli-reference/devbox-secrets/index.mdx | 6 +-- .../devbox-services-attach/index.mdx | 4 +- .../devbox-services-ls/index.mdx | 4 +- .../devbox-services-restart/index.mdx | 4 +- .../devbox-services-start/index.mdx | 4 +- .../devbox-services-stop/index.mdx | 4 +- .../devbox-services-up/index.mdx | 6 +-- .../cli-reference/devbox-services/index.mdx | 6 +-- .../cli-reference/devbox-shell/index.mdx | 6 +-- .../cli-reference/devbox-shellenv/index.mdx | 4 +- .../cli-reference/devbox-update/index.mdx | 6 +-- .../devbox-version-update/index.mdx | 4 +- .../cli-reference/devbox-version/index.mdx | 6 +-- docs/devbox/cli-reference/devbox.mdx | 4 +- docs/devbox/cli-reference/devbox/index.mdx | 4 +- docs/devbox/configuration/index.mdx | 28 +++++------ .../continuous-integration/github-action.mdx | 6 +-- .../github-action/index.mdx | 6 +-- .../databases/mariadb/index.mdx | 14 +++--- .../databases/mongodb/index.mdx | 8 ++-- .../devbox-examples/databases/mysql/index.mdx | 14 +++--- .../databases/postgres/index.mdx | 14 +++--- .../databases/rabbitmq/index.mdx | 8 ++-- .../devbox-examples/databases/redis/index.mdx | 14 +++--- .../databases/valkey/index.mdx | 14 +++--- docs/devbox/devbox-examples/index.mdx | 8 ++-- .../languages/csharp/index.mdx | 4 +- .../languages/elixir/index.mdx | 8 ++-- .../languages/fsharp/index.mdx | 4 +- .../devbox-examples/languages/go/index.mdx | 4 +- .../languages/haskell/index.mdx | 2 +- .../devbox-examples/languages/java/index.mdx | 6 +-- .../devbox-examples/languages/nim/index.mdx | 2 +- .../languages/nodejs/index.mdx | 10 ++-- .../devbox-examples/languages/php/index.mdx | 14 +++--- .../languages/python/index.mdx | 10 ++-- .../devbox-examples/languages/ruby/index.mdx | 10 ++-- .../devbox-examples/languages/zig/index.mdx | 2 +- .../devbox-examples/servers/apache/index.mdx | 14 +++--- .../devbox-examples/servers/caddy/index.mdx | 14 +++--- .../devbox-examples/servers/nginx/index.mdx | 14 +++--- .../devbox-examples/stacks/django/index.mdx | 10 ++-- .../devbox-examples/stacks/drupal/index.mdx | 6 +-- .../devbox-examples/stacks/jekyll/index.mdx | 4 +- .../devbox-examples/stacks/lapp/index.mdx | 4 +- .../devbox-examples/stacks/laravel/index.mdx | 8 ++-- .../devbox-examples/stacks/lepp/index.mdx | 10 ++-- .../devbox-examples/stacks/rails/index.mdx | 4 +- .../devbox-examples/stacks/spring/index.mdx | 6 +-- docs/devbox/devbox-global/index.mdx | 22 ++++----- docs/devbox/env-variables/index.mdx | 4 +- docs/devbox/faq/index.mdx | 30 ++++++------ docs/devbox/guides/creating-plugins/index.mdx | 40 ++++++++-------- docs/devbox/guides/pinning-packages/index.mdx | 8 ++-- .../platform-specific-packages/index.mdx | 6 +-- docs/devbox/guides/plugins/index.mdx | 24 +++++----- docs/devbox/guides/scripts/index.mdx | 10 ++-- docs/devbox/guides/services/index.mdx | 14 +++--- docs/devbox/guides/using-flakes/index.mdx | 18 ++++---- .../devbox/ide-configuration/direnv/index.mdx | 18 ++++---- .../ide-configuration/eclipse/index.mdx | 6 +-- .../devbox/ide-configuration/vscode/index.mdx | 16 +++---- docs/devbox/ide-configuration/zed/index.mdx | 4 +- docs/devbox/index.mdx | 12 ++--- docs/devbox/installing-devbox.mdx | 6 +-- docs/devbox/installing-devbox/index.mdx | 8 ++-- docs/devbox/quickstart/index.mdx | 20 ++++---- docs/nixhub/get-a-package/index.mdx | 4 +- docs/nixhub/index.mdx | 10 ++-- .../resolve-a-package-version/index.mdx | 4 +- docs/nixhub/search-packages/index.mdx | 4 +- docs/testpilot/ai-test-generation.mdx | 18 ++++---- .../best-practices/write-effective-tests.mdx | 6 +-- .../getting-started/testing-android-apps.mdx | 16 +++---- .../getting-started/testing-ios-apps.mdx | 12 ++--- .../getting-started/testing-web-apps.mdx | 6 +-- .../testpilot/guides/add-context-to-tests.mdx | 20 ++++---- .../guides/email-testing-mailosaur.mdx | 12 ++--- docs/testpilot/guides/parallel-testing.mdx | 8 ++-- ...rameterize-tests-environment-variables.mdx | 14 +++--- docs/testpilot/guides/test-authentication.mdx | 8 ++-- .../guides/test-responsive-design.mdx | 14 +++--- docs/testpilot/index.mdx | 8 ++-- docs/testpilot/install.mdx | 4 +- docs/testpilot/integrations/gitlab-cicd.mdx | 38 +++++++-------- docs/testpilot/model-context-protocol.mdx | 10 ++-- docs/testpilot/pilotfile-reference.mdx | 46 +++++++++---------- .../reference/cli/testpilot-auth-login.mdx | 10 ++-- .../reference/cli/testpilot-auth-logout.mdx | 10 ++-- .../reference/cli/testpilot-auth-whoami.mdx | 10 ++-- .../reference/cli/testpilot-auth.mdx | 8 ++-- .../reference/cli/testpilot-generate.mdx | 8 ++-- .../reference/cli/testpilot-install.mdx | 8 ++-- .../reference/cli/testpilot-report-merge.mdx | 8 ++-- .../reference/cli/testpilot-report.mdx | 8 ++-- .../reference/cli/testpilot-test.mdx | 10 ++-- .../cli/testpilot-version-update.mdx | 8 ++-- .../reference/cli/testpilot-version.mdx | 6 +-- docs/testpilot/reference/cli/testpilot.mdx | 4 +- docs/testpilot/tips/index.mdx | 6 +-- 157 files changed, 664 insertions(+), 664 deletions(-) diff --git a/docs/cloud/cache/authenticating/index.mdx b/docs/cloud/cache/authenticating/index.mdx index add689a..797d9b7 100644 --- a/docs/cloud/cache/authenticating/index.mdx +++ b/docs/cloud/cache/authenticating/index.mdx @@ -6,7 +6,7 @@ description: in." --- -## Managing Access to the Cache[​](#managing-access-to-the-cache "Direct link to Managing Access to the Cache") +## Managing Access to the Cache[](#managing-access-to-the-cache "Direct link to Managing Access to the Cache") Team members can be added in one of two Roles, which controls their access to the Jetify Build Cache. @@ -17,7 +17,7 @@ Cache. You can add or remove team members from your team, or modify their role, using the [Jetify Cloud Dashboard](/docs/cloud/dashboard/inviting-members/) -## Authenticating from the CLI[​](#authenticating-from-the-cli "Direct link to Authenticating from the CLI") +## Authenticating from the CLI[](#authenticating-from-the-cli "Direct link to Authenticating from the CLI") Once you’ve been invited to a team, you can authenticate from the CLI by running: @@ -46,7 +46,7 @@ You can logout by running: devbox auth logout ``` -### Authenticating CI or Build Hosts[​](#authenticating-ci-or-build-hosts "Direct link to Authenticating CI or Build Hosts") +### Authenticating CI or Build Hosts[](#authenticating-ci-or-build-hosts "Direct link to Authenticating CI or Build Hosts") Admin users can generate Personal Access Tokens to authenticate on hosts where you cannot login via the CLI or Browser. This token will have the same push/pull permissions as the account that diff --git a/docs/cloud/cache/index.mdx b/docs/cloud/cache/index.mdx index 71b6677..abbf077 100644 --- a/docs/cloud/cache/index.mdx +++ b/docs/cloud/cache/index.mdx @@ -25,7 +25,7 @@ Jetify Cache provides the following features: and makes it easy to revoke access directly from the dashboard. Jetify also supports Single Sign On for Enterprise Cache users -## Guides[​](#guides "Direct link to Guides") +## Guides[](#guides "Direct link to Guides") - [Setting Up Jetify Cache](/docs/cloud/cache/authenticating/) - [Pushing and Pulling Packages from the Cache](/docs/cloud/cache/usage/) diff --git a/docs/cloud/cache/prebuilt-cache/index.mdx b/docs/cloud/cache/prebuilt-cache/index.mdx index 19e4c06..6cc8815 100644 --- a/docs/cloud/cache/prebuilt-cache/index.mdx +++ b/docs/cloud/cache/prebuilt-cache/index.mdx @@ -12,7 +12,7 @@ which are not available by default. This includes: 2. Packages which have not been built for certain platforms 3. Packages with unfree licenses, which are not automatically built by NixOS -## Using the Prebuilt Cache[​](#using-the-prebuilt-cache "Direct link to Using the Prebuilt Cache") +## Using the Prebuilt Cache[](#using-the-prebuilt-cache "Direct link to Using the Prebuilt Cache") The Prebuilt Cache is available for free to every developer who signs up for a Jetify Cloud account. Devbox will automatically configure itself to use the Prebuilt Cache when you login with @@ -25,7 +25,7 @@ Solo, Starter, and Scaleup accounts have unlimited access to the Prebuilt Cache. -## Packages included in the Prebuilt Cache[​](#packages-included-in-the-prebuilt-cache "Direct link to Packages included in the Prebuilt Cache") +## Packages included in the Prebuilt Cache[](#packages-included-in-the-prebuilt-cache "Direct link to Packages included in the Prebuilt Cache") Some of the packages included in the Prebuilt Cache are: diff --git a/docs/cloud/cache/usage/index.mdx b/docs/cloud/cache/usage/index.mdx index 3702aa5..c276542 100644 --- a/docs/cloud/cache/usage/index.mdx +++ b/docs/cloud/cache/usage/index.mdx @@ -2,7 +2,7 @@ title: "Pushing and Pulling Packages to the Cache" --- -## Pulling Packages from the Cache[​](#pulling-packages-from-the-cache "Direct link to Pulling Packages from the Cache") +## Pulling Packages from the Cache[](#pulling-packages-from-the-cache "Direct link to Pulling Packages from the Cache") Once you have authenticated, Devbox will automatically configure your cache for you. You can also manually configure the cache by running: @@ -21,12 +21,12 @@ binary in the following locations: If the package is not available in those locations, then it will build the package from source. -## Pushing to the Cache[​](#pushing-to-the-cache "Direct link to Pushing to the Cache") +## Pushing to the Cache[](#pushing-to-the-cache "Direct link to Pushing to the Cache") You can push custom packages and project closures to your Jetify Cache directly from the Devbox CLI. Push access is currently only available for authenticated users with Admin permissions. -### **Pushing a Devbox Project**[​](#pushing-a-devbox-project "Direct link to pushing-a-devbox-project") +### **Pushing a Devbox Project**[](#pushing-a-devbox-project "Direct link to pushing-a-devbox-project") You can push the entire closure of a Devbox project to the Jetify Cache by navigating to your project root and running @@ -35,7 +35,7 @@ project root and running devbox cache upload ``` -### Pushing a specific package[​](#pushing-a-specific-package "Direct link to Pushing a specific package") +### Pushing a specific package[](#pushing-a-specific-package "Direct link to Pushing a specific package") You can also push a single package by passing a flake reference to the Devbox CLI. diff --git a/docs/cloud/dashboard/creating-your-team/index.mdx b/docs/cloud/dashboard/creating-your-team/index.mdx index 8b3b79c..70be68c 100644 --- a/docs/cloud/dashboard/creating-your-team/index.mdx +++ b/docs/cloud/dashboard/creating-your-team/index.mdx @@ -12,7 +12,7 @@ collaborate on projects in Jetify Cloud. Users with a free account can upgrade to a paid team on the dashboard anytime. -## Creating a New Team Account[​](#creating-a-new-team-account "Direct link to Creating a New Team Account") +## Creating a New Team Account[](#creating-a-new-team-account "Direct link to Creating a New Team Account") 1. From the Team Selector in the top right of your dashboard, select **Create a New Team** @@ -29,7 +29,7 @@ Users with a free account can upgrade to a paid team on the dashboard anytime. 1. Your new team will be created, and you will be automatically switched to your new team. You can now [invite other members](/docs/cloud/dashboard/inviting-members/) to join your team. -## Billing[​](#billing "Direct link to Billing") +## Billing[](#billing "Direct link to Billing") Free accounts are free forever. You will need to add a payment method to unlock paid tier features. diff --git a/docs/cloud/dashboard/index.mdx b/docs/cloud/dashboard/index.mdx index a4c8b2f..08de0a7 100644 --- a/docs/cloud/dashboard/index.mdx +++ b/docs/cloud/dashboard/index.mdx @@ -9,7 +9,7 @@ description: You can visit the Jetify Dashboard at [cloud.jetify.com](https://cloud.jetify.com) -## Guides[​](#guides "Direct link to Guides") +## Guides[](#guides "Direct link to Guides") - [Creating Your Team](/docs/cloud/dashboard/creating-your-team/) - [Inviting Members](/docs/cloud/dashboard/inviting-members/) diff --git a/docs/cloud/dashboard/inviting-members/index.mdx b/docs/cloud/dashboard/inviting-members/index.mdx index 510854b..c8dc6ee 100644 --- a/docs/cloud/dashboard/inviting-members/index.mdx +++ b/docs/cloud/dashboard/inviting-members/index.mdx @@ -18,7 +18,7 @@ Team members can be added in one of two Roles: - **Admins:** Have all the permissions of Members, but can also invite new team members and configure project billing -## Adding a Team Member[​](#adding-a-team-member "Direct link to Adding a Team Member") +## Adding a Team Member[](#adding-a-team-member "Direct link to Adding a Team Member") 1. In the Jetify Dashboard, navigate to the **Members** tab @@ -40,7 +40,7 @@ Team members can be added in one of two Roles: ![Active Member](./member-status-active.png) -## Removing a Team Member[​](#removing-a-team-member "Direct link to Removing a Team Member") +## Removing a Team Member[](#removing-a-team-member "Direct link to Removing a Team Member") Removing a team member will remove their access to all projects and secrets in your team. To remove a team member diff --git a/docs/cloud/deploys/custom-domains/index.mdx b/docs/cloud/deploys/custom-domains/index.mdx index b4ed072..cd7954e 100644 --- a/docs/cloud/deploys/custom-domains/index.mdx +++ b/docs/cloud/deploys/custom-domains/index.mdx @@ -11,7 +11,7 @@ description: You will need access to the DNS records for your Domain in order to configure it for Jetify Cloud. -## Adding a Custom Domain[​](#adding-a-custom-domain "Direct link to Adding a Custom Domain") +## Adding a Custom Domain[](#adding-a-custom-domain "Direct link to Adding a Custom Domain") 1. In your project on the Jetify Cloud Dashboard, select **Settings** 2. Scroll down to the **Custom Domain** section on the settings page @@ -24,7 +24,7 @@ description: **Issued** status: ![Custom Domain Issued](./custom-domain-status-issued.png) -## Removing a Custom Domain[​](#removing-a-custom-domain "Direct link to Removing a Custom Domain") +## Removing a Custom Domain[](#removing-a-custom-domain "Direct link to Removing a Custom Domain") You can remove a custom domain by clicking the Delete button. This will remove the domain from your project. Note that after removing the domain, you may want to also clean up your DNS records. diff --git a/docs/cloud/deploys/index.mdx b/docs/cloud/deploys/index.mdx index 0e2df91..b765c8d 100644 --- a/docs/cloud/deploys/index.mdx +++ b/docs/cloud/deploys/index.mdx @@ -13,13 +13,13 @@ description: Pricing](https://www.jetify.com/cloud/pricing). -## Quickstart[​](#quickstart "Direct link to Quickstart") +## Quickstart[](#quickstart "Direct link to Quickstart") This quickstart will walk through how to configure and deploy a project with Jetify Cloud. We'll start by forking an example repo that is configured for Jetify Deployments, and then demonstrate how to connect your Github repo and activate deploys for your account. -## Forking the Example Repo[​](#forking-the-example-repo "Direct link to Forking the Example Repo") +## Forking the Example Repo[](#forking-the-example-repo "Direct link to Forking the Example Repo") To help you get started with Jetify Cloud, we've created an [example Rails app](https://github.com/jetify-com/jetify-deploy-example) that's been configured to @@ -28,7 +28,7 @@ deploy with Jetify Cloud. You can fork this repo from the Github UI to add it to your account, or clone and push the repo to your Github account. -## Connecting your Repo to Jetify Cloud[​](#connecting-your-repo-to-jetify-cloud "Direct link to Connecting your Repo to Jetify Cloud") +## Connecting your Repo to Jetify Cloud[](#connecting-your-repo-to-jetify-cloud "Direct link to Connecting your Repo to Jetify Cloud") First, you'll need to sign-in with Github and connect your project to Jetify Cloud: @@ -42,7 +42,7 @@ First, you'll need to sign-in with Github and connect your project to Jetify Clo Once your project is added to Jetify Cloud, you can configure your secrets or deployments. -## Deploying your Site[​](#deploying-your-site "Direct link to Deploying your Site") +## Deploying your Site[](#deploying-your-site "Direct link to Deploying your Site") 1. Select the Deploys tab in your project 2. Click the **Enable Deployments** button to turn on Jetify Deployments for your project @@ -52,14 +52,14 @@ Once your project is added to Jetify Cloud, you can configure your secrets or de If your site fails to deploy, or if you want to update your deployment, push a commit to the default branch of your repo to trigger a new deploy. -## Visiting your Site[​](#visiting-your-site "Direct link to Visiting your Site") +## Visiting your Site[](#visiting-your-site "Direct link to Visiting your Site") When your site has finished deploying, Jetify Cloud will display a preview URL that you can visit to test your application. Congratulations! You've now deployed your first site with Jetify Cloud. -## Next Steps[​](#next-steps "Direct link to Next Steps") +## Next Steps[](#next-steps "Direct link to Next Steps") - Learn more about [setting up your project](/docs/cloud/deploys/setup/) - Set up a [custom domain](/docs/cloud/deploys/custom-domains/) for your application diff --git a/docs/cloud/deploys/integrations/s3/index.mdx b/docs/cloud/deploys/integrations/s3/index.mdx index 3384421..21e6beb 100644 --- a/docs/cloud/deploys/integrations/s3/index.mdx +++ b/docs/cloud/deploys/integrations/s3/index.mdx @@ -8,7 +8,7 @@ description: You can view an example of this integration on [Github](https://github.com/jetify-com/jetify-deploy-integration/tree/main/devbox-json/s3) -## Setting up S3[​](#setting-up-s3 "Direct link to Setting up S3") +## Setting up S3[](#setting-up-s3 "Direct link to Setting up S3") If you don't already have an S3 bucket configured, you will need an [AWS account](https://docs.aws.amazon.com/SetUp/latest/UserGuide/setup-overview.html) + IAM user @@ -28,7 +28,7 @@ and an [IAM User Policy](https://docs.aws.amazon.com/AmazonS3/latest/userguide/w allow your user to securely access the bucket. Consult the S3 documentation for more details on how to configure the correct policy for your needs. -## Connecting Jetify Cloud to your S3 Account[​](#connecting-jetify-cloud-to-your-s3-account "Direct link to Connecting Jetify Cloud to your S3 Account") +## Connecting Jetify Cloud to your S3 Account[](#connecting-jetify-cloud-to-your-s3-account "Direct link to Connecting Jetify Cloud to your S3 Account") If you want your Jetify Cloud App to push and pull objects from your S3 Bucket, you can use Jetify Secrets to set your AWS Access Key ID and Secret in your environment: diff --git a/docs/cloud/deploys/integrations/supabase/index.mdx b/docs/cloud/deploys/integrations/supabase/index.mdx index ae53566..03c79aa 100644 --- a/docs/cloud/deploys/integrations/supabase/index.mdx +++ b/docs/cloud/deploys/integrations/supabase/index.mdx @@ -10,7 +10,7 @@ description: You can view an example of this integration on [Github](https://github.com/jetify-com/jetify-deploy-integration/tree/main/devbox-json/supabase) -## Setting up Supabase[​](#setting-up-supabase "Direct link to Setting up Supabase") +## Setting up Supabase[](#setting-up-supabase "Direct link to Setting up Supabase") If you don't have one already, you will first need to create an organization and project in Supabase to use with Jetify Cloud. If you are just testing Supabase with Jetify, you can create a free @@ -19,7 +19,7 @@ personal organization to start. For more details, see the [Supabase Docs](https: If you plan to connect using PostgreSQL connection parameters, make sure that you save your Database password at creation time since you may need it to connect. -## Connecting using the Supabase API or Clients[​](#connecting-using-the-supabase-api-or-clients "Direct link to Connecting using the Supabase API or Clients") +## Connecting using the Supabase API or Clients[](#connecting-using-the-supabase-api-or-clients "Direct link to Connecting using the Supabase API or Clients") The simplest way to connect to Supabase is via the API or one of Supabase's client libraries. Connecting via the API also lets you use Supabase's advanced realtime and streaming features. @@ -57,7 +57,7 @@ key: str = os.getenv('SUPABASE_KEY') supabase: Client = create_client(url, key) ``` -## Connecting via PostgreSQL Connection Parameters[​](#connecting-via-postgresql-connection-parameters "Direct link to Connecting via PostgreSQL Connection Parameters") +## Connecting via PostgreSQL Connection Parameters[](#connecting-via-postgresql-connection-parameters "Direct link to Connecting via PostgreSQL Connection Parameters") You can also connect to your database using the standard PostgreSQL Database connection parameters. This is useful if your project cannot use the Supabase API, or if it requires a standard PostgreSQL diff --git a/docs/cloud/deploys/integrations/upstash/index.mdx b/docs/cloud/deploys/integrations/upstash/index.mdx index 68faf78..059d849 100644 --- a/docs/cloud/deploys/integrations/upstash/index.mdx +++ b/docs/cloud/deploys/integrations/upstash/index.mdx @@ -9,7 +9,7 @@ description: You can view an example of this integration on [Github](https://github.com/jetify-com/jetify-deploy-integration/tree/main/devbox-json/upstash) -## Using Upstash Redis with Jetify Cloud[​](#using-upstash-redis-with-jetify-cloud "Direct link to Using Upstash Redis with Jetify Cloud") +## Using Upstash Redis with Jetify Cloud[](#using-upstash-redis-with-jetify-cloud "Direct link to Using Upstash Redis with Jetify Cloud") - [Create a Redis Database](https://upstash.com/docs/redis/overall/getstarted) in Upstash. Select the Database's name and region, and then click the Create button diff --git a/docs/cloud/deploys/monitoring-deploys/index.mdx b/docs/cloud/deploys/monitoring-deploys/index.mdx index 8f278c7..042dd3e 100644 --- a/docs/cloud/deploys/monitoring-deploys/index.mdx +++ b/docs/cloud/deploys/monitoring-deploys/index.mdx @@ -5,7 +5,7 @@ description: Jetify Dashboard." --- -## Build Logs[​](#build-logs "Direct link to Build Logs") +## Build Logs[](#build-logs "Direct link to Build Logs") Build logs include all the logs generated when cloning, building, and uploading your project to Jetify's Docker Registry. You can check the build logs to see why a build or deployment failed, or @@ -16,7 +16,7 @@ expanding the Build logs section ![Build logs](./deployment-build-logs.png) -## Runtime Logs[​](#runtime-logs "Direct link to Runtime Logs") +## Runtime Logs[](#runtime-logs "Direct link to Runtime Logs") Runtime logs capture everything that has happened in your application after it is deployed to the Jetify Cloud. You can use these logs to for testing and debugging server-side errors, or for @@ -29,7 +29,7 @@ You can view your Runtime Logs by clicking the **Runtime Logs** tab in your Depl ![Runtime Logs](./deployment-runtime-logs.png) -## Preview URL[​](#preview-url "Direct link to Preview URL") +## Preview URL[](#preview-url "Direct link to Preview URL") In addition to build and runtime logs, Jetify Cloud automatically generates a randomized preview URL that you can use to test your application, or to share a preview of the deployment with other users diff --git a/docs/cloud/deploys/setup/index.mdx b/docs/cloud/deploys/setup/index.mdx index 747c79a..14c428f 100644 --- a/docs/cloud/deploys/setup/index.mdx +++ b/docs/cloud/deploys/setup/index.mdx @@ -2,7 +2,7 @@ title: "Setting Up Your Deployment" --- -## Configuring your Project[​](#configuring-your-project "Direct link to Configuring your Project") +## Configuring your Project[](#configuring-your-project "Direct link to Configuring your Project") Deploying a project with Jetify Cloud requires the following: @@ -14,7 +14,7 @@ Deploying a project with Jetify Cloud requires the following: running container, so you will need to ensure that your service is listening to that port. We also recommend setting your service host to `0.0.0.0`. -### Deploying with a devbox.json[​](#deploying-with-a-devboxjson "Direct link to Deploying with a devbox.json") +### Deploying with a devbox.json[](#deploying-with-a-devboxjson "Direct link to Deploying with a devbox.json") Jetify Cloud can use your `devbox.json` to generate a Docker container that will install your project dependencies and run your projects. In addition to installing your packages, Jetify will @@ -55,13 +55,13 @@ and `build` scripts (in that order), and the use `start` as the entrypoint to th You can preview how Jetify will run the project using `devbox generate dockerfile --for prod` -### Deploying with a Custom Dockerfile[​](#deploying-with-a-custom-dockerfile "Direct link to Deploying with a Custom Dockerfile") +### Deploying with a Custom Dockerfile[](#deploying-with-a-custom-dockerfile "Direct link to Deploying with a Custom Dockerfile") If your repo contains a Dockerfile, Jetify Cloud will use that Dockerfile to deploy your service (even if the project also contains a devbox.json). Your Dockerfile should define an entrypoint that Jetify can run upon deploying, as well as listen on port 8080. -## Connecting your Repo[​](#connecting-your-repo "Direct link to Connecting your Repo") +## Connecting your Repo[](#connecting-your-repo "Direct link to Connecting your Repo") Jetify requires you to connect a Github repo in order to deploy your service. To access private repositories, you will need to install the Devbox Cloud Github app in your repository: @@ -76,7 +76,7 @@ repositories, you will need to install the Devbox Cloud Github app in your repos ![Select the Repo for your Jetify Project](./select-repository-for-project.png) -## Choosing an Instance Size[​](#choosing-an-instance-size "Direct link to Choosing an Instance Size") +## Choosing an Instance Size[](#choosing-an-instance-size "Direct link to Choosing an Instance Size") Jetify will default your deployment to the smallest instance size (0.1 CPU + 512MB RAM). To choose a different size: @@ -87,7 +87,7 @@ different size: Changes to your instance size will take effect on the next deployment. -## Deleting your Project[​](#deleting-your-project "Direct link to Deleting your Project") +## Deleting your Project[](#deleting-your-project "Direct link to Deleting your Project") If you no longer want to deploy your project with Jetify Deploys, you can disable deployments in the Settings tab of your project. diff --git a/docs/cloud/faq/index.mdx b/docs/cloud/faq/index.mdx index c1bdadd..25ef046 100644 --- a/docs/cloud/faq/index.mdx +++ b/docs/cloud/faq/index.mdx @@ -6,7 +6,7 @@ description: us on our" --- -## Do I have to pay to use Jetify Cloud?[​](#do-i-have-to-pay-to-use-jetify-cloud "Direct link to Do I have to pay to use Jetify Cloud?") +## Do I have to pay to use Jetify Cloud?[](#do-i-have-to-pay-to-use-jetify-cloud "Direct link to Do I have to pay to use Jetify Cloud?") Jetify accounts are free for individual developers, and includes access to Jetify Secrets and the Jetify Prebuilt Cache. @@ -14,13 +14,13 @@ Jetify Prebuilt Cache. Using Jetify with a team requires a paid Jetify Solo, Starter, or Scale-up account. For details on other plans and limits, see our [**pricing**](https://www.jetify.com/cloud/pricing) page. -## How can I share my Jetify Cloud project with other developers?[​](#how-can-i-share-my-jetify-cloud-project-with-other-developers "Direct link to How can I share my Jetify Cloud project with other developers?") +## How can I share my Jetify Cloud project with other developers?[](#how-can-i-share-my-jetify-cloud-project-with-other-developers "Direct link to How can I share my Jetify Cloud project with other developers?") To share secrets and access to deployments with other team members, you will need to create a new Jetify Starter Team and then invite developers to join your team. See the [cloud dashboard docs](/docs/cloud/dashboard/creating-your-team/) for more details. -## How do Jetify Cloud Plans work?[​](#how-do-jetify-cloud-plans-work "Direct link to How do Jetify Cloud Plans work?") +## How do Jetify Cloud Plans work?[](#how-do-jetify-cloud-plans-work "Direct link to How do Jetify Cloud Plans work?") Jetify Cloud Plans are available for a monthly platform fee, and allow you to share your Jetify Cloud resources with your team, along with increased support levels. All plans include usage credits @@ -28,20 +28,20 @@ equal to the monthly platform fee, which are billed at standard usage rates. For more details, see our [**pricing**](https://www.jetify.com/cloud/pricing) page. -## Do you offer self-hosted or private instances of Jetify Cloud?[​](#do-you-offer-self-hosted-or-private-instances-of-jetify-cloud "Direct link to Do you offer self-hosted or private instances of Jetify Cloud?") +## Do you offer self-hosted or private instances of Jetify Cloud?[](#do-you-offer-self-hosted-or-private-instances-of-jetify-cloud "Direct link to Do you offer self-hosted or private instances of Jetify Cloud?") We offer private instances and other features as part of our Enterprise Plan. [Contact us](https://calendly.com/d/3rd-bhp-qym/meet-with-the-jetify-team) so we can build a solution that meets your needs. -## How does pricing for Jetify Cache work?[​](#how-does-pricing-for-jetify-cache-work "Direct link to How does pricing for Jetify Cache work?") +## How does pricing for Jetify Cache work?[](#how-does-pricing-for-jetify-cache-work "Direct link to How does pricing for Jetify Cache work?") The Jetify Prebuilt Cache is included in your subscription for no additional cost. Jetify Private Cache costs $0.60/GB of storage per month for the first 50 GB, and $0.50/GB per month after that. Jetify Private cache does not charge for bandwidth or downloads. -## My project needs a custom instance size or scaling policy[​](#my-project-needs-a-custom-instance-size-or-scaling-policy "Direct link to My project needs a custom instance size or scaling policy") +## My project needs a custom instance size or scaling policy[](#my-project-needs-a-custom-instance-size-or-scaling-policy "Direct link to My project needs a custom instance size or scaling policy") We can customize Jetify Deployments for your project's needs. [Contact us](https://calendly.com/d/3rd-bhp-qym/meet-with-the-jetify-team) for help with a diff --git a/docs/cloud/index.mdx b/docs/cloud/index.mdx index 7ce1e2c..ffbb6a5 100644 --- a/docs/cloud/index.mdx +++ b/docs/cloud/index.mdx @@ -24,7 +24,7 @@ environments, and automatically synchronize them with your Devbox Shells and Scr More features are coming soon, keep an eye on our [**blog**](https://www.jetify.com/blog) for future updates! -## Getting Started[​](#getting-started "Direct link to Getting Started") +## Getting Started[](#getting-started "Direct link to Getting Started") - Speed up your dev environments with [**Jetify Cache**](/docs/cloud/cache/) - Integrate Secrets with your Devbox project using [**Jetify Secrets**](/docs/cloud/secrets/) diff --git a/docs/cloud/secrets/dashboard-secrets/index.mdx b/docs/cloud/secrets/dashboard-secrets/index.mdx index 2ea8c0f..2e2071d 100644 --- a/docs/cloud/secrets/dashboard-secrets/index.mdx +++ b/docs/cloud/secrets/dashboard-secrets/index.mdx @@ -7,14 +7,14 @@ description: application." --- -## Prerequisites[​](#prerequisites "Direct link to Prerequisites") +## Prerequisites[](#prerequisites "Direct link to Prerequisites") To manage secrets from the Jetify Cloud Dashboard, you must first: 1. Add the project to your Jetify Cloud account 2. Initialize the project to use Jetify Secrets -## Adding a Secret[​](#adding-a-secret "Direct link to Adding a Secret") +## Adding a Secret[](#adding-a-secret "Direct link to Adding a Secret") 1. From the Jetify Dashboard, select the project whose secrets you want to manage 2. Navigate to the Secrets tab of the Jetify Dashboard @@ -28,7 +28,7 @@ To manage secrets from the Jetify Cloud Dashboard, you must first: 5. To add multiple secrets at one time, click the **Add Another** button 6. When you are finished adding secrets, click the **Submit** button -## Updating and Managing Secrets[​](#updating-and-managing-secrets "Direct link to Updating and Managing Secrets") +## Updating and Managing Secrets[](#updating-and-managing-secrets "Direct link to Updating and Managing Secrets") You can update or manage secrets by clicking the edit button next to the secret that you want to update. This will open a modal where you can update the value of the secret, or delete the secret @@ -36,6 +36,6 @@ entirely. ![Editing Secrets](./edit-secrets-interface.png) -## Further Reading[​](#further-reading "Direct link to Further Reading") +## Further Reading[](#further-reading "Direct link to Further Reading") - [Managing Secrets with the Devbox CLI](/docs/cloud/secrets/secrets-cli/) diff --git a/docs/cloud/secrets/index.mdx b/docs/cloud/secrets/index.mdx index 3cf5cb5..bb5a8c7 100644 --- a/docs/cloud/secrets/index.mdx +++ b/docs/cloud/secrets/index.mdx @@ -6,7 +6,7 @@ description: your project's Devbox environment whenever you start a shell, run a script, or start a service." --- -## Key Concepts[​](#key-concepts "Direct link to Key Concepts") +## Key Concepts[](#key-concepts "Direct link to Key Concepts") Jetify provides an easy way to manage secrets for your projects. To get started, it’s helpful to understand the following key concepts: @@ -26,7 +26,7 @@ all secrets are set on the `Development` environment, but Devbox also lets you s `Preview` and `Production` environment. Starting a shell or running a script in a specific environment gives you access to all the secrets that are set for your environment. -## Getting Started[​](#getting-started "Direct link to Getting Started") +## Getting Started[](#getting-started "Direct link to Getting Started") To learn how to set secrets from the Jetify Dashboard, see our [Dashboard Secrets](/docs/cloud/secrets/dashboard-secrets/) guide. diff --git a/docs/cloud/secrets/secrets-cli/index.mdx b/docs/cloud/secrets/secrets-cli/index.mdx index fa39261..de57c39 100644 --- a/docs/cloud/secrets/secrets-cli/index.mdx +++ b/docs/cloud/secrets/secrets-cli/index.mdx @@ -11,7 +11,7 @@ description: If you don't already have Devbox installed, see our [Quickstart](https://www.jetify.com/docs/devbox/quickstart/) guide to get started. -## Authenticating with Devbox[​](#authenticating-with-devbox "Direct link to Authenticating with Devbox") +## Authenticating with Devbox[](#authenticating-with-devbox "Direct link to Authenticating with Devbox") You can authenticate with Jetify Cloud by running `devbox auth login`. This will launch the browser authentication flow to sign into Jetify Cloud. @@ -21,7 +21,7 @@ authentication flow to sign into Jetify Cloud. Once you complete the authentication flow and select a team, the Devbox CLI will configure itself to use the team you selected -## Integrating a project with devbox secrets[​](#integrating-a-project-with-devbox-secrets "Direct link to Integrating a project with devbox secrets") +## Integrating a project with devbox secrets[](#integrating-a-project-with-devbox-secrets "Direct link to Integrating a project with devbox secrets") To create a new project on Jetify Cloud, navigate to the root directory of your project and run `devbox secrets init` @@ -38,9 +38,9 @@ Running `devbox secrets init` will create a new project in your current Jetify C org, and configure your project to use Jetify Secrets. The project should also be visible if you navigate to the [Jetify Dashboard](/docs/cloud/dashboard/). -## Adding Secrets to your Project[​](#adding-secrets-to-your-project "Direct link to Adding Secrets to your Project") +## Adding Secrets to your Project[](#adding-secrets-to-your-project "Direct link to Adding Secrets to your Project") -### Adding Secrets from the Command Line[​](#adding-secrets-from-the-command-line "Direct link to Adding Secrets from the Command Line") +### Adding Secrets from the Command Line[](#adding-secrets-from-the-command-line "Direct link to Adding Secrets from the Command Line") You can set secrets using `devbox secrets set`: @@ -61,7 +61,7 @@ devbox secrets set FOO=BAR --environment prod Supported environments include `dev`, `preview`, and `prod`. -### Adding Secrets from a File[​](#adding-secrets-from-a-file "Direct link to Adding Secrets from a File") +### Adding Secrets from a File[](#adding-secrets-from-a-file "Direct link to Adding Secrets from a File") You can bulk add secrets from a file by using `devbox secrets import`: @@ -108,7 +108,7 @@ Environment: preview +-----------------+-------+ ``` -## Accessing your Secrets from a Devbox Shell[​](#accessing-your-secrets-from-a-devbox-shell "Direct link to Accessing your Secrets from a Devbox Shell") +## Accessing your Secrets from a Devbox Shell[](#accessing-your-secrets-from-a-devbox-shell "Direct link to Accessing your Secrets from a Devbox Shell") Once your project is configured for Jetify Cloud, Devbox will automatically check whether the project exists in your Jetify Cloud account based on: @@ -123,7 +123,7 @@ secrets as environment variables whenever you: 2. Start services with `devbox services up` or `devbox services start` 3. Run a script with `devbox run` -## Removing a Secret from your Project[​](#removing-a-secret-from-your-project "Direct link to Removing a Secret from your Project") +## Removing a Secret from your Project[](#removing-a-secret-from-your-project "Direct link to Removing a Secret from your Project") You can remove a secret from your project by running `devbox secrets rm`: @@ -132,7 +132,7 @@ devbox secrets rm FOO [DONE] Deleted environment variable 'FOO' in environment: dev ``` -## Exporting Secrets to a File[​](#exporting-secrets-to-a-file "Direct link to Exporting Secrets to a File") +## Exporting Secrets to a File[](#exporting-secrets-to-a-file "Direct link to Exporting Secrets to a File") You can export your secrets to a `.env` file using `devbox secrets download`: @@ -143,7 +143,7 @@ devbox secrets download .env You can download from a specific environment using the `--environment` flag: -## Further Reading[​](#further-reading "Direct link to Further Reading") +## Further Reading[](#further-reading "Direct link to Further Reading") - [Devbox Secrets CLI Reference](/docs/devbox/cli-reference/devbox-secrets/) - [Managing Secrets from the Dashboard](/docs/cloud/secrets/dashboard-secrets/) diff --git a/docs/devbox/cli-reference/devbox-add/index.mdx b/docs/devbox/cli-reference/devbox-add/index.mdx index bb7e24e..b63888a 100644 --- a/docs/devbox/cli-reference/devbox-add/index.mdx +++ b/docs/devbox/cli-reference/devbox-add/index.mdx @@ -7,7 +7,7 @@ description: "Add a new package to your devbox" devbox add ... [flags] ``` -## Examples[​](#examples "Direct link to Examples") +## Examples[](#examples "Direct link to Examples") ```bash # Add the latest version of the `ripgrep` package @@ -23,7 +23,7 @@ devbox add busybox --exclude-platform aarch64-darwin,x86_64-darwin devbox add prometheus --outputs=out,cli ``` -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | @@ -50,7 +50,7 @@ The platforms below are also supported, but will build packages from source - `i686-linux` - `armv7l-linux` -## SEE ALSO[​](#see-also "Direct link to SEE ALSO") +## SEE ALSO[](#see-also "Direct link to SEE ALSO") - [devbox](/docs/devbox/cli-reference/devbox/) - Instant, easy, predictable shells and containers diff --git a/docs/devbox/cli-reference/devbox-cache-configure/index.mdx b/docs/devbox/cli-reference/devbox-cache-configure/index.mdx index 8883fad..163fd6a 100644 --- a/docs/devbox/cli-reference/devbox-cache-configure/index.mdx +++ b/docs/devbox/cli-reference/devbox-cache-configure/index.mdx @@ -18,7 +18,7 @@ This command is a no-op for single-user Nix installs that aren't running the Nix devbox cache configure [flags] ``` -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | --------------- | --------------------------------------------------------------- | diff --git a/docs/devbox/cli-reference/devbox-cache-info/index.mdx b/docs/devbox/cli-reference/devbox-cache-info/index.mdx index 97569da..aa6c494 100644 --- a/docs/devbox/cli-reference/devbox-cache-info/index.mdx +++ b/docs/devbox/cli-reference/devbox-cache-info/index.mdx @@ -7,7 +7,7 @@ description: "Output information about the nix cache" devbox cache info [flags] ``` -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | ------------- | --------------- | diff --git a/docs/devbox/cli-reference/devbox-cache-upload/index.mdx b/docs/devbox/cli-reference/devbox-cache-upload/index.mdx index 4a2ed4b..8ffb22c 100644 --- a/docs/devbox/cli-reference/devbox-cache-upload/index.mdx +++ b/docs/devbox/cli-reference/devbox-cache-upload/index.mdx @@ -11,11 +11,11 @@ description: devbox cache upload [installable] [flags] ``` -## Aliases[​](#aliases "Direct link to Aliases") +## Aliases[](#aliases "Direct link to Aliases") upload, copy -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | --------------------- | ------------------------------------------------------ | diff --git a/docs/devbox/cli-reference/devbox-cache/index.mdx b/docs/devbox/cli-reference/devbox-cache/index.mdx index 6f997bf..acad1c2 100644 --- a/docs/devbox/cli-reference/devbox-cache/index.mdx +++ b/docs/devbox/cli-reference/devbox-cache/index.mdx @@ -7,12 +7,12 @@ description: "A collection of commands to interact with the Jetify Cache or othe devbox cache [command] ``` -## Subcommands[​](#subcommands "Direct link to Subcommands") +## Subcommands[](#subcommands "Direct link to Subcommands") info Output information about the nix cache upload specified or nix packages in current project to cache -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | ------------- | --------------- | diff --git a/docs/devbox/cli-reference/devbox-completion-bash/index.mdx b/docs/devbox/cli-reference/devbox-completion-bash/index.mdx index 8a8fe2c..680059f 100644 --- a/docs/devbox/cli-reference/devbox-completion-bash/index.mdx +++ b/docs/devbox/cli-reference/devbox-completion-bash/index.mdx @@ -14,13 +14,13 @@ source <(devbox completion bash) To load completions for every new session, execute once: -## Linux[​](#linux "Direct link to Linux") +## Linux[](#linux "Direct link to Linux") ```bash devbox completion bash > /etc/bash_completion.d/devbox ``` -## macOS[​](#macos "Direct link to macOS") +## macOS[](#macos "Direct link to macOS") ```bash devbox completion bash > \ @@ -33,7 +33,7 @@ You will need to start a new shell for this setup to take effect. devbox completion bash ``` -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | ------------------- | ------------------------------- | @@ -41,7 +41,7 @@ devbox completion bash | `--no-descriptions` | disable completion descriptions | | `-q, --quiet` | suppresses logs | -## SEE ALSO[​](#see-also "Direct link to SEE ALSO") +## SEE ALSO[](#see-also "Direct link to SEE ALSO") - [devbox completion](/docs/devbox/cli-reference/devbox-completion/) - Generate the autocompletion script for the specified shell diff --git a/docs/devbox/cli-reference/devbox-completion-fish/index.mdx b/docs/devbox/cli-reference/devbox-completion-fish/index.mdx index cf30940..a67b9db 100644 --- a/docs/devbox/cli-reference/devbox-completion-fish/index.mdx +++ b/docs/devbox/cli-reference/devbox-completion-fish/index.mdx @@ -21,7 +21,7 @@ You will need to start a new shell for this setup to take effect. devbox completion fish [flags] ``` -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | ------------------- | ------------------------------- | @@ -29,7 +29,7 @@ devbox completion fish [flags] | `--no-descriptions` | disable completion descriptions | | `-q, --quiet` | suppresses logs | -## SEE ALSO[​](#see-also "Direct link to SEE ALSO") +## SEE ALSO[](#see-also "Direct link to SEE ALSO") - [devbox completion](/docs/devbox/cli-reference/devbox-completion/) - Generate the autocompletion script for the specified shell diff --git a/docs/devbox/cli-reference/devbox-completion-zsh/index.mdx b/docs/devbox/cli-reference/devbox-completion-zsh/index.mdx index 30ed325..1c923d4 100644 --- a/docs/devbox/cli-reference/devbox-completion-zsh/index.mdx +++ b/docs/devbox/cli-reference/devbox-completion-zsh/index.mdx @@ -25,13 +25,13 @@ source <(devbox completion zsh); compdef _devbox devbox To load completions for every new session, execute once: -## Linux[​](#linux "Direct link to Linux") +## Linux[](#linux "Direct link to Linux") ```bash devbox completion zsh > "${fpath[1]}/_devbox" ``` -## macOS[​](#macos "Direct link to macOS") +## macOS[](#macos "Direct link to macOS") ```bash devbox completion zsh > \ @@ -44,7 +44,7 @@ You will need to start a new shell for this setup to take effect. devbox completion zsh [flags] ``` -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | ------------------- | ------------------------------- | @@ -52,7 +52,7 @@ devbox completion zsh [flags] | `--no-descriptions` | disable completion descriptions | | `-q, --quiet` | suppresses logs | -## SEE ALSO[​](#see-also "Direct link to SEE ALSO") +## SEE ALSO[](#see-also "Direct link to SEE ALSO") - [devbox completion](/docs/devbox/cli-reference/devbox-completion/) - Generate the autocompletion script for the specified shell diff --git a/docs/devbox/cli-reference/devbox-completion/index.mdx b/docs/devbox/cli-reference/devbox-completion/index.mdx index 102cbff..1ffea26 100644 --- a/docs/devbox/cli-reference/devbox-completion/index.mdx +++ b/docs/devbox/cli-reference/devbox-completion/index.mdx @@ -3,19 +3,19 @@ title: "devbox completion" description: "Generate the autocompletion script for the specified shell" --- -## Synopsis[​](#synopsis "Direct link to Synopsis") +## Synopsis[](#synopsis "Direct link to Synopsis") Generate the autocompletion script for devbox for the specified shell. See each sub-command's help for details on how to use the generated script. -## Options[​](#options "Direct link to Options") +## Options[](#options "Direct link to Options") | Option | Description | | ------------- | ------------------- | | `-h, --help` | help for completion | | `-q, --quiet` | suppresses logs | -## SEE ALSO[​](#see-also "Direct link to SEE ALSO") +## SEE ALSO[](#see-also "Direct link to SEE ALSO") - [devbox](/docs/devbox/cli-reference/devbox/) - Instant, easy, predictable development environments - [devbox completion bash](/docs/devbox/cli-reference/devbox-completion-bash/) - Generate the diff --git a/docs/devbox/cli-reference/devbox-create/index.mdx b/docs/devbox/cli-reference/devbox-create/index.mdx index 8414819..a854994 100644 --- a/docs/devbox/cli-reference/devbox-create/index.mdx +++ b/docs/devbox/cli-reference/devbox-create/index.mdx @@ -3,7 +3,7 @@ title: "devbox create" description: "Initialize a directory as a devbox project using a template" --- -## Synopsis[​](#synopsis "Direct link to Synopsis") +## Synopsis[](#synopsis "Direct link to Synopsis") Initialize a directory as a devbox project. This will create an empty devbox.json in the current directory. You can then add packages using `devbox add` @@ -12,7 +12,7 @@ directory. You can then add packages using `devbox add` devbox create [dir] --template