Replies: 2 comments 3 replies
-
|
Soooo youre using beta software in production? Anyways.... I'm sure we could figure somthing out. |
Beta Was this translation helpful? Give feedback.
-
Not in production but a real issue within my team too, I am hosting some bizzare node js app and reverse proxying it. Just using pelican for sake of my familiarity and management help. Just thought that presenting it in a way that others may be able to resonate with would be better for the sake of this discussion |
Beta Was this translation helpful? Give feedback.
-
We should add something like "Avoid users to remove primary allocations" maybe for hostings... |
Beta Was this translation helpful? Give feedback.
-
Why not add an attribute to allocations like 'admin_defined' or 'required' (someone can do a better job than me with the naming ofc) and those can then only be deleted by admins? This system would work really well with eggs or games that need multiple allocations |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Users can delete primary allocations and other allocations for the server that have been assigned to them, it becomes an issue when they accidentally delete these allocations and then open up support tickets which have to be managed, allocations that were assigned to them were not meant to be deleted in the first place as they are necessary for the server for function for some eggs.
I understand that a counter argument can be to let them self allocate ports but then that also creates issues if you have like a script that handles reverse proxy creation for each server from billing panel and also if you use different network subnets for different clients to let them privately network in their bungee and stuff. Letting them self allocate will also allow them to allocate themselves to someone else's network
Beta Was this translation helpful? Give feedback.
All reactions