You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
The text was updated successfully, but these errors were encountered:
@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
The text was updated successfully, but these errors were encountered: