Ability to create full URL scheme from hostname in render YAML
It appears that the render YAML specification does not allow for specifying a URL scheme on any environment variables with hostname. The example below uses the hostport property to add a REDIS_URL environment variable and sets it to the hostname. However the hostname will only be “example-redis:1234” and will not have a URL schema prefix such as “redis://example-redis:1234” this causes applications assuming a full URL prefix to not work.
Obviously this can be fixed in the application itself by adding the prefix to the ENV variables but services such as Heroku and Rails conform to general standard that the ENV variable will have a full URL schema. So migrating like I am from Heroku to Render requires application development that is specific to the render platform.
Environment Variables in dashboard vs render YAML
This also creates another problem when trying to manually change the env variable to add the prefix in the render dashboard. This works, however when a new deployment is triggered and the render YAML is synced the prefixed version is overwritten by the render YAML file and causes the service to obviously fail.
Would love to see how you guys could handle ensuring environment variables could have prefixes or full URL schemes in the YAML specification. It would be great to have some warning or preference when we edit an environment variable that is actually specified in the YAML file the given service is synced to!
- type: worker name: british_community_sidekiq env: ruby region: frankfurt numInstances: 1 buildCommand: "bundle install" startCommand: "bundle exec sidekiq -c 3 -q default -q mailers" envVars: - key: REDIS_URL fromService: name: british-community-redis-queue type: pserv property: hostport