A sandbox is a shared development server that runs the real WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ codebase against the real production database. It is where changes to WordPress.org, and the sites around it, are tested and deployedDeploy Launching code from a local development environment to the production web server, so that it’s available to visitors. from.
The name is misleading in one important way: a sandbox is not isolated from production. See Working on a sandbox before you use one.
Do you need one?
Most contributors never do. If you are writing a patch, fixing a bug, or building a feature, you can do all of that in a local environment — see Setting Up Your Machine. Your change reaches WordPress.org when a committer deploys it.
You need a sandbox when you are:
- committing to
meta.svnordotorg.svnyourself, - deployingDeploy Launching code from a local development environment to the production web server, so that it’s available to visitors. WordPress.org or WordCamp.org,
- working on a site that has no local development environment (some do not),
- reproducing something that only happens against production data or the production cache.
In practice that means committers and people working toward commit access. If you are not sure, ask in the #meta channel on Make WordPress Slack before filing a request.
In this chapter
- Requesting sandbox access — how to get one.
- Connecting to your sandbox — SSHSSH Secure SHell – a protocol for securely connecting to a remote system in addition to or in place of a password., and viewing your sandbox in a browser.
- Working on a sandbox — the ground rules, and how the environment differs from local.
- Deploying WordPress.org — committing to SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. and running a deployDeploy Launching code from a local development environment to the production web server, so that it’s available to visitors..
- Deploying WordCamp.org — the separate WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. deploy path.
Related pages
- Subversion Access — generating the SVN password you will need before you can commit.
- Configuring Two-Factor Authentication — required for all committers.
- Projects — which site lives where.
