Issues faced when installing ledokku in an existing Dokku server with deployed apps

[j-a-h-i-r]

This is a general report of the issues I faced when following the installation wiki (https://www.ledokku.com/docs/installation). I ended up following the manual installation steps (https://www.ledokku.com/docs/advanced/manual-installation) to get ledokku working.

Services were not created/linked

When I listed the redis and postgres services, there was no service created for ledokku

dokku redis:list
# only my existing redis services. No ledokku

dokku postgres:list
# only my existing pg services. No ledokku.

So I had to create and link these services,

dokku redis:create ledokku
dokku redis:link ledokku ledokku

dokku postgres:create ledokku
dokku postgres:link ledokku ledokku

Then deployed ledokku from image and set up config values,

dokku git:from-image ledokku ledokku/ledokku:0.7.0

IP was being used by another app

An existing app was being served on port 80. So visiting my droplet's IP showed that app. But the previous step deployed the app at ledokku.example.com. So I added a DNS record for ledokku.example.com and the UI finally appeared.

GitHub redirection link broken

GitHub was redirecting me to my IP address. But as another app was served on the IP, I had to manually replace the IP part in the URL to ledokku.example.com. I guess setting ledokku.example.com in the DOKKU_SSH_HOST config variable would have fixed this issue?

[akhil-naidu]

@j-a-h-i-r

An existing app was being served on port 80. So visiting my droplet's IP showed that app. But the previous step deployed the app at ledokku.example.com. So I added a DNS record for ledokku.example.com, and the UI finally appeared.

Thanks for your general insights; we will make our installation script look into the existing dokku apps to provide more flexibility.