20 / 27

Workflows

Suggestion: Name your workflows using a verb in the imperative, e.g. "archive", "develop".

GOTCHA

When you pull, the workflow configuration is read from the local environment!

The means you MUST always keep _.live_devporter/config.yml in sync between environments otherwise strange things being to happen.

All Chapters & Pages

Search Results

Matched Pages

  1. Live Dev Porter
  2. Changelog
  3. Trouble Connecting to Remote
  4. Databases
  5. Environment Roles
  6. Environments
  7. File Groups
  8. Import
  9. Lando
  10. Creating Scaffold Files from the Local Environment
  11. Migrating From Loft Deploy
  12. Plugins
  13. Developing New Processors
  14. Processors
  15. Pulling Remote to Local
  16. Push
  17. Remote Environment
  18. Source Control
  19. On Dreamhost, Export Failed Due to PHP Version
  20. Workflows
  21. Alternative Remote Installations
  22. Using PHP in the Codebase
  23. Troubleshooting Installation
  24. Remote Environment
  25. Validation Errors
  26. Sanitation of Vulnerable Data
  27. Provided Sanitization Code

General

  1. Live Dev Porter
  2. Changelog
  3. Trouble Connecting to Remote
  4. Databases
  5. Environment Roles
  6. Environments
  7. File Groups
  8. Import
  9. Lando
  10. Creating Scaffold Files from the Local Environment
  11. Migrating From Loft Deploy
  12. Plugins
  13. Developing New Processors
  14. Processors
  15. Pulling Remote to Local
  16. Push
  17. Remote Environment
  18. Source Control
  19. On Dreamhost, Export Failed Due to PHP Version
  20. Workflows
  21. Alternative Remote Installations

Developers

  1. Using PHP in the Codebase

Troubleshooting

  1. Troubleshooting Installation
  2. Remote Environment
  3. Validation Errors

Security

  1. Sanitation of Vulnerable Data
  2. Provided Sanitization Code