Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 36 Next »

In addition to our production environment, we have a sandbox environment which we will use for targeted development and experimentation. The sandbox is a copy of our production environment, refreshed biannually (in Feb and Aug).

Logging In

Sandbox development workflow

  1. Proposal: Create a ticket proposing a development need on the alma-config repo (requires a free GitHub account and inclusion into the PUL GitHub organization)

  2. Access: system admins will assign additional permissions as needed

  3. Development: Experiment and test in the sandbox
  4. Review: After the proposed changes have been made in the sandbox, they are reviewed with the system admin group
  5. Communication: Upcoming changes to production are communicated to affected stakeholders (e.g., during departmental check-ins and in issues on the alma-config repo)
  6. Implementation: System admins implement the approved changes in production

Refresh: System Administrator Tasks

Twice yearly (in Aug and Feb) the sandbox is refreshed. The following tasks need to be done by the system administrators:

Before refresh

  • Export lists of roles for users with roles differing from their prod roles (save to MEO Team Drive)
  • Export allowed S/FTP connections
  • Export allowed emails
  • Verify that the 'Webhook Monitoring Staging' integration profile setting is identical to prod.

After refresh 

  • Alma color scheme needs to be changed to orange (prod is black) (config > Alma Logo and Color Scheme)
  • Sandbox banner needs to be recreated (config > institution notifications)
  • Elevated Permissions need to be updated (from list exported above in 'Before refresh' steps and saved to MEO Team Drive)
  • Allowed S/FTP connections needs to be updated (config > Allowed S/FTP connections > import)
  • Allowed Emails need to be restored (config > Allowed Emails > import)
  • Ensure that 'New Princeton SFTP Staging' connection has been copied over from production (or recreate it using credentials in LastPass) (config > General > S/FTP Definitions)
  • Publishing profiles need to be pointed to 'New Princeton SFTP Staging' for the "Incremental Publishing" and "General Publishing" profiles (Resources > Publishing Profiles)
  • Webhook integration profile 'Webhook Monitoring Staging' needs the URL and secret key copied over from prod, activated and saved (config > Integration Profiles)





  • No labels