Describe the bug
When attempting to configure a sync to run on a schedule, the multiwoven server throws the following error in the logs

multiwoven-server-1   | Failed to schedule sync with Temporal. Error: 14:errors resolving :: [field:hostname lookup error:host must not be empty in name: :]. debug_error_string:{UNKNOWN:Error received from peer  {grpc_message:"errorsresolving :: [field:hostname lookup error:host must not be empty in name: :]", grpc_status:14, created_time:"2025-07-17T11:21:49.756197901+00:00"}}

To Reproduce

1. Set up multiwoven on an EC2 instance according to the documentation
2. Pull the latest docker image and build
3. Set up a source, destination and sync
4. Attempt to schedule a sync

Expected behavior
The sync should be scheduled and run on the specified schedule.

Screenshots

Note that this appears to be caused by the fact that temporal.rb is not initialised. The reason I say this is that running the command sudo docker-compose exec multiwoven-server sh -c 'env | grep TEMPORAL_' yields the following output:

TEMPORAL_ROOT_CERT=/certs/temporal.pem
TEMPORAL_UI_VERSION=2.21.0
TEMPORAL_ACTIVITY_THREAD_POOL_SIZE=20
TEMPORAL_POSTGRES_DEFAULT_PORT=5432
TEMPORAL_POSTGRES_PASSWORD=temporal
TEMPORAL_NAMESPACE=multiwoven-dev
TEMPORAL_POSTGRESQL_VERSION=13
TEMPORAL_POSTGRES_USER=temporal
TEMPORAL_CLIENT_KEY=/certs/temporal.key
TEMPORAL_WORKFLOW_THREAD_POOL_SIZE=10
TEMPORAL_CLIENT_CHAIN=/certs/temporal.chain.pem
TEMPORAL_VERSION=1.22.4
TEMPORAL_HOST=temporal
TEMPORAL_ADDRESS=temporal:7233
TEMPORAL_TASK_QUEUE=sync-dev
TEMPORAL_PORT=7233

which suggests that the env file is being successfully loaded. Hence I believe it to be an issue with the initialisation of the temporal service.

Desktop (please complete the following information):

• Ubuntu

Additional context

I think adding TemporalService.setup to the bottom of server/config/initializers/temporal.rb may resolve the issue.