- Home
- Guides
- MVP Program
- Tech Track
- Pre-MVP checklist
- Humanitec Guides
-
- How to get started
- The five-minute IDP
- Setup Wizard
-
- Introduction
- Design principles
- Structure and integration points
- Dynamic Configuration Management
- Theory on developer workflows
- Tutorial: Deploy an Amazon S3 Resource to production
- Tutorial: Perform daily developer activities (debug, rollback, diffs, logs)
- Tutorial: Deploy ephemeral Environments
- Theory on platform engineering workflows
- Resource management theory
- Tutorial: Provision a Redis cluster on AWS using Terraform
- Tutorial: Update Resource Definitions for related Applications
-
-
Pre-MVP checklist
On this page
Any item not checked off will potentially delay the MVP and cost you money.
Prepare Tech Track work #
Can technical work start at your MVP start date? Have you… #
- Identified a suitable test app for the MVP and convinced the team to spend 4 hours testing your platform? Before approaching a team, read the document Identifying and onboarding app 1 during MVPs
- Collected deployment artifacts for this app? This includes helm charts, TF files, pipelines, network diagrams
- [for Slack users] Please provide the email address of at least one person to be invited to our Support Slack and let us know whether you can use Slack Connect; we will set up the channel so that this person can invite all other team members
[for MS Teams users] Please provide the email addresses of everybody to be invited to a shared channel in our MS Teams instance - Do you have your final Humanitec Org created? If not, create one here . Please invite your Humanitec architect to this org with admin access
- Do you require SSO? Gather the data outlined in this docs page and share with your Humanitec architect
- Created (and have approval for) any necessary cloud accounts (sandbox or otherwise) for the MVP?
- Created the required clusters to be used during the MVP?
- Are there limitations on egress traffic to the public internet from the cluster?
If yes:- Open up access to
drivers.humanitec.io
andagent-01.humanitec.io
from the cluster - If a proxy is required for egress, collect the proxy connection data and share with your architect
- Open up access to