Skip to content
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

Plugin activation #15

Closed
niklaswallerstedt opened this issue Apr 18, 2017 · 4 comments · Fixed by #16
Closed

Plugin activation #15

niklaswallerstedt opened this issue Apr 18, 2017 · 4 comments · Fixed by #16

Comments

@niklaswallerstedt
Copy link
Contributor

niklaswallerstedt commented Apr 18, 2017

@3noch Regarding #14 and plugin activation. I would use wp-cli for this as well and extend the install script. You could either pass a list of plugins to activate or activate them all with the --all option.

@3noch
Copy link
Member

3noch commented Apr 18, 2017

@niklaswallerstedt Sweet! I could extend plugins.nix to tack on a bool for each plugin. Then your plugins.nix file could list both the source and whether or not you want it activated. That does make the plugin code a bit more complex, but I might be able to do it without much disruption. What do you think?

@niklaswallerstedt
Copy link
Contributor Author

I think I'd also prefer to keep it in there. I'm curious how you would extract all the plugin names that should be activated? Passing it to the script then should be pretty straightforward.

@3noch
Copy link
Member

3noch commented Apr 18, 2017

I already have to loop over the list of plugins to copy their source into the package. I could also loop over them (map) to generate a list of names that would be used to produce a command to give to wp-cli.

@niklaswallerstedt
Copy link
Contributor Author

Ah, I see 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants