search

nickthecook / ops

The operations team for your project.
GNU General Public License v3.0
50 stars 1 forks source link

working_dir for actions #54

Closed nickthecook closed 4 years ago

nickthecook commented 4 years ago 
actions:
  start: ops start
  working_dir: app
nickthecook commented 4 years ago

This doesn't really make sense for calling ops commands from another dir. That's more of a use-case for forwards (added in 0.19.0).

This is more useful with a command that doesn't run ops, like if you have an action in your project's ops.yml that needs to work in another directory. In that case, working_dir saves you a cd ../some_dir && in your command. That's not a big deal, and there's an easy workaround.

I feel like if this feature were in ops, most people would just use cd && instead, since it's easy, intuitive, and readable to anyone.

The reverse of this feature is actually needed, where you can run an action in your current directory that is defined in an ops.yml that is not in your current directory.