Wheels Deployment

Configure CFWheels production settings for security, performance, and database handling.

203|108|Updated Jan 13, 2011
One-click install
npx skills add https://github.com/wheels-dev/wheels --skill wheels-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Wheels Deployment
Source: https://github.com/wheels-dev/wheels/tree/main/.claude/skills/wheels-deployment
Command: npx skills add https://github.com/wheels-dev/wheels --skill wheels-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through the critical process of configuring CFWheels applications for production deployment, addressing essential security hardening and performance optimization concerns to ensure a robust, efficient, and secure live environment.

Core Features & Use Cases

  • Production Configuration: Provides clear examples for error handling, caching, and database settings tailored for production.
  • Security Checklist: Ensures CSRF protection, debug information suppression, strong passwords, and HTTPS are in place.
  • Performance Checklist: Guides on enabling caching, optimizing database indexes, and using eager loading for faster applications.
  • Use Case: Before launching your Wheels application, use this skill to systematically review and apply production-ready settings. Ensure all debug information is off, caching is enabled, and essential security measures like CSRF protection are active, preventing common production pitfalls and vulnerabilities.

Quick Start

In config/settings.cfm, for production environment:

<cfif get("environment") == "production"> <cfscript> set(showDebugInformation=false); set(cacheActions=true); set(csrfProtection=true); </cfscript> </cfif>

Frequently Asked Questions about Wheels Deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure CFWheels for production deployment?

Production configuration for CFWheels involves setting environment-specific parameters in config/settings.cfm. Disable debug information, enable caching and CSRF protection, configure database autocommit settings, and apply security hardening to create a secure, high-performance live environment ready for production rollout.

What security settings should I enable before deploying a Wheels application?

Essential security settings include enabling CSRF protection, disabling debug information, enforcing HTTPS, suppressing error details from users, implementing strong session configuration, and obfuscating URLs. These measures prevent common vulnerabilities and protect your application during production deployment.

How do I optimize Wheels application performance for production?

Performance optimization includes enabling action caching, configuring gzip compression, minifying assets, using CDN for static content, optimizing database indexes, and implementing eager loading. These techniques reduce server load and improve response times in production environments.

What database settings are required for production Wheels deployments?

Production database configuration requires setting autocommit to false to improve transaction handling, configuring connection pooling, optimizing indexes for query performance, and ensuring secure credential storage. Proper database tuning is critical for reliability and performance at scale.

Can I use environment detection to apply different production settings?

Yes, Wheels supports environment detection through the get("environment") function. Use conditional checks to apply production-specific settings only when deploying to production, keeping development and staging configurations separate and maintaining clean deployment workflows.

What errors should I watch for when deploying Wheels to production?

Common production pitfalls include leaving debug information enabled, forgetting CSRF protection, misconfiguring database connections, disabling caching unintentionally, and missing HTTPS enforcement. A production deployment checklist ensures these critical security and performance settings are properly configured before going live.