Open Wylbur opened 3 years ago
I'm not sure about this... If it turns out to be fairly simple to implement, then maybe. But if it's too complex, then I think it's better left for Drush.
I think leaving this for Drush is not really an option.
If we could get https://github.com/backdrop-contrib/bee/issues/190 done, then we could create an add-on module called bees
or swarm
or hive
that expands it to include more of the commands from drush.
This was raised in today's discussion at Backdrop LIVE. Names were recommended by @keiserjb (bees
), @TheMetMan (swarm
), and @indigoxela (hive
).
Module's adding their own commands is already possible. So have at it!
We had a useful discussion at Backdrop Live on what, if it is to be included, site alias functionality would look like. For reference, here are the notes.
~/.bee/aliases
OR ~/path/to/localsite/bee/aliases
) though if config fully defines the path, then shouldn't be an issue.sitename.json
or sitename.php
). PHP may be easier if using brush
as a template.bee
is installed as part of the app tooling.bee
should recognise this as a global argument that can operate any commands~/.ssh/config
) and use the hostname rather than having to re-specify the SSH details. Don't know whether drush
does this or not?brush
code may be easier as a pattern as is much shorter.@jenlampton @oadaeh @hosef (@Wylbur - I know you couldn't make it, but I know you have an interest in this) - let me know if I've summarised this correctly or not.
@BWPanda - FYI
Site Aliases is a significant feature of Drush and Brush. It allows you to execute commands on a remote backdrop installation. To also allows you to use rsync to move files between installations.