We’re using https://github.com/marketplace/actions/setup-meteor-js-environment to use Meteor in Github Actions. What’s the best way to deploy to Galaxy via GH Actions? I’ve been trying but haven’'t found a good way to get Galaxy deploy to play nice with Github’s secrets. Does anyone have any tips on what I might be missing? ie how are you accessing settings as well as deploy tokens when running via an action?
In case anyone finds this later. Here was my solution.
I encrypted the settings.json and deployToken.json I created. Then I wrote a script to decrypt them before using them to deploy.
I did so by adapting this post here:
https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#limits-for-secrets
IMO this would make a great blog post to show that Meteor is up to date with the latest stuff.
1 Like
Here’s a quick how-to.
https://www.scotttolinski.com/posts/how-to-deploy-to-meteor-galaxy-with-github-actions/
6 Likes