One-click Auto Upgrade has returned in 1.3!

Those of you who have been using pfSense for several years will remember pre-1.0, there was an auto-upgrade page that would upgrade you to the latest available release with one click. It was later broken by some changes and removed prior to the 1.0 release, but has been fixed and resurrected. It’s now working in 1.3.

By default, it checks for a newer stable release than the one you are using, and if one is available, you can click a button and it will download and install the update. It also allows changing the URL to pull snapshots, or you can enter your own URL if you maintain a custom version. The current manual upgrade remains available as well.

1.3 is under such active development that it isn’t really suitable for any non-developers at this time. We gave the URL for the snapshots to attendees at our BSDCan tutorial, but won’t be releasing it to everyone just yet.

Share this Post:

4 Responses to “One-click Auto Upgrade has returned in 1.3!”

  1. Martin Says:

    Sounds really great. Will this also work on the embedded version? I know that upgrading embedded platforms have been a bit of an issue in earlier versions. Lastly, when do you expect to have a publicly available beta and what timeframe is the final release targeted for? I’m currently using pfSense in my data center, and from everything I read about 1.3, it sounds like I really want to upgrade from 1.2.

    Thanks for the great work!

  2. Chris Buechler Says:

    Embedded is going to take a completely different path in 1.3, we’re currently working on the specifics. It will use its own, different upgrade system and it will eliminate all the past issues (and provide other benefits).

    Embedded will have one click upgrade support as well, though it will be a completely different upgrade mechanism (same from the end user’s perspective though).

  3. Bill McGonigle Says:

    This is great news! Kudos to all. Upgrading can be one of the bigger pains, currently.

    I hope that it will be possible to converge the upgrade systems, so there’s only one upgrades code-base to maintain at some point in the future, to consolidate bug fix and features work. I assume there are currently two systems being considered and each has features the others lack? From one perspective, embedded can be viewed as a specific ‘profile’ of a full install. That’s theoretical, of course, not necessarily based in the ‘reality on the ground’.

    I look forward to seeing what you guys come up with.

  4. Chris Buechler Says:

    The upgrade code will be different in the back end between full and embedded, but the same from the user’s perspective. This is a requirement for the direction we’re going with 1.3 embedded. Full upgrades are reliable now, they aren’t changing a lot. It’s the same code base, just different functionality depending on your platform.

    The build scripts for full and embedded will also differ, but they always have so that isn’t a change. That’s all an automated process anyway.

    Though the images will remain separate out of necessity, all platforms have always been based off a single code base and that isn’t going to change. It’s just built into releases differently depending on platform.

Please don’t post technical questions or off-topic comments. It is far more likely that your questions and concerns will be addressed effectively through one of our support channels.

Leave a Reply