Diff for "StagingServer"

Not logged in - Log In / Register

Differences between revisions 4 and 5
Revision 4 as of 2010-04-28 16:00:22
Size: 1234
Editor: f054123001
Comment: Copied text from help pop-up.
Revision 5 as of 2011-08-26 18:11:47
Size: 1304
Editor: c-98-246-63-231
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * Every 24 hours, staging's database is replaced with a fresh snapshot of Launchpad's production database: you will lose anything you do on staging.  * Every 24 hours, staging's database is replaced with a fresh snapshot of Launchpad's production database: you will lose anything you do on staging.  [[https://staging.launchpad.net/successful-updates.txt|Update logs]]

Staging — Launchpad's sandbox

If you want to try Launchpad out, you can use the staging environment (at https://staging.launchpad.net/) to experiment with real data and functionality, but without affecting the day-to-day work of other Launchpad users.

However, there are a few things to note about staging:

  • Every 24 hours, staging's database is replaced with a fresh snapshot of Launchpad's production database: you will lose anything you do on staging. Update logs

  • Staging runs the latest bleeding edge code from the Launchpad developers — if things go wrong, please let us know.

  • You can't create a new account on staging — instead, create one in Launchpad's production environment and then wait up to 24 hours for your account to be available on staging.
  • Staging does not send email.
  • You can upload translations and templates but not export them — uploaded translations/templates will disappear after 24 hours.
  • To push code branches to staging you need use bzr push lp://staging/~your-id/branch-name.

StagingServer (last edited 2020-05-22 14:18:38 by doismellburning)