-
Notifications
You must be signed in to change notification settings - Fork 19
Error at dokuen create #18
Comments
It looks like it's running
Thanks! |
Here it is:
|
Ah! In your .gitolite.rc file, the
|
After correcting the
Have I missed something? In doubt, i will make a new clean install. |
@paulollivier If you just |
Hi @pauloliver, @peterkeen, I was having the same problem, and I've got an idea as to where it comes from. Depending on how you install RVM, it can put the RVM A quick fix is to send the command |
Wrong. @jphastings this might help https://gist.github.com/dd7ffd2dbde27bc32446, but prepare for long journey. Btw, dokuen leaves running processes when scaling down |
@teamon that looks like super useful information ... if I could read Polish. Do you think you could provide an English translation of your notes? Also I was sure I fixed the running process issue at some point. I'll look into it. It's possible I fixed it on my own install and didn't push a new gem out. |
Great, thanks. So there's problems on multiple fronts :) First off it looks like Dokuen is not working with more recent versions of Second, the nginx path is hardcoded. That one is trivial to add a config Third, there's a problem with Mason. I'll have to look into that one and Fourth, Mason is not compatible with Ruby 1.8.7. I'm not sure if I'll be On Fri, Oct 26, 2012 at 4:34 PM, Tymon Tobolski notifications@github.comwrote:
|
+1 I had no success, it seems gitolite doesn't see dokuen |
So, I tried installing it on an Ubuntu-server 12.04 LTS. Everything went fine, except on
dokuen create --aplication=name
I followed standard installation procedure, as detailed in the README.
Please find the full command and error log below.
I am at your disposal for any further test or information.
The text was updated successfully, but these errors were encountered: