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

install phpcs via composer #608

Closed

Conversation

cfoellmann
Copy link
Member

phpcs needs to be installed via composer to reduce the provision process significantly. My last vagrant provision took 7039 seconds! mostly due to git clones.

@cfoellmann
Copy link
Member Author

I fixed the oversight of setting the correct path to the WP coding standards.
This should save 5-10 minutes for the first provision.

@cfoellmann
Copy link
Member Author

@jeremyfelt please add needs-feedback label

@jeremyfelt jeremyfelt added this to the Future Release milestone Jul 3, 2015
@jeremyfelt
Copy link
Member

Thanks @cfoellmann!

  • Is the switch in directories from /srv/www/phpcs/CodeSniffer/Standards/WordPress to /srv/www/phpcs-wordpress going to mess with any current installations?
  • Why sudo now on the phpcs lines?

@jeremyfelt
Copy link
Member

/cc @westonruter for feedback too 😄

/srv/www/phpcs/scripts/phpcs --config-set installed_paths ./CodeSniffer/Standards/WordPress/
/srv/www/phpcs/scripts/phpcs --config-set default_standard WordPress-Core
/srv/www/phpcs/scripts/phpcs -i
sudo /srv/www/phpcs/scripts/phpcs --config-set installed_paths /srv/www/phpcs-wordpress/
Copy link
Contributor

Choose a reason for hiding this comment

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

This absolute path will break PHPCS when invoked from outside of Vagrant. This is why a relative path is used currently.

@westonruter
Copy link
Contributor

The path to the WPCS shouldn't be changed.

@jeremyfelt jeremyfelt removed this from the Future Release milestone Feb 26, 2016
@jeremyfelt
Copy link
Member

@cfoellmann do you want to address the path naming and update the PR accordingly? It seems like this would help as long as we're consistent with the location.

@jeremyfelt
Copy link
Member

I think we need to regroup on this in a new pull request. I've opened issue #922 to describe the intent here. Thanks for the work on this @cfoellmann. :)

@jeremyfelt jeremyfelt closed this Jun 14, 2016
@cfoellmann cfoellmann deleted the feature/phpcs branch April 2, 2017 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants