On 02Feb2024 11:29, bruce <badouglas@xxxxxxxxx> wrote:
But setting up ssh is no issue. My issue, I'm wondering how to "run" a
cmd on srvr2 via ssh when I'm on srvr1.
How is:
ssh srvr2 the-command...
not enough? I feel that I'm missing some larger context here.
And a larger issue, is this
even the "right" way to handle testing "stuff" within Github?
Shrug. Why not? If you want to test "run some command on srvr2" and
you're orchestrating things from srvr1, the above ssh seems fine to me.
Obviously it glosses over the target user on srvr2 and the ssh key
setup, but you say you've got that side of things sorted.
Example: I've got a little script to twiddle our firewall's routing as
needed. It looks like this:
#!/bin/sh
set -ue
if [ $# = 0 ]
then ssh fw cat /etc/isp-state
else set-x ssh fw doas -u root isp.sh "$@"
fi
It just sshes to the firewall and runs the required command.
Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
