| Age | Commit message (Collapse) | Author |
|---|
|
This is a security measure better fulfilled with a firewall.
The problem is when it is restricted to the `zeth` interface it cannot
be reliably started while the firmware is not running, since the
interface is not up.
But when the MQTT broker is not available it is hard to start the
firmware in the current state because it requires a running MQTT broker.
This is a chicken-egg-problem solved with this commit.
|
|
This avoids warnings and sets the focus to the IP version which is the
current focus.
|
|
This folder should explain how to setup the network environment for the
firmware simulation.
|
|
Everything else is implicitly build by default since it should
contribute to the tar archive.
|
|
Using the installation step to copy selected artifacts into one folder
was anyway a hack.
This commit shows that the complexity can be reduced by adding copy
targets. The `build/artifacts` folder contains the selected artifacts,
they are always up to date, the user does not have to call the install
step separately and the target definitions do not require
install-related keyword arguments.
|
|
A static site generator is currently not really required. A static
index.html is currently sufficient.
|
|
This adds a build for the native_sim board of the application firmware
to the default Meson build.
The resulting Linux binary is also added to the webpage.
|
