Schedule
AppKu™ utilizes a standard deployment schedule and typically will manage deployments for you (unless you specify otherwise).
Note: All dates & times are in Pacific Standard Time.
- All standard
production deployments occur Friday, 7 AM to 11 AM.
In rare cases, due to delays or migrations, they may occur after Friday, 5 PM to Monday, 11 AM.
- Emergency/critical deployments will occur as soon as possible.
The AppKu™ team will do their best to coordinate with your organization's project owners and managers.
- All standard
review deployments will occur as soon as possible.
The AppKu™ team is happy to work with
your organization's project owners and managers to schedule non-standard (early or late) deployments. If this is needed, they can respond to an existing ticket, or contact the AppKu™ team directly. Optionally, they can
create a ticket & add the details of their request.
Deployment Environments
AppKu™ utilizes a tri-environment deployment model for the majority of information systems. That means that as updates are created, they will first be deployed to environment #1, quality checked, then to environment #2, quality checked again, and then finally deploy to the "#3" production environment (and quality checked), before the update is considered "Delivered".
- The first environment is called
Staging and is completely managed by AppKu™ internally.
The purpose of this environment is for our team to perform early-stage quality checks.
- The second environment is called
Review and is run on your organization's infrastructure of choice.
The purpose of this environment is to provide a place for Acceptance.
- The third environment is called
Production and is run on your organization's infrastructure of choice.
The purpose of this environment is day-to-day use by your organization and team. It is the "live" environment.
