Hello! Sometime recently, Push To Deploy stopped working. I no longer see Push To Deploy enabled for apps, and I can no longer select any repos in the Galaxy UI. GitHub shows the connection/authorization is still active.
Did something change with Push To Deploy that could have broken?
In the meantime, I could not get meteor deploy to work, it would keep having an error that the app size is too big to upload. However the app size was fine when using Push To Deploy.
I also tried to meteor deploy a modified bundle, but that did not work, seems like meteor unpacks it, and tries to do something with dev dependencies that I don’t need and then fails.
And there’s no documentation anywhere that indicates how to deploy without web.browser.legacy (which no one needs these days).
Overall, I’m having a hard time trying to manually deploy (in case something like Push to Deploy is not working), and there are so few docs that average AIs cannot answer questions properly in this area.
I haven’t tried running an instance of Copilot on GitHub, that might have better results if it inspects source code, but still I feel the docs are too lacking here.
Reported to the Galaxy platform team the issue with Push To Deploy.
The OSS Meteor-related question is answered in the other post: How to prevent web.browser.legacy from being built with meteor build?. The issue is likely tied to try that config in an older Meteor versions, before the modern .meteor/platforms config existed. That was introduced in Meteor 3.3 (docs)
Regarding the Push to Deploy settings being lost, this issue is affecting some of our Galaxy users. We have a fix in the final staging of testing and should be available very soon. It’s a big update for Galaxy that brings new features and bug fixing.