My Recipes

My Recipes lets Administrators keep reusable private deployment definitions for applications and Site layouts they manage themselves.

What you can save

Where supported by the current Control release, a private recipe can describe a Custom Image, a Compose stack, or a native PHP/Node Site profile. A recipe stores deployment configuration, not a copy of a running Site.

Save and deploy

1. Choose Save as Private Recipe from a supported application/Site form, or create a recipe from My Recipes.
2. Give the recipe a clear name and review the saved source/runtime settings.
3. Open My Recipes later and select Deploy to create a new Site from that definition.
4. Enter any required environment values or credentials for the new deployment.

Revisions

Editing a saved recipe creates a newer revision. Sites already deployed from an older revision keep their existing configuration until you deliberately change those Sites.

Secrets

Protected environment values are not included in saved recipe definitions or exported recipe files. Supply fresh values when deploying. Do not put passwords or tokens in ordinary command arguments or other fields that are part of the reusable definition.

Import and export

Recipe export moves the validated definition only; it does not move a Site's files, database or secrets. Review imported recipes before using them, particularly their images, packages and installation steps.

Delete a recipe

Deleting a saved recipe removes that reusable definition and its revisions. It does not delete Sites that were already deployed from it.