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
Bulding Form Builder or Domino Visual Editor database with Vagrant does not work currently when using Domino 12.0.2 (since the update site is not generated properly). This may be investigated separately, but for now we don't have a workaround.
We have been working on supporting Domino 12.0.1 in Super.Human.Installer, but we also need a way to warn the user if a Vagrant instance does not have the correct version of Domino.
When the user runs Project > Run on Vagrant, check the Domino version and show a warning in the prompt as the user selects a Vagrant instance.
Alternatively, we could add logic to the provisioner to not add the nsfodp capability depending on the Domino version. This would allow us to update the restrictions on the provisioner side as we support newer versions of Domino. However, in this case the user would not see a warning - the vagrant instance would be excluded from the list instead.
The text was updated successfully, but these errors were encountered:
Bulding Form Builder or Domino Visual Editor database with Vagrant does not work currently when using Domino 12.0.2 (since the update site is not generated properly). This may be investigated separately, but for now we don't have a workaround.
We have been working on supporting Domino 12.0.1 in Super.Human.Installer, but we also need a way to warn the user if a Vagrant instance does not have the correct version of Domino.
We discussed a design like this:
Alternatively, we could add logic to the provisioner to not add the
nsfodp
capability depending on the Domino version. This would allow us to update the restrictions on the provisioner side as we support newer versions of Domino. However, in this case the user would not see a warning - the vagrant instance would be excluded from the list instead.The text was updated successfully, but these errors were encountered: