sebakerckhof
commented
9 years ago Well, I guess this could be used to that purpose. Although I can't spend much time towards that right now, we can discuss the subject and look at what the best approach would be.
Note that this project is only the package server, but not the build server. So the build server will have to support builds for ARM (Do the meteor build servers support that?) If not you will have to set up your own build server.
Anyway what you'd probably have to do is: 1) When importing packages from upstream, make sure they do not get published to the client if they do not have an ARM build. You could do so by setting a flag when importing them (here: https://github.com/sebakerckhof/stratosphere/blob/master/packages/stratosphere_synchronizer/server/synchronizer.js#L131 ) and not publishing those packages to the clients (here: https://github.com/sebakerckhof/stratosphere/blob/master/packages/stratosphere_core/server/rpc/meteortool/syncNewPackageData.js#L113 )
2) Schedule builds for those packages and after they are build, remove the flag so they get published to the clients.
TomFreudenberg
Hi, I am maintaining currently the ARM fork of meteor at https://github.com/4commerce-technologies-AG/meteor.
There are often packages on atmosphere that are not ready deployed for ARM architecture. In this cases you have to download the package source (mostly from github) and append it locally to your meteor project.
I would like to spend an ARM stratosphere server to provide all packages also on ARM devices.
Could / would you like to spend some time helping on this?
In any way, great to see this project! Tom