- No c compiler found ec2 instance nvm install node how to#
- No c compiler found ec2 instance nvm install node full#
- No c compiler found ec2 instance nvm install node code#
* creating myapp/lib/myapp_web/templates/layout/
* creating myapp/lib/myapp_web/controllers/page_controller.ex * creating myapp/priv/gettext/en/LC_MESSAGES/errors.po * creating myapp/lib/myapp_web/gettext.ex * creating myapp/test/myapp_web/views/error_view_test.exs * creating myapp/test/support/conn_case.ex * creating myapp/test/support/channel_case.ex
* creating myapp/lib/myapp_web/endpoint.ex
* creating myapp/lib/myapp_web/views/error_view.ex * creating myapp/lib/myapp_web/views/error_helpers.ex * creating myapp/lib/myapp_web/channels/user_socket.ex * creating myapp/lib/myapp/application.ex
No c compiler found ec2 instance nvm install node code#
(To get spoilers for this post, follow along with the complete code here). So if you are ready to harness the awesome power of the Phoenix Framework as your server and ReasonReact as your client, please read on. To help you, humble reader, from also not finding any results on using these two technologies together, I have put together this post to show you how I managed to get the two working together quite nicely. Unfortunately, even though these two technologies (Phoenix and ReasonReact) are awesome, they are still fairly new and haven’t yet gotten an invitation to the “popular web technologies” club, so I was left to wiring up the two technologies together myself.
No c compiler found ec2 instance nvm install node how to#
Now that I chose the winning team of technologies to use, my next step was to “google” all of the technologies together to see if someone has already written a blog post on how to wire them all up together. Also, since ReasonML is also developed by Facebook developers, the project is very closely tied with React. Out of the box, ReasonML provides static typing, immutability, and other useful functional programming features ( Variants are pretty great!). ReasonML is basically a re-skinned syntax of OCaml to make it look more like JavaScript and less like a scary functional programming language. The choice was easy.įor the client, I wanted to use static typing, immutability, and composable components, but I didn’t want the complexities of handling a different dependency for each of these criteria. This means that I get all of the niceties of Rails with all the power of the Erlang RunTime System and OTP (fast, scalable, reliable). This led me to the Phoenix Framework, which is basically Rails, but instead of running on Ruby, it runs on Elixir in the Erlang RunTime System. Based on an interview with Jesper Louis Anderson, I decided to consider functional programming languages as a starting point since they are the most “agile” types of languages.įor the backend web server, I wanted to use a functional programming language, but I wasn’t ready to give up all of the niceties of Rails (convention over configuration, generators, ActiveRecord). Like many other developers, I have seen the technical debt that is inherent to some of the potential choices, so I decided to take a step back and objectively evaluate which technologies would work best for this specific project. Especially during development when package.json changes nearly all the time.Īs I started designing a new web application project, I had the wonderful opportunity to choose which technologies to use to power it. Waiting for over 6 minutes to build the docker container whenever anything changes in the package.json file is unacceptable. On my slower machines, this process takes nearly half an hour. On my fast machine, this process takes over 6 minutes. This typically isn’t a problem for smaller npm dependencies that take less than a few seconds to install, but bs-platform installs and compiles an OCaml compiler from scratch.
No c compiler found ec2 instance nvm install node full#
However, when installing npm dependencies in a docker container, any change to the package.json file would trigger a full install of all of the npm packages. This method works great on a development machine where npm dependencies are cached and only need to be installed again if the package is deleted from the local node_modules directory. The simplest option to include bs-platform in the project is to add it to the dependencies field of package.json and allow NPM (or yarn) to install it locally into the project's node_modules directory.
0 kommentar(er)
