Overview
The customer wanted to know if "ey-core" can accept extra options to be used in deploy hooks, specifically to skip asset precompilation. The solution involves configuring the ey.yml file to manage deployment options, as ey-core does not support arbitrary custom CLI options for deploy hooks.
Information
Issue: Inquiry about passing extra options to ey-core for deploy hooks to skip asset precompilation.
Resolution Steps:
-
Understand ey-core Limitations:
- ey-core does not natively support passing arbitrary custom CLI options for deploy hooks.
-
Use ey.yml for Deployment Customization:
- Navigate to your application's config directory.
- Locate or create the ey.yml file.
-
Configure ey.yml to Skip Asset Precompilation:
- Add or update the following line in the ey.yml file:
-
precompile_assets: false - This setting will skip asset precompilation during deployment for the specified environment.
-
Conditional Behavior:
- For conditional behavior, manually update the ey.yml setting before deployment or maintain separate configuration files or environments as needed.
-
Verify Configuration:
- Deploy your application and confirm that asset precompilation is skipped as expected.
Note: For more detailed information, refer to the public knowledge base article on ey-core usage in Engine Yard Cloud.
Frequently Asked Questions
- How can I skip asset precompilation during deployment with ey-core?
- Set
precompile_assets: falsein the ey.yml file located in your application's config directory to skip asset precompilation during deployment. - Can I pass custom CLI options to ey-core for deploy hooks?
- No, ey-core does not support passing arbitrary custom CLI options for deploy hooks. Deployment customization is managed via the ey.yml file.
- How do I manage conditional deployment behavior with ey-core?
- For conditional behavior, manually update the ey.yml setting before deployment or maintain separate configuration files or environments as needed.
Priyanka Bhotika
Comments