-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Look into if modeling data differently in the DB has benefits #51
Comments
duanhongyi
added a commit
to duanhongyi/controller
that referenced
this issue
Nov 26, 2021
chore(chart): modify the problem of using buildpack and pretty pods list print
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @helgi on September 15, 2016 23:13
Instead of JSONField consider doing a parent/child model to handle proc type information. (and other nested information). Autoscales model with Autoscale for web and worker records. This will only work in some cases. Might not map to health checks very well given it is a very nested structure.
There are two reasons why I want to see some exploration on this
This may not be viable at all, or is only viable when dealing with very simple structures, at best when we know it needs to only map down to the level of process type
Copied from original issue: deis/controller#1075
The text was updated successfully, but these errors were encountered: