-
Notifications
You must be signed in to change notification settings - Fork 31
Deployment plan #9
Comments
Hi, Sorry for my late reply I did not see it :/ Well I have just recieved a pull request and merged it, which fix the first issue. All entered data is now added to style.css As for the second question I am not sure what you mean. What I do is I run the wp-bones command from within the wordpress theme folder, hence it is 'always deployed' if you mean deploy to another server, yes I would copy the fies manually. I have seen other generators who create a git repo and so you can just do a git pull if you want to deploy elsewhere |
hi! the second question. steps for production upload:
is this correct? or is better upload all files |
I'm the one who should thank. It feels good when people find ones tool If we go with the git approach we can exclude the files in question. or could we make a grunt task to recompile everything into a global dist
|
hey @oldlastman |
wow that task it's pretty awesome :O |
Sounds good bro
|
I'm a little confused on grunt dist. Its great that it copies in everything from /library but why not copy all the templates as well, effectively making the dist folder a ready to deploy theme? This makes sense to me but maybe there's a reason not to do this. For example, I'm creating a dist folder at the top level in the theme like this:
|
hey @mdmoore That is really not a bad idea! Maybe an option in the installer would be in place? What do you think? Feel free to do a pull request |
hello,
I install and use this generator and i have a couple of questions:
thanks
PD: sorry i'm not native
The text was updated successfully, but these errors were encountered: