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

Add supported OS list to readme #859

Merged
merged 1 commit into from
Aug 2, 2016
Merged

Conversation

vjeffrey
Copy link

@vjeffrey vjeffrey commented Aug 2, 2016

#842

Let me know if that's ok/if more/different things are needed! :)
@chris-rock


Remote Targets

Platform | Versions | Architectures | Package Format
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we do not need the package format column for remote targets.

Copy link
Author

Choose a reason for hiding this comment

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

yup. that makes sense! just pushed up the fix

@vjeffrey vjeffrey force-pushed the vj/add-supported-os-to-readme branch from 84e389a to b27d9a5 Compare August 2, 2016 14:43
@chris-rock
Copy link
Contributor

Forgot that, but we should add a warning for windows 2008 and windows 2008 R2 e.g. via a *. For those we need a specific version of powershell #633

* RHEL 6 & 7
* Ubuntu 12.04+
* Windows 7+
* Windows 2012+
Copy link
Contributor

Choose a reason for hiding this comment

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

Could we use the same table style as above?

@arlimus
Copy link
Contributor

arlimus commented Aug 2, 2016

Awesome job @vjeffrey ! would love to have the table style on the list below

@vjeffrey vjeffrey force-pushed the vj/add-supported-os-to-readme branch from b27d9a5 to 3dcf866 Compare August 2, 2016 15:11
@vjeffrey vjeffrey force-pushed the vj/add-supported-os-to-readme branch from 3dcf866 to 485e765 Compare August 2, 2016 15:13
@vjeffrey vjeffrey force-pushed the vj/add-supported-os-to-readme branch from 485e765 to ffbe540 Compare August 2, 2016 15:15
@vjeffrey
Copy link
Author

vjeffrey commented Aug 2, 2016

@arlimus @chris-rock updated :)

Gentoo Linux | | x86_64
Arch Linux | | x86_64

* Powershell with Windows Management Framework 5.0 required
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe: For Windows 2008 and 2008 R2 an updated Powershell (Windows Management Framework 5.0) is required.

@chris-rock
Copy link
Contributor

Looks great. Tables are much better. Lets just make the Windows 2008 requirements a little more clear and we are good to go.

@vjeffrey vjeffrey force-pushed the vj/add-supported-os-to-readme branch from ffbe540 to 5b80875 Compare August 2, 2016 15:56
@vjeffrey vjeffrey force-pushed the vj/add-supported-os-to-readme branch from 5b80875 to 987a0d5 Compare August 2, 2016 15:57
@vjeffrey
Copy link
Author

vjeffrey commented Aug 2, 2016

should probably make sure this info eventually gets to: https://docs.chef.io/platforms.html

@chris-rock
Copy link
Contributor

@vjeffrey this is only a restriction for inspec

@vjeffrey
Copy link
Author

vjeffrey commented Aug 2, 2016

ya, I meant more like, is inspec gonna have a section on that page, since automate and a bunch of things are listed on there, as a one place to look at chef-things requirements? just curious. also, why is the build failing? that error msg is pretty vague..i assume it's just a transient error thing?

@chris-rock chris-rock merged commit 8b196bd into master Aug 2, 2016
@chris-rock chris-rock deleted the vj/add-supported-os-to-readme branch August 2, 2016 17:54
@chris-rock chris-rock modified the milestone: 0.29.0 Aug 4, 2016
@chris-rock chris-rock added the Aspect: Docs Write the Fine Manual label Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aspect: Docs Write the Fine Manual
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants