fgrehm / chef-dokku Goto Github PK

We need to tag whatever the SHA was for the v0.2.0 release. Also should probably tag releases in the future as well.

Implement LWRPs to handle working with the underlying dokku CLI

Keeping a copy of the stack locally and providing it to the bootstrap script while developing the cookbook comes in hand as it lowers the initial provisioning time a lot :)

0.0.1 was mostly an experiment and starting from 0.2.0 I expect things to be more stable and that people are likely to start using it a bit more. So it'll be nice to keep track of changes as not knowing what changed between releases is a big PITA :P

Add the default vagrant public key to the list of allowed users

Hey there,

I'm adding a new app to a server. When I do the following steps:

• add an environment variable for the app "staging.myserver.com"
• run chef-client on staging.myserver.com
• push a new app to [email protected]:staging.myserver.com

I get an error from the push:

ra:app(dev-procfile) ryan$ git push staging dev-procfile:master
fatal: 'staging.ramen.is' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
ra:app(dev-procfile) ryan$

I'm guessing git is mad that the /home/dokku/staging.myserver.com directory exists, but only contains the ENV file and is not a git repo.

Am I just using this wrong, or have I hit a race condition?

The checksum for https://s3.amazonaws.com/progrium-pluginhook/pluginhook_0.1.0_amd64.deb is now 0a9f89ad3fd12fbeed604af8c01b0f6d3ab98e273c89a5495cd877e6a46ef8f3. I don't know whether it should have changed or not.

Instead of relying on a Vagrantfile for chef-solo testing, I'd like to switch us over to test-kitchen. This combined with serverspec tests should help keep us from regressing along with maintaining behavior with the base dokku project.

It'll also help me since I use parallels instead of VirtualBox 😄