PHOENIX OS HDMI CODE

Our configuration might look like this (as of Phoenix 1.6.2): # my_app_/my_app_firmware/config/target.exs config :my_app_ui, MyAppUiWeb.Endpoint, url :, http :, cache_static_manifest : 'priv/static/cache_manifest.json', secret_key_base : 'HEY05EB1dFVSu6KykKHuS4rQPQzSHv4F7mGVB/gnDLrIu75wE/ytBXy2Ta元A6RA', live_view :, check_origin : false, render_errors :, pubsub_server : Ui.PubSub, # Start the server since we're running in a release instead of through `mix` server : true, # Nerves root filesystem is read-only, so disable the code reloader code_reloader : false # Use Jason for JSON parsing in Phoenix config :phoenix, :json_library, Jason Import it from there or duplicate the required configuration. My_app/my_app_ui configuration won't be applied automatically, so we should either We're using a poncho project structure, we'll need to keep in mind that the Using appropriate settings for deployment on an embedded device. Nerves-based my_app/my_app_firmware project, we need to configure our Phoenix.Endpoint In order to deploy the my_app/my_app_ui Phoenix-based project along with the Refer to the Connecting to Nerves Target page.

Project as a dependency, because we want to use the my_app_firmware projectĪs a deployment wrapper around the my_app_ui project. Now, we add the Phoenix-based my_app_ui project to the my_app_firmware Mix phx.new my_app_ui -no-ecto -no-mailer # Create a Phoenix 1.6 UI project called 'my_app_ui' # Create a Nerves firmware project called 'my_app_firmware' Side-by-side with path dependencies between them, in the same source code repository.įirst, we generate the two new Mix projects in a containing directory: # Create a container directory called 'my_app' Using the poncho project structure, we simply use separate Mix projects, For the reasoning behind this, please see the originalīlog post describing poncho projects. There are two commonly used project structures for Nerves-based devices that usesĪlthough Nerves supports both, the preferred project structure is what we call Hello Phoenix is an example of structuring a project as described here. Interfaces intended to be accessed from a computer or mobile device.

For example, aĭevice with no display might provide administration and configuration That need to serve content over HTTP directly from the device. The Phoenix web framework makes an excellent companion to Nerves-based devices

Phoenix os hdmi