Blank dashboard after install with docker

Hi,
I'm trying to install Loomio for Framasoft, a french non profit NGO who wants to degooglize the internet :)
And I have the same problem as in this thread : "sing_in" and "sing_up" forms seems to work, I'm redirected on dashboard page but it's blank.
I'm in a "production" environment, inside a docker container, so I'm surprised that I should have to build the Angular app as it saids in the thread.
This is the log file I get on a fresh install.
Is there something to do on my side or the documentation is too fresh (I saw that the loomio-deploy repository is young) ?

JosephK Fri 8 Apr 2016 3:10PM
I reinstalled from scratch before asking for help here (I've tried many things) so the docker image is up to date actually.
James Kiesel Fri 8 Apr 2016 8:05PM
Definitely appears that the app is unbuilt; have you tried entering the container, navigating to /angular
, and running gulp compile
?
Any other thoughts on why the app might be unbuilt in the docker container @robertguthrie ?

Robert Guthrie Sat 9 Apr 2016 3:29AM
Thanks for the bump.
Have a look at https://github.com/loomio/loomio/blob/master/Dockerfile ( https://github.com/loomio/loomio/blob/master/Dockerfile )
Is that how we should build assets?
If you push a new master the Docker image is rebuilt.

Robert Guthrie Sat 9 Apr 2016 11:22PM
@josephk I hope to get a chance to look into this tomorrow.

Robert Guthrie Tue 12 Apr 2016 4:52AM
@josephk This problem has been fixed now.
To get the latest docker image with the fix run docker-compose pull
when logged into your server, in the loomio-deploy directory.

JosephK Tue 12 Apr 2016 8:40AM
Not better. (I describe all I've done. I'm a newbie in using docker maybe I've done something wrong)
First, I've run docker-compose pull
. Nothing changed so I restart the containers docker-compose restart
then I tried to run the commands in the dockefile :
docker run -i -t loomio/loomio /bin/bash
cd angular
npm install
npm rebuild node-sass
node node_modules/gulp/bin/gulp.js compile
cd ..
bundle install
And it's the same result. The files missing pointed to /client/0.19.103, the same path as before.
So I tried to resinstall (removed all container then docker-compose run web rake db:setup
and docker-compose up -d
), the only difference il that the home page is redirected to /marketing instead of /sing_in.
Minified css and js are still missing but now they point to /client/0.19.105.
BTW, I think there is an error with the crontab file :
- the docker container is named loomiodeploy_web_1 not loomio
- and certificates are placed in /root/loomio-deploy/certificates as it said in the tutoriel not /loomio/config/letsencrypt
Bzzrd Wed 13 Apr 2016 12:45AM
Hello @josephk ,
I've found a workaround to the blank dashboard problem,
it seems that the container search for a globally installed gulp that doesn't exist during the following command:
RUN bundle exec rake deploy:build
you can then restore the assets by connecting to the running container and installing gulp before running the two rake commands:
docker exec -it loomiodeploy_web_1 bash
npm install -g gulp
bundle exec rake deploy:build
bundle exec rake assets:precompile
for me it restores the ui.
Cheers.

Robert Guthrie Wed 13 Apr 2016 3:47AM
Thanks for all your patience @josephk. I really appreciate it - I think you might be the first person to try all the new docker based stuff, so please know that I'm grateful for your feedback.
I've updated and tested it just now, please try docker-compose pull
again and you should see it pull new images.
Then run docker-compose down
and docker-compose up -d
to restart the services. You can also run docker-compose logs
to see what is going on under the hood.
Thanks for the heads up about the crontab. Please modify your /root/crontab as necessary and I'll make the changes upstream soon.

Robert Guthrie Wed 13 Apr 2016 3:52AM
sorry I spoke too soon. I'm working on it now..
GasparI · Fri 8 Apr 2016 2:28PM
Hi Joseph!
Yesterday the master build was failing, now it's green again.
I'm not sure there is a connection but maybe just running the last few commands (Docker update) you could get it running properly.