Skip to main content

​
Planning Your Deployment

​
Choose Meaningful Subdomains

Your subdomain is your application’s identity. Make it count:

Good Subdomains

  • portfolio-2024
  • my-store
  • blog-demo
  • project-tracker

Avoid

  • test123
  • app
  • asdf
  • project1
Think long-term. You’ll share this URL with others, so choose something professional and memorable.

​
Version Selection Strategy

Deploy the latest version when:
  • You’ve thoroughly tested all changes
  • All features work as expected
  • No known critical bugs exist
Deploy a previous version when:
  • The latest version has issues
  • You want to showcase a specific feature set
  • Rolling back from a problematic update
Always test in preview mode before deploying a new version to production.

​
Pre-Deployment Checklist

Before clicking deploy, verify:
1

Test in Preview

  • Open the preview of your selected version
  • Test all interactive features
  • Check responsiveness on different screen sizes
  • Verify integrations work correctly
2

Verify Integrations

  • Ensure required integrations are enabled
  • Test database connections
  • Confirm API endpoints respond
  • Check authentication flows (if applicable)
3

Review Content

  • Check for placeholder text or images
  • Verify all links work
  • Ensure no development/debugging code remains
  • Confirm proper error handling
4

Check Subdomain

  • Subdomain is available
  • Follows naming conventions
  • Easy to remember and share
  • Represents your project well

​
Deployment Workflow

Follow this workflow for smooth deployments:

​
Iterative Improvement

Use deployments to gather feedback:
  1. Deploy v1 - Basic functionality
  2. Collect Feedback - From users or stakeholders
  3. Create v2 - With improvements
  4. Test Thoroughly - Ensure v2 works perfectly
  5. Update Deployment - Switch to v2
  6. Repeat - Continue improving

​
Managing Multiple Projects

​
Subdomain Naming Convention

If you have multiple projects, use a consistent naming scheme: 
[category]-[project-name]
Examples:
  • portfolio-personal
  • portfolio-client
  • demo-ecommerce
  • demo-blog
  • client-dashboard
  • client-website
This makes it easy to remember and organize your deployments.

​
Priority System

Not all projects need deployment. Prioritize:
  • Client presentations
  • Portfolio pieces
  • Production applications
  • Public demos
  • Experimental projects
  • Learning projects
  • Internal tools
  • Template showcases
  • Quick tests
  • Code experiments
  • Incomplete projects
  • Sensitive applications

​
Performance Optimization

​
Keep Applications Lightweight

Deployed applications load faster when they’re optimized:
Minimize external dependencies
Optimize images before including them
Remove unused code and features
Avoid heavy animations or large media files

​
Efficient Integrations

When using integrations:
  • Only enable integrations you actually use
  • Avoid unnecessary API calls
  • Implement proper error handling
  • Use caching where appropriate
Each integration adds initialization time. Only enable what you need for production.

​
Security Considerations

​
Sensitive Data

Never include sensitive information in deployed applications:
API keys should be in integrations, not hardcoded
No passwords or secrets in the code
Don’t expose internal URLs or endpoints
Avoid personal information in demos

​
Public Access

Remember that deployed applications are publicly accessible:
  • Anyone with the URL can access your application
  • Search engines may index your subdomain
  • Content is visible to the world
For private or sensitive projects, keep them undeployed and share only via preview links with authenticated users.

​
Monitoring and Maintenance

​
Regular Health Checks

Periodically verify your deployments: Weekly:
  • Visit your deployed URL
  • Test main features
  • Check for broken links
Monthly:
  • Review deployment costs (premium subscription)
  • Update to latest stable version
  • Check for security updates
As Needed:
  • After creating significant updates
  • When you get user feedback
  • If you notice issues

​
Version Management

Keep track of your deployments: 
Project: Portfolio
- Version 0: Initial design ⭐ Deployed
- Version 1: Added projects section
- Version 2: Fixed mobile responsiveness
- Version 3: Added contact form

Next: Deploy version 3 after testing

​
Sharing Your Deployment

​
Best Practices for Sharing

When sharing your deployed application: Do:
  • Test the URL before sharing
  • Provide context about what they’ll see
  • Mention if it’s a work-in-progress
  • Include instructions if needed
Don’t:
  • Share immediately after deploying (test first)
  • Forget to mention it’s a demo/prototype
  • Share broken or incomplete versions
  • Use generic descriptions

​
Example Share Message

✓ Good:
"Hi! I built a task manager app with React.
Check it out: task-manager-demo.coderocket.app
Feel free to create tasks and test the features!"

✗ Poor:
"Check this: myapp.coderocket.app"

​
Cost Management

​
Optimizing Premium Usage

Make the most of your premium subscription:
  • Deploy your best work that you want to showcase
  • Keep a reasonable number of active deployments
  • Undeploy projects you no longer need
  • Update existing deployments rather than creating new ones
You can have unlimited deployments with premium, but managing fewer high-quality deployments is more effective than deploying everything.

​
Troubleshooting Prevention

Avoid common issues by:
Testing thoroughly before deploying
Using descriptive, available subdomains
Keeping your premium subscription active
Documenting what each version contains
Rolling back quickly if issues arise

​
Long-Term Strategy

​
Portfolio Building

Use deployments to build a professional portfolio:
  1. Curate Your Best Work - Deploy only polished projects
  2. Consistent Branding - Use a cohesive naming scheme
  3. Keep Updated - Refresh deployments with improvements
  4. Document Each Project - Maintain a list of deployed projects

​
Client Work

For client projects:
  • Use client name in subdomain: clientname-project
  • Keep separate from personal projects
  • Undeploy after project completion
  • Document handoff procedures

​
Next Steps

Deployment Guide

Start deploying your first application

Troubleshooting

Solve deployment issues