You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 28, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 28, 2026. It is now read-only.
For versioning a deployment configuration of a project a "SurfCaptain.json" in the project could hold the configuration.
So the dev can change the build steps within the project -> commit -> build and deploy with new settings/steps/whatever.
I dont think it is very likely that you will have surf deployments of the same application but with different task sets. If I understand you correctly this is what you are aiming for?
Activity
ervaude commentedon May 14, 2015
As of now the steps (tasks) that are performed when deploying e.g. TYPO3 CMS are defined in the Application class (see: https://github.com/lightwerk/SurfRunner/blob/master/Classes/Lightwerk/SurfRunner/Domain/Model/Application/TYPO3/CMS/DeployApplication.php).
I dont think it is very likely that you will have surf deployments of the same application but with different task sets. If I understand you correctly this is what you are aiming for?