Ideally, we will run schedulers for multiple 'communities' in the same dagster, but for now, we need to run them as separate stacks.
This means that is a community uses a resource of the same name (or a dev instance runs on same docker swarm), that they need to not cause a conflict (usually 409 error) if they end up running at same time.
So, treafik labels, and service names generated need to not conflict.
Make sure treafik labels have a project (i think this is done)
allow for a hostname to be provided right now sched.{host}
in generated code template be sure service name, and (future) headless container for each run have non-conflicting names (aka project).
Ideally, we will run schedulers for multiple 'communities' in the same dagster, but for now, we need to run them as separate stacks.
This means that is a community uses a resource of the same name (or a dev instance runs on same docker swarm), that they need to not cause a conflict (usually 409 error) if they end up running at same time.
So, treafik labels, and service names generated need to not conflict.
Probably more