Can I use more than one provision or there have another way to run commands each by each？ about dip

[bibendi]

Hi!
Dip cannot do that.
I think it's better to define a separate yarn_server service in a docker-compose.yml file and make rails service depends_on: them.

[Dearest]

@bibendi Can I make a pull request to implement this feature?
maybe I will add a keyword like flow。 it will have the same level as interaction or provision 。
flow is very similar to provision, but it can define multiple。
maybe it look like this

interaction:
  rails:
    description: Run Rails commands
    service: rails
    command: bundle exec rails
    subcommands:
      s:
        description: Run Rails server 
        service: rails
        compose:
          run_options: [service-ports, use-aliases]

  yarn:
    description: Run Yarn commands
    service: rails
    command: yarn
    compose_run_options: [no-deps]

flow:
  start:
    - rails s
    - yarn start

I can use dip flow start to run rails s and yarn start one by one

[bibendi]

Sorry, but I think that doesn't make sense. The dip uses Process.exec to run a command. So, basically, you cannot run more than one command at a time. Another reason is how the secondary command should run? In a background? How should we be able to stop or interact with them?

Well, again, if you just need to autostart a dependent command in the background, please use Docker Compose services. The dip is just a wrapper around it. I don't want to duplicate its built-in functionality.

[Dearest]

Thank you for your reply, I see what you mean, this issiue can be closed now