Skip to content

Update README.md #40

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

Open
Greg-Boggs wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ A command line tool for interfacing with Drupal.org. Uses the Drupal.org REST AP

Use the following command to install the command line tool via Composer:

`composer global require mglaman/drupalorg-cli`
`composer require mglaman/drupalorg-cli`
Copy link
Owner

@mglaman mglaman May 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where would someone run this? The project wasn't intended to be attached to a Drupal project, but rather as a global CLI command

Copy link
Author

@Greg-Boggs Greg-Boggs May 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The user would run this on any project they are working on where they want access to the command. Does the tool have use for other projects like WordPress or Symphony based ones? If so, then the desired version would be added to the composer file for those projects with the same command.

https://www.sitepoint.com/composer-global-require-considered-harmful/

Copy link
Author

@Greg-Boggs Greg-Boggs May 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brew has some advantages over composer in this regard because it has access to the OS outside of the home folder and doesn't get tied to the dependencies of project based work. But, brew is also a real pain in the neck to maintain for an end user.

Copy link
Author

@Greg-Boggs Greg-Boggs May 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For example, lets say, I have two projects, a WordPress one and a Drupal one. Both have different tools. But, both sets of tools share a dependency on a base library common to many tools. However, Drupal requires version 2 or lower of the dependency and WordPress requires version 3 or higher. If I'm putting tool dependencies in global, there is no path forward and I simply can't work on Drupal and WordPress together on one machine if they share dependencies and aren't on the same versions for their requirements.

Copy link
Author

@Greg-Boggs Greg-Boggs May 8, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With Brew, every project's dependencies are separate even when a tool is installed in a global path.

Copy link
Owner

@mglaman mglaman May 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is why I suggest primarily downloading the Phar from https://github.com/mglaman/drupalorg-cli/releases/latest. I can add a self-updater

Copy link

@NickDickinsonWilde NickDickinsonWilde Oct 17, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about suggesting CGR instead - https://github.com/consolidation/cgr


## Updating

Expand Down