This is one of my areas of expertise. > . Whether its getting haskell running at all, getting the right version of > glibc to execute the elm binaries or hacking the elm-stuff folder to fake > private repos, I'm hitting walls at every turn. To make matters worse, I > don't have a lot of control over the build systems. They run a pretty old > version of something like Red Hat.
If this is a problem, consider running a virtualization layer or something like Docker. Setting Elm to compile inside a docker instance is pretty trivial - even newcomers to docker should be able to get it set up in less than a couple of hours. Another trick is to have a seperate deploy server from the build servers. We use instances with Jenkins on to do exactly this - it runs with node 6.x, so we can use webpack. Webpack is run, then it is sent to our actual servers afterwards. It's hard to give exact advice here without knowing more about your infrastructure, but I would generally recommend having your build servers running more modern stuff than your actual production servers. Especially when dealing with the wacky world of JS build tools. > If anyone is using Elm in production can you talk a bit about your automated > deployment and testing process around it? If you have any more questions, feel free to ping me on Slack On Tue, Dec 27, 2016 at 7:27 AM, Anthony Naddeo <[email protected]> wrote: > I've been beating my head against a wall trying to integrate Elm into my > companies build system. Whether its getting haskell running at all, getting > the right version of glibc to execute the elm binaries or hacking the > elm-stuff folder to fake private repos, I'm hitting walls at every turn. To > make matters worse, I don't have a lot of control over the build systems. > They run a pretty old version of something like Red Hat. > > If anyone is using Elm in production can you talk a bit about your automated > deployment and testing process around it? I have a lot of restrictions that > I'm trying to work around at the moment. > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
