Hi Christoph and Alex,

We have "new secure VLAN" templates for the pipeline hosts which I am currently testing. These have no access to download anything from the internet. Therefore we had to modify the dashboard cookbook so that there is no dependency at all on any external repository, this includes the Ubuntu key-server. One piece of this task, was that the dash-debian-repo recipe in chef-dash which contacts the Ubuntu key server also had to be changed. After discussing, we decided to make chef-dash more flexible to allow usage of a corporate repo to install dashboard packages. We will add the dash packages key via "apt-key add" if using a corporate repo. So,

1. Introduce an attribute "use-corp-repo" which can be set to "true" or "false". Defaults to "false" to use the Pingworks repo and Ubuntu key server. if set to "true" downloads the dashboard packages (scripts, front-end and back-end) from the corporate repo and provisions the dash packages key from a cookbook file using "apt-key add".
2. However this means we have to also move the install_method choice over to chef-dash. So I will introduce a case statement on the value of the "use-corp-repo" attribute, which sets the install_method to "dpkg" when "use-corp-repo" is "true" and sets it to "apt" when it is "false"
3. This means splitting all package installation recipes into two choices for "dpkg" and "apt" install methods based on the value of "use-corp-repo".

Hey guys,
I have been using your cookbook for some time, and on my debian7 box it worked quite well, but after changing to debian8 this happens:
`bash[enable_apache_site] action run

       ================================================================================
       Error executing action `run` on resource 'bash[enable_apache_site]'
       ================================================================================

       Mixlib::ShellOut::ShellCommandFailed
       ------------------------------------
       Expected process to exit with [0], but received '1'
       ---- Begin output of "bash"  "/tmp/chef-script20160210-1181-d4epna" ----
       STDOUT: 
       STDERR: ERROR: Site dash-prod does not exist!
       ---- End output of "bash"  "/tmp/chef-script20160210-1181-d4epna" ----
       Ran "bash"  "/tmp/chef-script20160210-1181-d4epna" returned 1`

After some test it seem the problem is that the config file is called "dash-prod" and not "dash-prod.conf"

vagrant@default-debian-8:/etc/apache2/sites-available$ sudo a2ensite 000-default.conf dash-prod default-ssl.conf vagrant@default-debian-8:/etc/apache2/sites-available$ sudo a2ensite dash-prod ERROR: Site dash-prod does not exist! vagrant@default-debian-8:/etc/apache2/sites-available$ sudo mv dash-prod dash-prod.conf vagrant@default-debian-8:/etc/apache2/sites-available$ sudo a2ensite dash-prod Enabling site dash-prod. To activate the new configuration, you need to run: service apache2 reload

Although stated in the readme:

Supported Platforms
Debian 7.x (wheezy)

getting the URL from the kitchen.yml:

➜  pingworks-chef-dash git:(master) curl -I http://vagrant.pingworks.net/opscode_debian-7.7_chef-11.16.4-1.box
HTTP/1.1 404 Not Found
Date: Mon, 18 Apr 2016 15:33:27 GMT
Server: Apache/2.2.22 (Debian)
Vary: Accept-Encoding
Content-Type: text/html; charset=iso-8859-1

➜  pingworks-chef-dash git:(master)