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.

Sign up for GitHub

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

Jump to bottom

Have docpad run the local docpad installation if it exists... #620

Closed
balupton opened this issue Aug 29, 2013 · 8 comments
Closed

Have docpad run the local docpad installation if it exists... #620

balupton opened this issue Aug 29, 2013 · 8 comments

Comments

@balupton
Copy link
Member

Not sure if this is a good idea or not?
@balupton balupton mentioned this issue Aug 29, 2013
Closed
@greduan
Copy link
Contributor

greduan commented Aug 29, 2013

I personally think this is a good idea. It'll allow the user more control over what version of DocPad to use in specific projects.

It'll also remove the need for updating the global version of DocPad with each update no?

@balupton
Copy link
Member Author

Yeah, updates would then become suggestions. Rather than warnings.

The concern here is that before docpad update no one ever updated their plugins. Right now people are updating their plugins and local docpad instance via docpad update, but they're not updating their global instance.

We just need a way to guarantee the implementation of this feature won't make it worse. As we really need both to be in sync as much as possible.

@balupton
Copy link
Member Author

Perhaps one way is so that the global docpad installation auto-updates itself, but the local docpad installation only updates via docpad update. Just have to hope then that there isn't a bug in the latest global release.

@balupton
Copy link
Member Author

Alternatively, we could have it so docpad update is used to update the global installation too.

@greduan
Copy link
Contributor

greduan commented Aug 29, 2013

I like that last option. :)

@flamingm0e
Copy link

docpad update should update local and global if possible

balupton added a commit that referenced this issue Aug 29, 2013
@balupton
v6.51.0. Improvement.
7493a0a 
- v6.51.0 August 29, 2013
	- Better upgrade `docpad upgrade` and update `docpad update` experience
		- Thanks to [drguildo](https://github.com/drguildo) and [Eduan
Lavaque](https://github.com/Greduan) for [issue
#619](#619)
	- DocPad will now run the local installation if it exists (avoid this
by using the `--global` flag)
		- Thanks to [Eduan Lavaque](https://github.com/Greduan) and
[flamingm0e](https://github.com/flamingm0e) for [issue
#620](#620)
	- Added the ability to uninstall plugins via `docpad uninstall
<pluginName>`
	- Updated dependencies
@balupton
Copy link
Member Author

Implemented in v6.51.0. docpad will run the local installation by default (turn off with the --global flag).

docpad update just updates the local installation, docpad upgrade updates the global installation

The reasoning for docpad update not updating the global install as well, is that it could get really annoying if we want to keep the global installation as an older version, but work on a newer version locally.

@greduan
Copy link
Contributor

greduan commented Aug 29, 2013

Cool, already updated. :)

balupton added a commit that referenced this issue Oct 23, 2013
@balupton
v6.51.0. Improvement.
dc88945 
- v6.51.0 August 29, 2013
	- Better upgrade `docpad upgrade` and update `docpad update` experience
		- Thanks to [drguildo](https://github.com/drguildo) and [Eduan
Lavaque](https://github.com/Greduan) for [issue
#619](#619)
	- DocPad will now run the local installation if it exists (avoid this
by using the `--global` flag)
		- Thanks to [Eduan Lavaque](https://github.com/Greduan) and
[flamingm0e](https://github.com/flamingm0e) for [issue
#620](#620)
	- Added the ability to uninstall plugins via `docpad uninstall
<pluginName>`
	- Updated dependencies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@balupton @flamingm0e @greduan