At DeployHQ, we're always excited to showcase how our platform helps innovative companies streamline their deployment processes. Today, we're diving into how Flywheel manages their software deployments using our platform.
The Deployment Challenge
According to Flywheel's own documentation, deploying code can be challenging. Git is excellent for tracking changes, but transferring those changes to a production environment isn't always straightforward.
The DeployHQ Solution
Flywheel specifically recommends DeployHQ as their preferred deployment method for getflywheel.com. Here's why:
Key Platform Features
Supports multiple repository types:
- Git
- Mercurial
- Subversion
Deployment destinations include:
- FTP/SFTP
- Amazon S3
- Digital Ocean
- Lots of hosting providers
Deployment Configuration Highlights
Prerequisites
Flywheel recommends having:
- A Git repository (GitHub or Bitbucket preferred)
- A DeployHQ account (Free tier supports 1 project, 10 deploys/day)
Deployment Options
Flywheel uses two primary deployment strategies:
- Manual Deployment: Manually initiate deployments through DeployHQ dashboard
- Automatic Deployment: Automatic code push on each repository commit
Technical Implementation Details
Server Configuration
Flywheel uses these specific DeployHQ settings:
- Hostname: sftp.flywheelsites.com
- Protocol: SSH/SFTP
- Port: 22
- Deployment Path: Specific to WordPress theme/plugin directories
Important Deployment Considerations
- Only deploy themes or custom plugins
- WordPress core files are write-protected
- Ensure deployment path matches repository subdirectory
Pro Deployment Tips
"It's important that the settings for the Path on server and Subdirectory to deploy from are correct. These two must match up, or else you risk deploying the wrong files." - Flywheel Documentation
Deployment Workflow
- Connect Git repository
- Configure Flywheel SFTP server
- Set deployment parameters
- Choose deployment type
- Execute deployment
Potential Limitations
Warning: Configuring Git + DeployHQ deployment will overwrite files uploaded via traditional SFTP. Commit to a Git-only update strategy.
Conclusion
Flywheel's implementation demonstrates DeployHQ's flexibility in managing complex deployment scenarios, particularly for WordPress environments.
Ready to Optimize Your Deployments?
Start Your Free DeployHQ Trial
Source: Flywheel WordPress Support Documentation. Disclaimer: WordPress® is a registered trademark of the WordPress Foundation.
