-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
Simplified Deployment - ONE Docker Image for both Backend + Frontend #537
Comments
Work in progress: papermerge/papermerge-core#124 |
Please check here the new, simplified docker compose file. Use it only for papermerge/papermerge:2.1.8 docker image (and later). Notice there is nothing about traefik, frontend/backend, web sockets in it - now there are just 4 services which, I guess, should make perfect sense to have around:
Now, the simplest way of lunching papermerge:
will include UI as well, on other words, if you point your browser to http://localhost:16000, you will see papermege login window. If you experience any "gray screen", please either delete cookies for that domain (localhost:16000) or start in incognito mode. Documentation update: work in progress.... |
This is great, now I can login (it was impossible before, even in dev version it didn't work properly). Is OCR working in this version? I have uploaded one item in Inbox, but it keeps showing 0 and it wont ocr (gray circle). I also don't see an option to start ocr. Also drag'n'drop didn't work (should it?), I have uploaded file by manually choosing it via upload icon. |
@homehtha did you start it with docker compose ? Is worker up and running ? Please provider here logs from both worker and backend as per docker compose |
@ciur
Environment variables
The all 4 containers are running. Thats the log from worker
|
"import" and automates features were part of 2.0.x This new docker image ships 2.1.x version which does not include automates |
Problem
Current deployment, which is separated as backend docker image and frontend docker image is a pain to setup.
In order to be marginally useful you need to create a docker compose with at least 3 services:
I received lots of complains reported as bugs because of (usually traefik) misconfiguration. It makes perfect sense, since traefik is not the most intuitive tool to configure, but also it is difficult to reason in terms of routing between frontend and backend.
Also, there is another problem with above approach - the backend and frontend version should be compatible e.g does backend version 2.1.7 work with frontend version 2.1.2?
Solution provided below will solve this problem as well.
Solution
Solution is relatively simple - is to copy static assets directly into backend, and let backend serve those static assets.
In other words - instead of three docker images configuration (backend, frontend, traefik) you will be able to use only one - backend!
I am currently working on this.
The text was updated successfully, but these errors were encountered: