New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Templates improvement #286
Comments
First one definitely makes a lot of sense and shouldn't be that complicated Second seems reasonable, and I guess wouldn't be much work after doing the first part Third one is slightly tricky, I was thinking of templates more like templates for say Microsoft Word, when you change a template file it doesn't change any existing word document using it. The reason for this is that the place I was working at when I originally wrote had a slight difference in the steps so each project so although they were set up from a template if the template changed we didn't want to existing projects to change. I guess I can understand how it would be useful though as several people have asked for it, maybe I could add an option to "link" and/or "unlink" from the template when creating a project |
Actually, I'm rethinking about this issue and I might have some changes to offer. For example : we work with Wordpress but we don't commit any Wordpress files in the repo. Instead we have a /theme and a /plugin folders. Then we use a Gulp task who will process everything (sass, minify, images...) and will copy the plugin and the theme folder into the wp-content. So this kind of project, I have created a script for the deployer. The script will fetch two project variables named WORDPRESS_VERSION and WORDPRESS_LOCALE. According to this settings, the script will download the asked version of Wordpress in the right locale, then create the symlinks and move what needs to be moved. There is the script if anyone interested :
Well, I think this script could be a template itself. Meaning that when you add a step, you can choose this script as a template. Just an idea... Thanks |
@REBELinBLUE don't want to argue about default steps, but it would be great to have templates for custom commands. One-type projects with big amount of post-install scripts are b-hurt when creating them one-by-one. |
Hello,
Just some feature requests concerning the templates :
It takes quite some time to configure a project especially when this project requires a lot of steps to deploy properly. In this case, it is very complicated to create a template first and then the project.
I would be nice to be able to generate a template from a project : when you're done configuring your project which deploys smoothely, you could click the "Generate template" button, give it a name and voila.
Also, it would be nice to be able to overwrite this template : if you improve the deployment process in the project, clicking the "Generate template" button should ask if you want to create a new template or overwrite an existing. This step is not mandatory as one could create a new template with a new name and delete the old one. But still, it's a nice to have.
Finally, when generating a project from a template, the project and the template are detached meaning that altering the template will not affect the project. Not a big deal but can become a pain when you have many projects generated from the same template and you have to fix something...
Thanks
Axel
The text was updated successfully, but these errors were encountered: