Error during net-new Docker & OpenEats Install: MariaDB "Access denied for user 'root'@'localhost'" about openeats HOT 3 CLOSED

Hi,

Thanks for the detailed report. I will try and replicate the issue. However I'm not sure if this was caused by the DB. Regardless of if the DB/API were working or not, the UI should load (you just won't get any content).

If you were getting a blank screen when trying to load the App in a web browse, then there was something funky going on with the UI. One potential cause of this could be the extra time that the UI needs on a first time boot to load all the NPM packages. After the first boot the UI caches all the NPM packages so you don't need to install them again.

Back to the DB issues. The Postgres container will use the settings you have in the env_prod.list file to initialize itself. So if these values weren't initialize, the API uses the defaults: https://github.com/open-eats/openeats-api/blob/master/base/settings.py#L28-L32

Couple closing questions for you:

• Is the App working as expected now: IE you can use it.
• Are you trying to re-use another dockerized DB container (outside of the one that OpenEats will create)?

-Ryan

from openeats.

To answer your closing questions first:

1. "Is the App working as expected now: IE you can use it". No, however I now believe this to be unrelated to this problem-report (see below).
2. "Are you trying to re-use another dockerized DB container?". No, the only DB involved is the one created during OpenEats' installation. This also includes no external (non-dockerized) DB instances.

During my previous installation attempt, I waited approx. 30 secs before hitting the main page (I think I read about 30 secs somewhere in the doc'n). This time, to try and confirm your first-time-boot suspicion, I blew away all OpenEats containers, images, volumes and networks, and did a full reinstall from scratch, waiting 5 minutes after quick-start.py completed before hitting the main page. As you suspected, this time the main page got successfully (sort of) served up.

So it looks like, although no-password warnings are still being thrown, this does not appear to be inhibiting presentation of the homepage after initial installation. Whether or not those no-password warnings allude to future problems I cannot say, since I cannot yet fully utilize the app properly.

Unrelated Issues

The app still does not function correctly. However I suspect this to be caused by my use of an external (non-dockerized) Apache reverse-proxy (for HTTPS), combined with OpenEats apparently serving up static-content URLs. I will troubleshoot this separately, as I believe it's unrelated to this problem report. (Hopefully it's mis-configuration on my part.)

Thanks again for your quick response and sorry for the red-herring.

from openeats.

Good to know that was the issue. I'll be sure to update the docs to add that warning in there.

As for the HTTPS issues, you might wanna checkout this issue: open-eats/openeats-api#15

from openeats.