We would like to stop supporting https://play.grid.tf in favor of https://playground.grid.tf , are you missing any features or facing any bugs that forces us to keep supporting the legacy playground?
Phasing out the old playground?
2 Likes
One change i notice is the shift from capacity filter to farm name - what happens behind the scene where the farm have multiple nodes - does it random pick one of the nodes? 
By the way - great work on the new playground 
2 Likes
I think we would still need the option to decide on which node to deploy on the new playground
For example I had to redo a whole deployment and had to use the old playground to make sure the node I wanted would get the deployment.
It’s not a matter of ‘thinking we need that’, we DO need that first. Me, as well as our customers, should be able to decide which node to deploy on. Until that option is back I’m not even considering switching, sorry.
1 Like
(https://playground.dev.grid.tf/#/vm)
Looks like it’s already in on dev net.
So the feature of choosing a node will be there in playground (new).
I would say we can get rid of the old playground once this is to main net and test net.
Let’s see if others have some parameters they want in the new playground that is only in the old playground.
1 Like
Send it, it’s a massive improvement and the hold outs won’t give it the time and feedback it deserves if it stays around.
1 Like