-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Not found issue #35
Comments
Could you share your docker-compose file and the exactly url you're trying to access? |
It's the docker compose example given but the port changed to 8282.
Http://docker:8282
…On Thu, Apr 13, 2023, 6:23 AM Matheus Baldissara ***@***.***> wrote:
Could you share your docker-compose file and the exactly url you're trying
to access?
—
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD3PBMOLR4IX2ESWWC5B5ZDXA7OZLANCNFSM6AAAAAAW4OTV5M>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The docker-composer example has the env variable BASE_PATH=/tasks, so it's probably running at http://docker:8282/tasks |
Oh shoot I should have paid more attention. That was it, thanks.
…On Thu, Apr 13, 2023, 6:49 AM Matheus Baldissara ***@***.***> wrote:
The docker-composer example has the env variable BASE_PATH=/tasks, so it's
probably running at http://docker:8282/tasks
—
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD3PBMJHMPUNCHAKXVLS77LXA7R3BANCNFSM6AAAAAAW4OTV5M>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Great! I'm glad it worked. I'm closing this thread now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After starting the container via docker compose and accessing it via url all I get is a "not found" message on the site. Logs are empty and dont indicate what the issue could be.
The text was updated successfully, but these errors were encountered: