unmade / shelf-showcase

An example of Shelf Cloud ready-to-run docker-compose
https://getshelf.cloud
GNU Affero General Public License v3.0
291 stars 7 forks source link

APP_SECRET_KEY error #13

Closed viriatusX closed 1 year ago

viriatusX commented 1 year ago

Hi, I am trying to get the docker up, and everything is correct, but the Worker is NOT. It shows this error. I have specified a value in the .env file.

Captura de pantalla 2023-07-07 a las 11 54 35

Thanks!

unmade commented 1 year ago

Hey,

Can you please provide a bit more details, like what command you ran, whether you made changes to .shelf-back.env, docker-compose.yml, etc..

viriatusX commented 1 year ago

Hey,

Can you please provide a bit more details, like what command you ran, whether you made changes to .shelf-back.env, docker-compose.yml, etc..

Hi! I am running in Unraid My docker-compose.yml

services: shelf-back: image: fdooch/shelf-back:0.1.0-alpha.12 env_file:

volumes: dbvolume: {}

My .shelf-back.env

Captura de pantalla 2023-07-10 a las 19 32 12

And all containers are lifted correctly but the shelf-worker show the error list above.

unmade commented 1 year ago

Oh, it seems shelf-worker config missing the env_file attribute. All you need to do is to add it (like in shelf-back):

    env_file:
      - ./.shelf-back.env

Please, let me know if that solves the issue!

viriatusX commented 1 year ago

Oh, it seems shelf-worker config missing the env_file attribute. All you need to do is to add it (like in shelf-back):

    env_file:
      - ./.shelf-back.env

Please, let me know if that solves the issue!

Thanks for your quickly response. Now, the application starts but I seems not "connect" correctly with DB. I can't access neither create new account.

The logs shows:

Captura de pantalla 2023-07-10 a las 20 55 55 Captura de pantalla 2023-07-10 a las 20 56 09

CleanShot 2023-07-10 at 21 01 23

unmade commented 1 year ago

To be honest I don't know what's wrong with EdgeDB container. I know some of the issue can be related to the architecture. Are you running on x86_64 or arm64 (raspberry pi)? If you're running on arm64, then most likely that is the case.

Alternatively, you can try to remove containers and related volumes and create everything from scratch. Sorry for such inconvenience

viriatusX commented 1 year ago

To be honest I don't know what's wrong with EdgeDB container. I know some of the issue can be related to the architecture. Are you running on x86_64 or arm64 (raspberry pi)? If you're running on arm64, then most likely that is the case.

Alternatively, you can try to remove containers and related volumes and create everything from scratch. Sorry for such inconvenience

Thanks for your reply. I'm running on x86 (AMD64) platform, not ARM. When I try to login it, the Chrome shows this error 405: It seems that it is not edgedb's error. In CORS I have specified "*" and in API_BASE_URL=http://192.168.1.165:6778 (6778 in my case since port 8000 is busy).

Captura de pantalla 2023-07-11 a las 19 41 56
unmade commented 1 year ago

Sorry that it took me a bit long to reply.

Based on docker-compose you've provided, I think the API_BASE_URL should be set to http://192.168.1.165:6777. The port 6778 points to the frontend server, hence the 405 error code. But the 6777 actually points to the backend

viriatusX commented 1 year ago

Solved!!! Thanks!!!!!