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
Love Cosmos server! Just installed and noticed that Vandam has changed, as seen here, Vandam has changed their name to Manifold. Upon entering the site, we are given a warning that the name has changed and in order to continue to receive updates, the image must be changed to ghcr.io/manyfold3d/manyfold
What should have happened?
The Vandam image / name in the Market should be swapped to reflect this.
How to reproduce the bug?
Go to Market
Click on Vandam
Install
Open page
See message telling you to switch
Relevant log output
No response
Other details
No response
System details
N/A
The text was updated successfully, but these errors were encountered:
Hello! I'm the developer of Manyfold! I've just come across Cosmos Cloud, and was amazed to see that people are running my code on it 😁
Is there anything I can do to help make the change? I'm not familiar with the way apps are defined, but I'm happy to make whatever change required, and add Cosmos to the list of installation methods at https://manyfold.app/get-started/
With a description file and a screenshot folder. It works almost the same as the normal yml compose except it's in json a has 1 or 2 additional features (but the API is the same). If you can make the amend on that folder I will happily merge it!
What happened?
Love Cosmos server! Just installed and noticed that Vandam has changed, as seen here, Vandam has changed their name to Manifold. Upon entering the site, we are given a warning that the name has changed and in order to continue to receive updates, the image must be changed to
ghcr.io/manyfold3d/manyfoldWhat should have happened?
The Vandam image / name in the Market should be swapped to reflect this.
How to reproduce the bug?
Relevant log output
No response
Other details
No response
System details
N/A
The text was updated successfully, but these errors were encountered: