Skip to content

Commit c4b80b9

Browse files
authored
luci-app-attendedsysupgrade: Rewrite README.md
Signed-off-by: Bruxism <38876789+Bruxism@users.noreply.github.com>
1 parent e8f5750 commit c4b80b9

1 file changed

Lines changed: 21 additions & 7 deletions

File tree

  • applications/luci-app-attendedsysupgrade
Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,29 @@
11
# luci-app-attendedsysupgrade
22

3-
This app adds OpenWrt firmware upgrade and update as well as package update
4-
functionality via its web interface.
3+
`luci-app-attendedsysupgrade` is a plugin for the OpenWrt LuCI web interface
4+
that facilitates updates and upgrades for both firmware and software packages.
55

6-
When activated, this app sends a build request that includes system CPU
7-
architecture/target and currently installed packages to an
8-
*Attended SysUpgrade server* (ASU) which, if available, will then respond
9-
with an install-ready custom image that includes firmware and package updates.
6+
Upon installation, it adds a web page to the OpenWrt LuCI web interface
7+
available at `System > Attended Sysupgrade` which provides controls
8+
and configurations for when and where to send build requests.
9+
10+
Build requests include information about the request system's
11+
CPU architecture/target and its currently installed packages. These are sent
12+
to an _**A**ttended **S**ys**U**pgrade_ server (ASU) which,
13+
if available, will then respond with an install-ready custom firmware image that
14+
includes the latest requested firmware and package updates.
15+
16+
_An option in the configuration page called "Advanced Mode" activates a prompt
17+
to customize what to include upon a manually-activated build request._
18+
19+
Following a successful build request, the user is prompted with a link to
20+
download a copy of the custom firmware image to their computer and the option to
21+
immediately install the custom firmware image either with or without keeping
22+
currently set system configurations.
1023

1124
The process per image takes between 30 seconds and 5 minutes, and may be down
12-
for a few days during the build rollouts and peak use following major upgrades.
25+
for a few days during the build rollouts and peak usage that follows major
26+
OpenWrt upgrades.
1327

1428
More information on the backend server and how to host one are available on the
1529
projects page: https://github.com/openwrt/asu

0 commit comments

Comments
 (0)