111 Commits (fadda1fe6d7711b05cd21bebc818e9894deffec2)

Author	SHA1	Message	Date
Matthew Hooker	bd5d1fc53a	fix formatting;	8 years ago
Matthew Hooker	f07b791a3f	revert eol whitespace changes	8 years ago
Matthew Hooker	b942c27b21	remove end of line spaces	8 years ago
SwampDragons	734acd9935	Merge branch 'master' into examples-docs	8 years ago
DanHam	c9e6ffa91c	Add warning note about using the 'winrm quickconfig -q' command ... A lot of examples out there on the web make use of this command to configure the instance to allow connections over WinRM. Since the danger is not immediately obvious and the failure because of its use intermittent, we should do our best to advise against its use here.	8 years ago
DanHam	26319ee74b	Additional explanations possibly needed by a user new to Packer or AWS	8 years ago
DanHam	400f210dc2	Set region to use user configured variable	8 years ago
DanHam	69393ef9bb	No need to set execution policy. AWS default is unrestricted	8 years ago
DanHam	6d4e8ab583	Suggest Windows 2008 and 2016 and add name filter	8 years ago
DanHam	e1d88ffaab	Export of AWS creds for users who skipped over the GNU/Linux example	8 years ago
DanHam	10af3770c7	New sample output to match changes	8 years ago
DanHam	5eb68e0573	GNU to make a happy RMS	8 years ago
DanHam	dc45bd381c	Manually set up all required for remote management. Use in-built FW rules ... Use of 'winrm quickconfig' can sometimes cause the Packer build to fail shortly after the WinRM connection is established. * When executed the 'winrm quickconfig -q' command configures the firewall to allow management messages to be sent over HTTP (port 5985) * This undoes the previous command in the script that configured the firewall to prevent this access. * The upshot is that the system is configured and ready to accept WinRM connections earlier than intended. * If Packer establishes its WinRM connection immediately after execution of the 'winrm quickconfig -q' command, the later commands within the script that restart the WinRM service cause the established connection, and consequently, the overall build to fail.	8 years ago
DanHam	e4985ae6f6	Set to use a basic Windows source AMI that qualifies for free tier usage	8 years ago
DanHam	ed0a60bd61	Fix quotes. Use Write-Host in preference to Write-Output	8 years ago
DanHam	1b8238e35f	Fix missing powershell tags around User Data script	8 years ago
DanHam	9daabf3b12	Fix some typo's; Fix markdown and formatting	8 years ago
Charlie Egan	159785e7b0	Fix build image section fenced example formatting	8 years ago
Megan Marsh	157137573c	fix line length	9 years ago
Megan Marsh	be25ad8021	adding pr suggestions to docs improvements	9 years ago
Megan Marsh	48c5c1b8c3	remove unnecessary faqs. Replaced the ami name with a filter.	9 years ago
Megan Marsh	aaa706f4c3	add two more examples to the getting-started documentation, including a windows example.	9 years ago
Matthew Hooker	df64021c16	website: remove remote-builds	9 years ago
Matthew Hooker	0857cfbd4b	removing atlas from docs	9 years ago
raylu	6135b0bf48	Fix ubuntu source_ami_filter examples ... Canonical publishes stable AMIs at ubuntu/images/ and unstable AMIs at ubuntu/images-testing/. Combined with most_recent: true, the old name filter bounces you between stable and unstable.	9 years ago
Megan Marsh	b59383f88a	clean up stale documentation for packer push	9 years ago
James Turnbull	df5e35f408	Updating some references from mitchellh to hashicorp	9 years ago
Megan Marsh	52113dcdb9	update getting started docs to use a filter meaning they should stay up to date longer	9 years ago
liz abinante	5139949d5c	docs: some stuff is easy, some stuff is not ⚡ let's be more descriptive	9 years ago
Matthew Hooker	d30605fdfb	use json markdown syntax	9 years ago
Matthew Hooker	81522dced0	move packer to hashicorp	9 years ago
Seth Vargo	38e0ba8bd3	Fix broken links	9 years ago
Seth Vargo	6b80c21043	Revamp pages and docs to fit HashiCorp brand	9 years ago
Matthew Hooker	57d2fede3f	the digitalocean ubuntu user is root	9 years ago
Matthew Hooker	0d16df1427	clarify docs ... closes #4208	9 years ago
Prashant Kandathil	92e2fe9fe9	Update build-image.html.md (#4471) ... * Update build-image.html.md Without setting this field a user with get a SSH timeout error. * Update build-image.html.md * Update build-image.html.md	9 years ago
Matthew Hooker	67b8b70b8d	update wording	9 years ago
Prashant Kandathil	2e1f18b10a	Update build-image.html.md	9 years ago
JJ Asghar	8db7793ee6	Update parallel-builds.html.md ... It seems that `ssh_username` is required from the packer binary.	9 years ago
Matthew Hooker	09ca600ad9	add note about handling vpc not found errors.	9 years ago
Matthew Hooker	3e186b185d	tutorial WIP	9 years ago
Iain Elder	b18152ca77	More neutral wording clearly refering to docs.	9 years ago
Iain Elder	db63ee3507	Note more secure ways to pass credentials. ... Link to the documentation for new users who want to use AWS's existing credential infrastructure, and provide a familar example.	9 years ago
Purple90	17f3fac39b	Update vagrant.html.md ... Grammar fix. Anyways -> anyway	10 years ago
Matthew Hooker	4ac1f5a105	Merge pull request #3972 from mitchellh/pr-3777 ... instructions for installing with chocolatey	10 years ago
Matthew Hooker	28dc5055d3	rewrite to be complete sentence	10 years ago
Matthew Hooker	b8da25f599	choco install	10 years ago
Arve Knudsen	4e3da3ef54	Improve language	10 years ago
Sourabh Pawar	07e6509bc4	Removed additional whitespace ... Removed additional whitespace	10 years ago
Sourabh Pawar	103a8a9223	Note for executing the first build on Windows ... The first packer build command includes passing AWS access key and secret key as variables. On Windows, the single quotes must be replaced with double quotes or an AWS error occurs. This may not be obvious to everyone, hence a note. The AWS error (as below) is not adequately self-explanatory. Build 'amazon-ebs' errored: Error querying AMI: NoCredentialProviders: no valid providers in chain. Deprecated. For verbose messaging see aws.Config.CredentialsChainVerboseErrors	10 years ago