meshviewer: replace manual tasks with automation#189
Conversation
|
Could you add a check which version is currently deployed so it does not need to download it on every deployment? |
7010115 to
f987a5d
Compare
|
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. |
f987a5d to
dec48f0
Compare
|
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 |
dec48f0 to
33049ef
Compare
|
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 |
|
But how do you know if you need to download something? You could add the Version to the downloaded file name. |
|
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:
As the release file should change with every release this approach should work. If you still prefer another way just let me now. |
|
Ok, i am confused by anisble: |
Set a fixed version that can be updated with version control. Automate the updating step.