I’ve updated the Debian / Ubuntu repository, please see the updated instructions in the documentation:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1CE2AFD36DBCCA00
sudo echo "deb https://artifacts.loraserver.io/packages/0.x/deb testing main" | sudo tee /etc/apt/sources.list.d/loraserver.list
sudo apt-get update
(https://www.loraserver.io/install/install/)
Note: the old repository located at repos.loraserver.io
will redirect to the above URL, so there is no need to make any changes now
The past years many changes have been introduced, some of them involving manual steps when upgrading from an older version. This was needed as at an early stage of the project it was not always possible to stay backwards compatible, stay in sync with the LoRaWAN specifications and keep the development on speed. However, as LoRa Server is being used more and more in production (some deployments involve around 300.000 devices!), a bit more care is needed
My plan is to soon release a 1.0.0 release of the LoRa Server components (this does not work for LoRa Gateway Bridge, as it is already at 2.x) and provide a repository per major version. This means:
- When using the
1.x
repository, anapt upgrade
will never upgrade the LoRa Server components to2.x
- All components within the same repository will be compatible
- From
1.x
onwards, there will only be backwards incompatible changes when changing to the next major release (1.x
->2.x
->3.x
).
Then per major repository there will be a stable
and testing
distribution. When you’re adventurous and want the latest features (e.g. testing at home, non critical deployments) you use the testing
distribution, for production you then probably want to use the stable
distribution.
E.g.
# current 0.x repository
deb https://artifacts.loraserver.io/packages/0.x/deb testing main
# future 1.x repositories
deb https://artifacts.loraserver.io/packages/1.x/deb stable main
deb https://artifacts.loraserver.io/packages/1.x/deb testing main
As LoRa Gateway Bridge is already at 2.x, I have added this to the 0.x
repository and it will also be part of the 1.x
. Starting with the 2.x
repository it will also stay in sync with the other components major versions