Skip to content

meshviewer: replace manual tasks with automation#189

Merged
nicolasberens merged 4 commits intomainfrom
more-automation
Feb 12, 2026
Merged

meshviewer: replace manual tasks with automation#189
nicolasberens merged 4 commits intomainfrom
more-automation

Conversation

@FFHener
Copy link
Contributor

@FFHener FFHener commented Jan 28, 2026

Set a fixed version that can be updated with version control. Automate the updating step.

@nicolasberens
Copy link
Contributor

Could you add a check which version is currently deployed so it does not need to download it on every deployment?

@FFHener
Copy link
Contributor Author

FFHener commented Feb 4, 2026

I solved it by storing the downloaded zip in /opt/meshviewer alongside the other files. Ansible wont redownload the file and since its < 2 MB i think its ok to leave it there.

@nicolasberens
Copy link
Contributor

it will still unpack the package every time.

i took a look and it does not seem like meshviewer has an easily readable way to determine the version.

you could e.g. add a file in /var/www/hopglass.berlin.freifunk.net/meshviewer_version with the version number currently deployed and decide based on that if a new version shoud be deployed

@FFHener
Copy link
Contributor Author

FFHener commented Feb 4, 2026

I was thinking about a version number as well, but this felt like a more build in way of handling things. I made the unpacking part a handler so it will only run when something new gets downloaded

@nicolasberens
Copy link
Contributor

But how do you know if you need to download something?

You could add the Version to the downloaded file name.

@FFHener
Copy link
Contributor Author

FFHener commented Feb 11, 2026

The get_url module should handle it fine. If force is false (default) than the module only downloads the file if something changed. I tested the following to confirm it works:

  1. 13.0.0 is installed
  2. Redo a ansible run => Nothing gets downlaoded or applied
  3. Change meshviewer_version: 13.0.0 to meshviewer_version: 12.8.0
  4. Redo a ansible run => Old release gets downloaded and apllied
  5. Redo a ansible run => Nothing gets downloaded or applied
  6. Change meshviewer_version: 12.8.0 to meshviewer_version: 13.0.0
  7. Redo a ansible run => New release gets downloaded and applied
  8. Redo a ansible run => Nothing gets downloaded or applied

As the release file should change with every release this approach should work. If you still prefer another way just let me now.

@nicolasberens
Copy link
Contributor

Ok, i am confused by anisble:
running it with --check shows 2 changes, but without it says nothing changed ...

@nicolasberens nicolasberens merged commit 2ce93a7 into main Feb 12, 2026
1 check passed
@nicolasberens nicolasberens deleted the more-automation branch February 12, 2026 20:23
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

Successfully merging this pull request may close these issues.

2 participants