-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation on docker #43
Comments
This was super helpful |
Also, before gem bundle, i had to install
|
Hello - I have been trying to get this running on Ubuntu server 18.10 - which are you using? I have not been able to get it to run - not a whole lot of documentation out there, and I am new to ruby on rails - thanks for your help! |
This is as far as I can get: I have tried again and again and this is the highest it installs |
@1kidvidiot I changed line 33 in Dockerfile.development from RUN gem install bundler to: And the installation worked! |
Hello all, After change line 33, I got an new error:
|
@celsoagra add |
Help me pls!!!! E: Sub-process /usr/bin/dpkg returned an error code (1) |
What you need to do is open the Dockerfile.developer and add the following line before the Replace $PACKAGENAME with the package that is causing the issues. More info here |
We forked this repository and applied several of the fixes described in this thread plus some others to make it work. Feel free to clone from https://gitlab.com/gruporhes/fluxday |
Hi,
Had some issues with installing this software on docker, succeeded eventually just wanted to share:
DB_HOST=db to DB_HOST=fluxday-db
image: mysql to image: mysql:5.6
(works with 5.6 tag, doesnt work with the latest mysql version)
7.docker-compose up -d --build --remove-orphans
9.rake db:create
10.rake db:migrate
11.rake db:seed
I also created subdomain and set nginx as frontend and created a proxy to localhost:3000.
Hope this helps.
If you have any problems with these steps, Im here to help.
BTW this is a great software, worth of extra figuring out.
Best regards,
The text was updated successfully, but these errors were encountered: