can not see any 'projects' in the projects page with docker compose depoly #212
Comments
|
This is strange since from the logs it seems like everything is working fine. I tested the docker-compose setup with WSL+Ubuntu-16.04 (docker-compose 1.24.0 and docker 18.06.1-ce) as well as a real install of Ubuntu-18.04 (docker-compose 1.21.2 and docker 18.09.6) and everything works fine. Perhaps there's something different about CentOS. A couple of avenues to investigate:
|
|
@c-w thanks for attention, and the version of docker-compose is by the way, I can see the |
|
@littleji I'm unable to reproduce the behavior you reported on a fresh CentOS 7.5 install so there may something peculiar about your machine. Could you please confirm that the steps below look representative of your setup? Step 1: Create a new CentOS VM on Azure Step 2: Connect to the VM Step 3: Setup Docker (guide) Step 4: Setup doccano Step 5: Access projects page Go to http://{INSERT_IP_OF_VM_HERE}:8000/projects/ and log in with |
|
I am having the same issue, when i did a fresh install. Everything was working fine before but now i got the same error as mentioned in the above. project call is happening on port ip:8000 and projects.js call is happening on localhost:8080. |
@BurakaKrishna |
|
That docker-compose file doesn't look like the one in the repo. Any particular reason why you're not using or adapting the docker-compose file in the repo? |
|
I have used the docker image to deploy and did a fresh install, couldn't solve using doccano compose. |
|
Is the intention to keep on using Webpack dev server in production? 10 minutes of debugging this led me to believe the root cause of this is that the bundle needs to be referred with a full url, as the webpack server runs on another port. Best way to fix this would probably be to build the assets before the web server starts / release with assets already build. First aid for this specific issue could also be to assign a new Django route that proxies requests to the webpack dev server. After this the web browser wouldn't have to specifically know where the dev server is located and you could refer javascript assets with relative paths. |
|
@rikukissa As mentioned in the readme, the docker-compose file included in this repository is intended for development purposes. For production usage, please use the Docker image which does not use webpack at runtime. |
|
Hello, And into docker-compose setup WEBPACK_HOST: "10.211.55.161" as external address. |
|
I am facing the same issue. Is there a workaround for this? |
|
I have not yet seen a way to reproduce this unfortunately. If someone can share the exact steps that lead to the error in a way that I can reproduce it, I can look into investigating this more. |
|
Yeah typically this problem arises during upgrades on existing installations. Its so easy to miss building the server pages with the npm build commands. |
|
We're currently caching node_modules and the python virtualenv in the docker-compose file to speed up the development loop. This means that if any of the project's dependencies changed, a clean stop via The docker-compose file is intended as a development tool only, not as a production deployment mechanism. For production deployment, I'd recommend to use the official Docker build. |
|
The topic is drifted to another issue. Please raise a new issue if you want to improve deployment. |
If you open a GitHub issue, here is our policy:
System information
Describe the problem
as the READEME describe, I deployed the doccano use the docker-compose method,after the system started,:
and I cannt see anything in this page like this
and I open the developer console, a js file cannot find by the system, like this
also I cannot find this js file in the app/server folder, but in the app/server/static
Source code / logs
docker node logs:
python logs:
The text was updated successfully, but these errors were encountered: