BrambleGB

Hi sorry I forgot to answer this. What you need to do is edit the nginx config files both within the openeats docker, and your lets encrypt nginx docker (if you are using it). For the openeats docker: 1. Copy the original default.conf file located at /etc/nginx/conf.d 2. Make a new folder in your Unraid with the default.conf (mine is at /mnt/user/configs/openeats/default.conf) 3. Edit the default.conf file, and add "client_max_body_size" to the server {} block It should look like this: (Note that 40M here means 40 Megabytes, which is probably bigger than what you need. You can set this to what you want, the default is 1M) upstream api { ip_hash; server 0.0.0.0:8000; } server { listen 80; server_name localhost; client_max_body_size 40M; location / { root /var/www/html/openeats-static/public-ui; try_files $uri $uri/ /index.html; } location /static/ { root /var/www/html/openeats-static/public-ui; gzip on; gzip_types text/plain text/xml text/css text/comma-separated-values text/javascript application/x-javascript application/javascript application/atom+xml; expires max; } location /api/ { proxy_pass http://api; proxy_set_header Host $http_host; } location /admin/ { proxy_pass http://api; proxy_set_header Host $http_host; } location /static-files/ { root /var/www/html/openeats-static; try_files $uri /static-files/$uri; } location /site-media/ { root /var/www/html/openeats-static; try_files $uri /site-media/$uri; } } 4. Mount your new folder against /etc/nginx/conf.d/ Now for the lets encrypt docker if you have it: 1. Go to /mnt/user/appdata/letsencrypt/nginx/nginx.conf and add "client_max_body_size" as well to the http {} block 2. Go to /mnt/user/appdata/letsencrypt/nginx/site-confs/default and add it to your server {} block 3. Go to /mnt/user/appdata/letsencrypt/nginx/proxy-confs/www.subdomain.conf (or whatever subdomain you use) and add it to the server {} block Let me know if this works or doesn't work

I mean the "USE DATABASE mysql" was wrong, it's just "USE mysql" You could try recreating the container and then attempting the same thing. I think I had a similar problem but can't remember anymore how I fixed it.

Hmm what if you try the update command without changing database to mysql (also oops the command I gave was wrong)

You're looking at the openeats database, you need to open the "mysql" database in adminer, or open a console in the mariadb docker. I haven't used adminer really, but if you open a mariadb docker console You can login using mysql -u root -p [type in root password you set in the container] USE DATABASE mysql; You then have to run: UPDATE mysql.user SET Host='%' WHERE User='openeats'; FLUSH PRIVILEGES;

When you log into the db with Adminer, what is the host for the openeats (or if you renamed it) user in the mysql.user table? It should be 'openeats'@'something', where you need to replace the something with either '%' or the docker ip of your openeats container (172.18.0.5:80 for me) Example: These are my users, I called mine "rob"

I would love to make my own custom website, but that would take quite some effort. I have updated the Docker container again, forgot to add the part in the startup script that changes your locale. Edit: There was an issue with CRLF line endings, the latest container should work now (works for me)

I have updated the dockerfile again with the (one) latest change (grocery sorting). However updating other packages breaks a lot of things, the project is using quite a few deprecated features and packages.

There are 2 ways you can do this without having to change the source code itself: 1. Bash in and replace the .png file in /var/www/html/openeats-static/public-ui/images 2. Copy the entire /var/www/html/openeats-static/public-ui/images folder to somewhere on your unraid drive, replace the images, then mount that folder to /var/www/html/openeats-static/public-ui/images, replacing the original location. The first way is quicker, but you lose the change every time you edit the container settings The second way persists but takes a bit more effort I think the size doesn't matter too much as long as you keep the same ratio, as it should resize itself to fit. Let me know if you want step by step instructions for either.

Try adding these as well. And then using the added account in the openeats container settings

The last error is explainable because you only allow openeats@localhost but you are connecting from [email protected] Can you share the settings that you are starting the mariadb container with?

When you open the website, does it say you are already logged in?

Genau, alles gleich einstellen. Dann wenn du es an machst und die logs anguckst, sollte es sagen "current locale is en, new is de", und hoffentlich ist es auf Deutsch.

Du musst "Enable additional search results from dockerHub:" an machen, under Other-> Settings. Und dann "Click Here To Get More Results From DockerHub" drücken wenn du nach openeats suchst.

You cannot change the name, you have to download my container from Community Apps( see photo) and use the same settings. You may need to delete the current one as having two containers with the same name can cause issues. Ich kann auch Deutsch falls du willst das ich es in Deutsch schreibe.

Ok I was able to get it to work. Basically, if NODE_LOCALE at runtime is different from build time, it will rebuild the web files. You'll have to run my personal version from https://hub.docker.com/repository/docker/bramblegb/openeats. It works the same as Cornelius' as I have based it off it. @CorneliousJD if you want to add it to yours, the way I did it was: Add RUN echo $NODE_LOCALE > /current_locale To the Dockerfile after the ENV statement Then add this part to start.sh after the sed and before the nginx # Rebuild the web service if locale has changed if [ -f /current_locale ]; then OLD_LOCALE="`cat /current_locale`" if [ "$OLD_LOCALE" != "$NODE_LOCALE" ]; then echo "Current locale is $OLD_LOCALE, new is $NODE_LOCALE" # Rebuild and update locale cd /openeats-web && yarn start && echo $NODE_LOCALE > /current_locale fi fi

I was able to get it working in German (see attached image). I am using my own dockerfile though and had to rebuild the image with NODE_LOCALE=de Let me know if you need help with that, or I can push my own forked version for you.

You probably haven't rebuild the container from scratch, and it was pulling it from cache. You can try using docker build with --no-cache --pull I believe the NODE_LOCALE fix would also require a rebuild? Since the environment variables are captured by webpack at build time, which then isn't updated if the user changes it. 1. Create the folder where you want to put the config file. I will use "/mnt/user/configs/openeats" Open the unraid console and type "mkdir -p FOLDER_NAME" 2. Create the "default.conf" file inside that folder. In the unraid console, type "touch FOLDER_NAME/default.conf" 3. Copy my current configuration file from https://pastebin.com/CaPikhGr to a text editor and set the client_max_body_size (im using 40MB for no reason) 4. Copy the content to the default.conf file you created. You can use vi, or echo, or cat. Quick way with echo is running the command "echo "PASTE THE CONTENT HERE, DON'T FORGET QUOTATION MARKS" > FOLDER_NAME/default.conf" 5. Edit the openeats container, select "Add another Path, Port, Variable, Label or Device", choose path. Name doesn't matter, container path is "/etc/nginx/conf.d/", and host path is "FOLDER_NAME" 6. Restart the container and the new configuration should work. You may also have to edit the LetsEncrypt configuration, but there are other tutorials for that.

Sorry, just got around to it. https://hub.docker.com/repository/docker/bramblegb/openeats/general https://github.com/jzyrobert/openeats-docker Do note that this is based off a personal fork right now, not the original one.

Btw @CorneliousJD, you are using a rather old build of the UI and API (pre december 2018), which is causing the admin page issue. It was fixed by the author on 31 Dec 2018 (see https://github.com/open-eats/OpenEats/issues/74#issuecomment-447832673) Even though your docker file says it pulls from master, it hasn't been rebuilt in a long time. The nginx, node and yarn versions are also quite old, and all the custom setup in your dockerfile can be replaced by simply apk add --update nodejs apk add --update yarn As the code itself also uses somewhat outdated packages, I had to fork it, update it and make my own dockerfile based off it. It also ended up saving about 50MB on the built image.

I bashed in, copied the default.conf, and create my own default.conf (with the added client_max_body_size inside the http {} braces). Then I mounted that folder (e.g. /mnt/user/configs/openeats/) to /etc/nginx/conf.d/ and restarted the container. Ideally nginx can be removed, as people already run it separately. You also have to remember to change it if you're running an extra nginx container (e.g. the LetsEncrypt one)

Thanks, I had to do this as well. I believe this is more to do with MariaDB defaults, which this container doesn't change at the moment. Additionally, I had to overwrite /etc/nginx/conf.d with my own one in order to set the client_max_body_size A default of 1MB is kind of very small for images.

Sorry, I mean the one where you can't access the admin page over the reverse proxy.

Any idea if the admin issue is to do with the docker setup, the web server itself, or the reverse proxy?