I believe it still uses EAS for certificates by default. You can use "prebuild" to get the ios / android directories. Alternatively start a React Native app and install their modules separately. These options still work well but require a lot more setup.
Also see Fleet (https://fleetdm.com/) for an open source self-hosted solution. I'm currently using this at a small company to query / enforce policies across a bunch of Windows laptops.
Very much agree with you on this. I picked up a live Meteor app that felt very much like it had been built as a prototype that had been built upon into a production app. It was a mess, it had clearly evolved over time and over multiple Meteor releases, there was no obvious structure at all - just felt like a bunch of files that were all loaded into some soup that became the app.
I don't think Meteor ever had decent docs on going from the prototype stage to a fully fledged application and how you'd evolve the structure over the time.
I could name a lot of problems I've had with Meteor, and I definitely agree with having a proper evaluation of tech before using it - knowing the limits of the stack you choose and if it's going to lock you in in the long term.
It's felt like a framework that hasn't been given time needed recently to keep it up to date, improving docs etc as MDG have shifted their focus on Apollo.
Hiring/skillset of the existing team, existing legacy codebases that need to be worked on, simplicity... things aren't as black and white of you must use this technology over another, there are a lot of reasons involved
Hey, I didn't write the article but work with John... we deploy through a CI/CD pipeline using Concourse CI. Which builds the docker containers and eventually deploys them onto a Rancher cluster
