I just migrated my packages from reactioncommerce 1.3 to the new JS-Standard for 1.4. Everything worked fine on my test server running a local reaction server with “reaction” command and placing the package into “~/reaction/imports/plugins/custom”. Now I try to find a solution to deploy it to our production server.
1st Idea was to put the package into the standard docker image of reactioncommerce but we couldn’t find a solution where to put it to make it load on an already compile reaction. Is that possible?
2nd Idea was running “meteor build” on the testserver creating a tar.gz and then executing a buildprocess to make it work on a production server. Which wasn’t running smooth because of the fibers package.
3rd Option was to setup the docker build which takes a very long time to debug the workflow but we got it finally to work.
Is there a possibility to speed up the build process for production and take advantage of developing the package separately or does it allway has to go through this complex build process?
I would appreciate if you could share some insights into the deployment chain and methods you are using to develop and operate your reactioncommerce solution.