Skip to content

Rename staging references to sandbox in developer guide #237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yarikoptic merged 2 commits into from
May 14, 2026
Merged

Rename staging references to sandbox in developer guide #237

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c5cefc7
docs: rename staging references to sandbox in developer guide
bendichter May 13, 2026
1b4ecbd
Update docs/developer-guide/developer-notes.md
bendichter May 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/developer-guide/creating-dandi-instance/dandi-infrastructure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion docs/developer-guide/creating-dandi-instance/initialize-vendors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion docs/developer-guide/developer-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading