Project home page and easy-deployer. about dokku-alt

[ayufan]

Looks great. Maybe we can extend .deb package and bootstrap.sh and replace dokku-installer.rb with manager? I think that .deb package is still the most convenient one.

Do we really need "wizard"? I think that as long as we type somewhere VHOST and setup user account everything could be done automatically.

As for web page we can use: http://dokku-alt.github.io. I created https://github.com/dokku-alt/dokku-alt.github.io and gave you permission for push.

Give me some instructions how to set up dokku-alt-manager and I'll think about best way to integrate it with project.

[romaninsh]

@ayufan , I don't seem to have permissions for that repository, but I've committed the files here:

https://github.com/romaninsh/dokku-alt.org/

If you think it's decent, copy to your github page and check my permissions again, please.

[ayufan]

You still have invitation pending. [image: Inline image 1]

On Thu, Sep 4, 2014 at 3:51 AM, Romans Malinovskis <[email protected]

wrote:

@ayufan https://github.com/ayufan , I don't seem to have permissions
for that repository, but I've committed the files here:

https://github.com/romaninsh/dokku-alt.org/

If you think it's decent, copy to your github page and check my
permissions again, please.

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

Kamil Trzciński

[email protected]
www.ayufan.eu

[romaninsh]

Awesome. And it's up: http://dokku-alt.github.io/

[romaninsh]

You'll need jade compiler if you want to change it.

[marvinroger]

The UI Manager is a great idea. Assuming it is going to be realtime with websockets, there must be a way to be aware of things done by dokku. Imagine the following scenario:

• The UI Manager is opened
• The user issues a Dokku command that add an ENV variable
• The UI Manager has no way to know that an ENV variable was added as there is no signalization from the dokku script

To fix this issue, I think a named pipe (FIFO) issuing json objects would be a good idea as this is pretty simple to implement in both sides (script and web UI). Then the following scenario happens:

• The UI Manager is opened
• The user issues a Dokku command that add an ENV variable
• Dokku issues kind of a { "type": "config:added", "app": "myapp", "value": "NODE_ENV=production" } to the pipe
• The UI Manager backend detects a new line in the named pipe and parses it
• The UI Manager backend sends the refreshed data using Websockets
• The UI Manager frontend has refreshed data

Due to the realtime nature of the UI, Node JS with Socket.IO would be a decent choice.

What do you think about it?

[romaninsh]

UI manager communicates with dokku through "ssh" shell, so it takes a while to execute command. Currently web server simply waits for response and browser needs to wait too. This works OK and using PHP and Agile Toolkit was quite simple to develop, which is what I was looking for anyway.

[marvinroger]

I will try a different approach using Angular, node and ws, just to see ;)
So you are opening a root SSH connection?