You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alright folks, welcome to ACARS Hub v3, or ACARS Hub NextGen
Before I start, don't worry, your v2 installs will remain untouched. You have to explicitly change your docker-compose.yaml file to switch. At this point, though, v2 is no longer supported and all of the work will now be on NextGen.
Once running, you shouldn't notice a thing different. It should look the same (minus a few bug fixes), it should function the same, it should log the same messages, everything.
I've spent the last two weeks, give or take, removing the decoders from the ACARS Hub container and creating containers to run the decoders separate from ACARS Hub. This is to reduce complexity in setup of the container, maintaining the backend code and services, etc. This change will also let you run ACARS Hub on one Pi, and the decoders on another, opening a world where you can now feed ACARS messages in from as many sites as you want. It's all up to you.
If, for some reason, you experience difficulties with ACARS Hub NextGen you can change your compose back to what it is now and be back up and running. I ask that if you need to do that please let me know via a GitHub issue, or on discord, letting me know what is going on.
To move to NextGen, please do the following
BACK UP YOUR CURRENT COMPOSE FILE
No really, please back it up :)
Visit here to see the new containers and how they are meant to be set up. Remove the current acarshub config and replace it with what is in that file. It should be super easy to copy old values from your current config and paste them in the appropriate spots. If you aren't sure, or need help, please let me know on discord or GitHub issue and I'll be happy to help.
Once you have done that, a docker compose up -d (or `docker-compose up -d if you are using the old compose) should get you up and running with no problems.
The text was updated successfully, but these errors were encountered:
Alright folks, welcome to
ACARS Hub v3
, orACARS Hub NextGen
Before I start, don't worry, your v2 installs will remain untouched. You have to explicitly change your
docker-compose.yaml
file to switch. At this point, though, v2 is no longer supported and all of the work will now be on NextGen.Once running, you shouldn't notice a thing different. It should look the same (minus a few bug fixes), it should function the same, it should log the same messages, everything.
I've spent the last two weeks, give or take, removing the decoders from the ACARS Hub container and creating containers to run the decoders separate from ACARS Hub. This is to reduce complexity in setup of the container, maintaining the backend code and services, etc. This change will also let you run ACARS Hub on one Pi, and the decoders on another, opening a world where you can now feed ACARS messages in from as many sites as you want. It's all up to you.
If, for some reason, you experience difficulties with ACARS Hub NextGen you can change your compose back to what it is now and be back up and running. I ask that if you need to do that please let me know via a GitHub issue, or on discord, letting me know what is going on.
To move to NextGen, please do the following
acarshub
config and replace it with what is in that file. It should be super easy to copy old values from your current config and paste them in the appropriate spots. If you aren't sure, or need help, please let me know on discord or GitHub issue and I'll be happy to help.docker compose up -d
(or `docker-compose up -d if you are using the old compose) should get you up and running with no problems.The text was updated successfully, but these errors were encountered: