From c5cefc7cf4bdbdec8780c60e08c8998239a43f7e Mon Sep 17 00:00:00 2001 From: Ben Dichter Date: Wed, 13 May 2026 16:13:44 -0400 Subject: [PATCH 1/2] docs: rename staging references to sandbox in developer guide Align developer-guide terminology with the rest of the docs, where the non-production environment is called "sandbox" rather than "staging". Co-Authored-By: Claude Opus 4.7 (1M context) --- .../creating-dandi-instance/dandi-infrastructure.md | 2 +- .../creating-dandi-instance/initialize-vendors.md | 2 +- docs/developer-guide/developer-notes.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/developer-guide/creating-dandi-instance/dandi-infrastructure.md b/docs/developer-guide/creating-dandi-instance/dandi-infrastructure.md index 5b97e4ce..211d4185 100644 --- a/docs/developer-guide/creating-dandi-instance/dandi-infrastructure.md +++ b/docs/developer-guide/creating-dandi-instance/dandi-infrastructure.md @@ -196,7 +196,7 @@ and [staging_pipeline.tf](https://github.com/dandi/dandi-infrastructure/blob/mas Setting up sandbox will require unique AWS Route 53 Domains, as well a different Heroku app with different compute. -**Note -- ensure you review your `web/netlify.toml` file in DANDI Archive -- this will define different environment variables that correspond with staging vs. production** +**Note -- ensure you review your `web/netlify.toml` file in DANDI Archive -- this will define different environment variables that correspond with sandbox vs. production** ### Email Setup diff --git a/docs/developer-guide/creating-dandi-instance/initialize-vendors.md b/docs/developer-guide/creating-dandi-instance/initialize-vendors.md index 10208c93..f029064d 100644 --- a/docs/developer-guide/creating-dandi-instance/initialize-vendors.md +++ b/docs/developer-guide/creating-dandi-instance/initialize-vendors.md @@ -6,7 +6,7 @@ The DANDI ecosystem relies on vendor services to operate. So first you will nee - **AWS**: Provides storage buckets (S3), as well as domain management (Route53), for resources across the DANDI ecosystem. As well as the services (EC2, Kubernetes, etc.) for deploying the JupyterHub. - **GitHub**: Serves as the authentication provider for accounts across the DANDI ecosystem. - **Terraform Cloud**: Manages provisioned resources across cloud vendors in a version-controlled manner. -- **Netlify**: Deploys production frontend build, as well as staging previews to assist with frontend development. +- **Netlify**: Deploys production frontend build, as well as sandbox previews to assist with frontend development. - **Sentry**: Provides observability and monitoring for API events. Some services are not yet integrated within the main infrastructure: diff --git a/docs/developer-guide/developer-notes.md b/docs/developer-guide/developer-notes.md index 49deaf95..93a696de 100644 --- a/docs/developer-guide/developer-notes.md +++ b/docs/developer-guide/developer-notes.md @@ -104,7 +104,7 @@ To access Sentry, login to https://dandiarchive.sentry.io . ### Heroku & Papertrail -The `dandi-api` and `dandi-api-staging` apps have the Papertrail add-on configured to capture logs. +The `dandi-api` and `dandi-api-sandbox` apps have the Papertrail add-on configured to capture logs. To access Papertrail, log in to the [Heroku dashboard](https://dashboard.heroku.com), proceed to the corresponding app and click on the "Papertrail" add-on. A cronjob on the `drogon` server backs up Papertrail logs as .csv files hourly at `/mnt/backup/dandi/papertrail-logs/{app}`. @@ -120,7 +120,7 @@ Logs for many of the repositories are archived on `drogon` server at `/mnt/backu All code repositories are hosted on GitHub. The easiest way to contribute is to gain push access to the repositories by talking to @waxlamp; this way, you can create pull requests based on branches within the origin repositories, which in -turn allows for Netlify deploy previews and Heroku staging previews to be built. +turn allows for Netlify deploy previews and Heroku sandbox previews to be built. However, this is not strictly required. You can contribute using the standard fork-and-pull-request model, but under this workflow we will lose the benefit of From 1b4ecbd5cb5da62b67a6887638d07c383c07e84a Mon Sep 17 00:00:00 2001 From: Ben Dichter Date: Wed, 13 May 2026 16:21:04 -0400 Subject: [PATCH 2/2] Update docs/developer-guide/developer-notes.md Co-authored-by: Kabilar Gunalan --- docs/developer-guide/developer-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-guide/developer-notes.md b/docs/developer-guide/developer-notes.md index 93a696de..2f7a129a 100644 --- a/docs/developer-guide/developer-notes.md +++ b/docs/developer-guide/developer-notes.md @@ -104,7 +104,7 @@ To access Sentry, login to https://dandiarchive.sentry.io . ### Heroku & Papertrail -The `dandi-api` and `dandi-api-sandbox` apps have the Papertrail add-on configured to capture logs. +The `dandi-api` and `dandi-api-staging` apps have the Papertrail add-on configured to capture logs. To access Papertrail, log in to the [Heroku dashboard](https://dashboard.heroku.com), proceed to the corresponding app and click on the "Papertrail" add-on. A cronjob on the `drogon` server backs up Papertrail logs as .csv files hourly at `/mnt/backup/dandi/papertrail-logs/{app}`.