Skip to content
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

dev routing #475

Open
fils opened this issue Nov 3, 2024 · 0 comments
Open

dev routing #475

fils opened this issue Nov 3, 2024 · 0 comments

Comments

@fils
Copy link
Collaborator

fils commented Nov 3, 2024

@arnounesco I logged into the dev server this weekend and tried a few things but so far I'm still having some routing issues getting to the scheduler.

I will keep playing a bit, but need to resolve out how you are doing the routing wit nginx for the containers so I can modify my compose file accordingly.

The indexer is working from a code logic level. Indexing all sites now well.

It's really just down to the networking.

I see your default network and I am looking at the api service as a model.

I'm going to try something like

    environment:
      - VIRTUAL_HOST=workflow.${HOST}
      - VIRTUAL_PROTO=http
      - LETSENCRYPT_HOST=workflow.${HOST}
      - LETSENCRYPT_EMAIL=  *********
    ```

but let me know if you have other suggestions.

VIRTUAL_PROTO is the protocol for the service, so http in my case as well for dagster/scheduler running on http://localhost:3000?

Also, is nginx fronting for the solr port?   I was thinking I would do something more like I think I see with the solr networking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant