Open JoelProminic opened 11 months ago
Some additional notes which may be off topic.
I confirmed that the generated Hosts.yml matched the format for new server, as long as I update the original server to use the latest demo-tasks version. This is a good sign for reusing the server.
I did not have actions to remove either server. Restarting SHI did not fix this problem:
I have bring back delete button from debug - for some reason it was conditioned to show only in debug mode. Now in theory you shouldn't end up with scenario where there is no option for deleting server. Please test it and let me know if it's resolve issue.
Additionally I have also get Open folder up in scenario when server is Starting/Stopped - To cover rest of the scenario I need more time - that is at least improvement.
I believe there is a mechanism to copy the installer based on OS.
In Mac and Linux, it was able to easily make a symlink, but on Windows, I believe it copies the file. This is a vague recollection, and may be dismissed if this was fixed.
I'm moving this issue for farther investigation to the next milestone.
I tried to test with production Super.Human.Portal 0.8.17 on macOS Monterey today. I had an existing server provisioned and running. Normally I delete the servers before updating, but I didn't remember to do it this time. After the update, I found that SHI reported that the application needed configuration. Note that I did not have buttons to stop or delete the running instance.
When I checked the configuration, I found that all options and the Save button were disabled. I'm pretty sure I couldn't open "Manage" from this state:
To fix this, I:
vagrant destroy
So, the problem could have been the invalid installer paths instead of the update. I can try a test with this after I finish a sanity test for 0.8.17.
UPDATE: I confirmed that this was caused by the installer. You can reproduce this with:
SH should skip the installer verification for a fully provisioned VM. This will allow users to delete the installers if desired after creating the VM (though they would need the installers again to recreate the VM).