As the server moved we ran into the issue that the configuration where to upload the binaries is in two places that have to be kept in sync: on of them is the action secret DEPLOY_SERVER which is used to retrieve the SSH key from the server. The other is the configuration in rclone.conf which specifies where Sandworm will upload the artifacts. This is obviously suboptimal, as that means that the same configuration change has to be done in two different places, using two different methods (changing secrets for one, updating the repo contents for the other).
Generally I think it would be better if the rclone.conf could be replaced altogether (e.g. by passing the values directly when invoking), since it currently hardcodes the configuration for Tarides but is not interesting to a general open source audience.
As the server moved we ran into the issue that the configuration where to upload the binaries is in two places that have to be kept in sync: on of them is the action secret
DEPLOY_SERVERwhich is used to retrieve the SSH key from the server. The other is the configuration inrclone.confwhich specifies where Sandworm will upload the artifacts. This is obviously suboptimal, as that means that the same configuration change has to be done in two different places, using two different methods (changing secrets for one, updating the repo contents for the other).Generally I think it would be better if the
rclone.confcould be replaced altogether (e.g. by passing the values directly when invoking), since it currently hardcodes the configuration for Tarides but is not interesting to a general open source audience.