Updates to support PHP on current dokku

[drmikecrowe]

Does the following:

1. Creates user dokku as uid/guid 1000 and runs server as this instead of nobody. This supports the very nice dokku-volume plugin, which mounts volumes as user dokku (uid/guid 1000). Otherwise, unable to write to persistent volumes
2. Creates /root/bin prior to downloading/installing jq
3. If adding nginx-include parameters, the following error occurs:

nginx: [emerg] could not build the types_hash, you should increase either types_hash_max_size

To resolve, adding types_hash_max_size 2048;

[bobmaerten]

Wooaah. Never thought that this repo would be spotted, nor forked and patched!
Thanks to propose your commits, I'll take a serious look at it.

[drmikecrowe]

Haha, no doubt. Hopefully, mine will escape notice too.

However, I was trying to get a hefty PHP CMS package to run in dokku, and I couldn't get the CHH/heroku-buildpack-php to work either. I think (I was trying any buildpack I could find) yours was the closest to what I hoped to do, if I could get it running.

One of the things that drove me nuts is the cache directory I needed in my container. I couldn't get any script to create a web/tmp directory and make it 0777 permissions. I tried everything, and I don't know what I was missing. I finally had to put it in a persistent volume (which I actually don't really want) to get it to work. That's when I found the volumes all showed uid=1000 instead of root.

From what I could see, no PHP app could run in Dokku at this time, and I don't understand why it hasn't been addressed.

[bobmaerten]

I have to admit I quit early on the problems you exposed, and quite amazed
by the tricks you found.
I think everybody end up on the same level of "enlightenment": dokku does
not run PHP well, and try something else, like recent docker langage images.

2014-09-29 13:45 GMT+02:00 drmikecrowe [email protected]:

Haha, no doubt. Hopefully, mine will escape notice too.

However, I was trying to get a hefty PHP CMS package to run in dokku, and
I couldn't get the CHH/heroku-buildpack-php to work either. I think (I was
trying any buildpack I could find) yours was the closest to what I hoped to
do, if I could get it runnning.

One of the things that drove me nuts is the cache directory I needed in my
container. I tried everything, but couldn't get any script to create a
web/tmp directory and make it 0777 permissions. I tried everything, and I
don't know what I was missing. I finally had to put it in a persistent
volume (which I actually don't really want) to get it to work. That's when
I found the volumes all showed uid=1000 instead of root.

From what I could see, no PHP app could run in Dokku at this time, and I
don't understand why it hasn't been addressed.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[drmikecrowe]

I know, but I somehow keep coming back because it seems to really be the easiest solution for quick, single-instance deployment.

I've been looking for an alternative, but Flynn and Deis seem like overkill (though I may take a serious look a Deis).

Would you mind pointing me to the alternative you use? I'd like to check it out

[bobmaerten]

My alternatives are currently :

• docker containers launched from custom image like docker-wallabag (source code mounted through a volume)
• dedicated PHP VM updated with any kind of SCM workflow

An acquaintance of mine (ping @tclavier) owns and runs Deliverous maybe you could have a look to their repos, or try their services.