Get Your First Infrastructure Package Deployed in 30 Minutes

Follow our proven 4-step process to transform how your team manages infrastructure.

Account Setup≈ 5 min
✅
Publish Package≈ 10 min
✅
Deploy≈ 10 min
✅
Measure Success≈ 5 min
✅
Start Step 1 Practical, proven & outcome-driven
Your 30-Minute Outcome
  • Infrastructure packaged for reuse
  • One-command deployment
  • Version visibility established
  • Baseline success metrics captured
Complete each step to unlock scalable infrastructure distribution.

Pre-Flight Checklist

Prepare once – accelerate every deployment

What You'll Need
  • Infrastructure code (Bicep / Terraform / PowerShell)
  • CI/CD pipeline files (Azure DevOps / GitHub)
  • Team member emails
  • 30 minutes focused time
What You'll Achieve
  • First reusable package
  • Team can use your package
  • Visibility into version usage
  • Foundation for scale & governance
1

Account Setup & Environment Preparation

Create your account & authenticate (≈ 5 minutes)

1.1 Sign Up Process
  1. Visit portal.ipmhub.io
  2. Choose GitHub or Microsoft authentication
  3. Create organization name
  4. Invite initial team members
1.2 Install IPM CLI

Windows


winget install IPMHub.IPM

macOS


brew install ipm

Linux


wget -O - https://raw.githubusercontent.com/ipmhubio/ipm/main/ipmInstall.sh | bash
1.3 Authenticate
ipm login
Checkpoint: Run ipm account to verify credentials.
Troubleshooting Tips
Issue: CLI not recognized
Fix: Restart shell or ensure PATH updated.
2

Create Your First Package

Package your infrastructure solution (≈ 10 minutes)

2.1 Choose Starting Point
  • Option A: Simple package (single IaC + script)
  • Option B: Complete solution (IaC + pipelines + scripts + examples)
2.2 Recommended Structure
my-infrastructure-package/
                        ├── infrastructure/
                        │ ├── main.bicep
                        │ ├── parameters.json
                        │ └── modules/
                        ├── pipelines/
                        │ ├── azure-devops.yml
                        │ └── github-actions.yml
                        ├── scripts/
                        │ ├── deploy.ps1
                        │ └── post-deployment.sh
                        ├── README.md
                        └── CHANGELOG.md
                        └── examples/
2.3 Create Package in Portal
  1. Go to portal → Create Package
  2. Set name: org/package-name
  3. Add description & select visibility
  4. Select package type & save
2.4 Publish First Version

cd your-package-directory
ipm publish --package org/your-package-name \
--version 1.0.0 --folder ./
Checkpoint: Version 1.0.0 visible in portal.
Verification Steps
  • Metadata displays correctly
  • All folders included
  • Scripts executable
  • CI/CD files present
Tip: Run ipm build --dry-run before publish for validation.
3

Team Deployment & Testing

Install & validate across team (≈ 10 minutes)

3.1 Test Installation
mkdir test-deployment
cd test-deployment
ipm init
ipm add --package org/your-package-name
3.2 Verify Contents
  • Folder structure intact
  • Scripts execute locally
  • Pipeline YAMLs referenced
3.3 Invite Team Members
  1. Portal → Organization → Users
  2. Invite with roles (Contributor / Viewer)
  3. Confirm acceptance status
3.4 Team Member Workflow
ipm login
ipm add --package org/your-package-name
# Use included scripts/pipelines
Checkpoint: Another user deploys successfully.

Get Help & Support

Resources for every stage

Self-Service Resources
  • Docs: docs.ipmhub.io
  • Video tutorials
  • Community forum
  • Best practice library
Direct Support
  • Chat (business hours)
  • Email: support@ipmhub.io
  • Success manager (Teams+)
  • Migration assistance (first packages)

Ready for Advanced IPMHub Features?

Scale your infrastructure enablement with governance, analytics, and automation.

Create Second Package Book Team Training Schedule Success Review
Accelerate adoption · Built-in governance · Measure ROI Zero lock‑in architecture · Works with any cloud & CI/CD