Hi everyone, I just came back to Prefect after a l...
# ask-community
k
Hi everyone, I just came back to Prefect after a long break, and there seems to be A LOT of changes. I am setting up Prefect to run in my home server with Docker, so I need a server, and a couple of workers. I can start the server in a container, but because a worker is in another container, it cannot find the Prefect server instance. When I use an agent instead, I got this to work, but there is a warning that agent is deprecated. A worker does not have any setting to change the API URL. So, I have a few questions on coming back: 1. Is the new worker supposed to work within the same environment (container) with the server? There is no option to point it to the server url, and the error is connection failure. 2. If worker is the future, and it does not work over remote server, then what is the approach with a Docker compose deployment? 3. Since this is a local deployment, I don't need Postgres, and would rather use SQLite. However, I cannot find the database file anywhere to volume mount it for backup. Could you point me to the database location for SQLite?
👀 1
For reference, here is my compose file
Copy code
services:
  server:
    image: prefecthq/prefect:2-latest
    command: ["prefect", "server", "start"]
    ports:
      - 4200:4200
    environment:
      - PREFECT_SERVER_API_HOST=0.0.0.0
  agent:
    image: prefecthq/prefect:2-latest
    command: ["prefect", "agent", "start", "--pool", "Demo"]
    environment:
      - PREFECT_API_URL=<http://server:4200/api>
    depends_on:
      - server