What is the best way to maintain a custom nerves firmware

With the discovery of the critical SSH vulnerability in Erlang, followed by the superb Nerves team’s @fhunleth bringing us updated nerves_system_br

I am wondering what the best way is to maintain a custom firmware image.

Do you clone the new version and make all the changes again?
Or ?

2 Likes

It will depend on how many and how complex your changes are.

If you have diverged you can monitor related systems for changes and apply your own adaptations of those. That’s the in-depth lifestyle of someone operating a highly custom Nerves system.

Most systems are probably close to what they forked from. In many cases I’ve updated them by just rebasing my changes on top of the official system. Rebasing rewriting history is of course inconvenient and you may want to take some other approach if you prefer but it gets less automagical.

If you have just a few changes and you’ve fallen far behind it can make sense to pick up the new system and just apply your fixes “by hand” or via git in whatever measures make sense.

So that’s an “it depends” style answer. Whatever you think you do consistently over time I suppose :slight_smile: