Diff for "StagingServer"

Not logged in - Log In / Register

Differences between revisions 1 and 7 (spanning 6 versions)
Revision 1 as of 2009-09-18 16:44:55
Size: 404
Editor: g224050196
Comment: created
Revision 7 as of 2020-05-22 14:18:38
Size: 1666
Comment: Brief notes about possible SSO auth issues and qastaging
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
== Using the Staging Server ==
Line 8: Line 7:
You can find a sandbox copy of Launchpad at https://staging.launchpad.net/ which you can use to try out Launchpad including its latest features. = Staging — Launchpad's sandbox =
Line 10: Line 9:
=== Restore cycle === 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.
Line 12: Line 11:
=== User accounts === However, there are a few things to note about staging:
Line 14: Line 13:
=== Pushing branches ===  * Every 7 days, staging's database is replaced with a fresh snapshot of Launchpad's production database: you will lose anything you do on staging. The update is scheduled to happen on Saturdays. [[https://staging.launchpad.net/successful-updates.txt|Update logs]]
 * Staging runs the latest bleeding edge code from the Launchpad developers — if things go wrong, please [[https://bugs.launchpad.net/launchpad/+filebug|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.
 * Timing interactions with SSO environment syncing and Launchpad environment syncing may mean you need the help of a Launchpad administrator to manually link up your account the first time
 * 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.

If you don't need particularly up-to-date data, then there is also [[GetInvolved/BetaTesting|the qastaging environment]].

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 7 days, staging's database is replaced with a fresh snapshot of Launchpad's production database: you will lose anything you do on staging. The update is scheduled to happen on Saturdays. 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.
  • Timing interactions with SSO environment syncing and Launchpad environment syncing may mean you need the help of a Launchpad administrator to manually link up your account the first time
  • 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.

If you don't need particularly up-to-date data, then there is also the qastaging environment.

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