Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Re-visit storage of farm.info #103

Closed
paul121 opened this issue Nov 17, 2020 · 3 comments
Closed

Re-visit storage of farm.info #103

paul121 opened this issue Nov 17, 2020 · 3 comments
Labels
2x farmOS 2x support

Comments

@paul121
Copy link
Member

paul121 commented Nov 17, 2020 •
edited

We currently save the content farm.json in the Aggregator DB for each farm. This information is not returned via the Aggregator API unless explicitly queried.

farmOS 2x uses JSONAPI and has a different structure for the "farm info" data. I think there is value in saving it within the Aggregator, but maybe we don't need all the keys returned by the root /api endpoint.

The changes are documented here under "Farm info endpoint": http://2x.farmos.org/api/changes/
@paul121
Copy link
Member Author

paul121 commented Nov 17, 2020

Related issue re: not returning the farm.json data via API: #90

@paul121 paul121 mentioned this issue Nov 17, 2020
Open
@paul121 paul121 added the 2x farmOS 2x support label Nov 17, 2020
@paul121
Copy link
Member Author

paul121 commented Nov 17, 2020

A reason to keep storing the server info: #106

paul121 added a commit that referenced this issue Mar 4, 2021
@paul121
Load version specific info. #103
a918696
@paul121
Copy link
Member Author

paul121 commented Mar 4, 2021

My first pass just saves the root meta.farm info from 2.x. This was easy enough to match with the existing info model.

Next step would be saving the links attributes from the root JSON:API document, roughly equivalent to the resources from 1.x, but in quite a different structure. This reminds me of JSON Schema related questions... perhaps links could be part of a later initiative to include all the schemas from the farmOS server?

@paul121 paul121 closed this as completed Mar 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2x farmOS 2x support
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paul121