If you deploy it once with the startup command (set the framework to standalone) and the bound service, save the settings and then deploy again it should recreate and bind the service if it doesn't exist.
As for the startup command, if it isn't in the manifest, just add the key 'command', for example;
applications:
- name: sidekiq-dh-worker
framework: standalone
runtime: ruby19
memory: 256M
instances: 1
url: none
path: .
command: bundle exec sidekiq
services:
sidekiq-dh-redis:
vendor: redis
version: "2.6"
tier: free
sidekiq-dh-mysql:
vendor: mysql
version: "5.1"
tier: free
This is a manifest.yml for a Ruby sidekiq worker, note the 'command' key and also the two named services.
--
Dan Higham
CloudFoundry Support
@danhigham