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
Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Steps to reproduce
Set up a docker-socket-proxy deploy target, make sure the test deploy is working properly, and then deploy Windmill with occ
Open the Windmill workspace and let it automatically set stuff up
In the left sidebar, go to Resources, then switch tabs to "Resource Types"
Expected behaviour
I see a lot of resource types from hub.windmill.dev.
Actual behaviour
There are no resource types available out of the box, except for the Nextcloud resource type (I think? I can't remember).
These are only populated if you switch to the Admins workspace and then run the flow to sync with the Hub. Additionally, you have to enable a scheduled sync manually. (I gather from the "New User Setup App" flow in the Admins workspace that in a standalone Windmill installation, this stuff is configured during initial setup.)
Server configuration
N/A
Browser
N/A
The text was updated successfully, but these errors were encountered:
How to use GitHub
Steps to reproduce
Expected behaviour
I see a lot of resource types from hub.windmill.dev.
Actual behaviour
There are no resource types available out of the box, except for the Nextcloud resource type (I think? I can't remember).
These are only populated if you switch to the Admins workspace and then run the flow to sync with the Hub. Additionally, you have to enable a scheduled sync manually. (I gather from the "New User Setup App" flow in the Admins workspace that in a standalone Windmill installation, this stuff is configured during initial setup.)
Server configuration
N/A
Browser
N/A
The text was updated successfully, but these errors were encountered: