This message was deleted.
# hobbyfarm
a
This message was deleted.
w
I can add some color here in a bit
m
No rush. I just wanted to make sure I understood its purpose as I’m restructuring things a bit.
f
We should move this page from setup to another section. We should create another page that lists all available options and their purpose. The existing settings page is mainly targeted at developers that want to add custom settings to hobbyfarm - not for people installing and using hobbyfarm
m
That’s what I thought as well. I’ve moved it to the Appendix for now, but will most likely move it to the contributors section once that gets flushed out. I’ve flushed out the actual Settings document for the Admin-UI which should allow users/admins to more easily understand the initial setup.
f
Appendix seems fine.
Thank you for your work so far. This is really great!
m
Absolutely. It’s really helped me understand the project at a much deeper level than before.
I’ve updated the Settings page so that it now lives under the Contributing section and have flushed it out a bit so it should be more clear than before.
One major take-away I had with the Settings resource is how the variables are all on the top level. For example:
Copy code
apiVersion: <http://hobbyfarm.io/v1|hobbyfarm.io/v1>
dataType: boolean
kind: Setting
metadata:
  labels:
    <http://hobbyfarm.io/setting-scope|hobbyfarm.io/setting-scope>: public
  name: registration-disabled
  namespace: hobbyfarm
value: "true"
valueType: scalar
I’m curious if it would be of benefit to have it nested to reduce confusion:
Copy code
apiVersion: <http://hobbyfarm.io/v1|hobbyfarm.io/v1>
kind: Setting
metadata:
  labels:
    <http://hobbyfarm.io/setting-scope|hobbyfarm.io/setting-scope>: public
  name: registration-disabled
  namespace: hobbyfarm
settings:
  dataType: boolean
  value: "true"
  valueType: scalar
f
@worried-fountain-60974
w
We could do this. However it would be a breaking change and would require writing a conversion webhook and adding a v2 CRD
👍 1