kosmos/chef
8
3
Fork 0
Code Issues 34 Pull Requests 3 Projects 2 Activity

Do not vendor cookbooks using Berkshelf anymore

Browse Source 
Instead, use the Berkshelf support in knife-solo and the
vagrant-berkshelf plugin on Vagrant
This commit is contained in:
Greg Karékinian
2019-04-11 18:16:28 +02:00
parent 87d7c721b1
commit ba6e4220a1
1436 changed files with 12 additions and 110987 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
cookbooks/redis/test/support/keys/README.md
View File

@@ -1,17 +0,0 @@
# Insecure Keypair
These keys are the "insecure" public/private keypair we offer to
[base box creators](http://docs.vagrantup.com/v1/docs/base_boxes.html) for use in their base boxes so that
vagrant installations can automatically SSH into the boxes.
If you're working with a team or company or with a custom box and
you want more secure SSH, you should create your own keypair
and configure the private key in the Vagrantfile with
`config.ssh.private_key_path`
# Putty
If you are using Vagrant on windows, the .ppk file contained here, in the keys directory,
has been generated from the private key and should be used to connect Putty to any VMs that
are leveraging the default key pair. See [guide](http://docs.vagrantup.com/v1/docs/getting-started/ssh.html)
in the documentation for more details on using Putty with Vagrant.