Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Welcome to ACARS Hub Next Gen #332

Open
fredclausen opened this issue Feb 6, 2022 · 0 comments
Open

Welcome to ACARS Hub Next Gen #332

fredclausen opened this issue Feb 6, 2022 · 0 comments

Comments

@fredclausen
Copy link
Member

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant