3 ms·
If anyone wants to know the stack it's Django/Postgres on the backend, and an Elm SPA frontend. All data goes through an undocumented REST API.
by keithasaurus 9y ago
If anyone wants to know the stack it's Django/Postgres on the backend, and an Elm SPA frontend. All data goes through an undocumented REST API.
- brntn 9y agoNice work! Are you using mptt or treebeard under the hood to manage the forking?
- keithasaurus 9y agoNope. It's a pretty simple relation to express without external libraries, so I figured I'd keep the granular control and just do foreign keys. Easier to refactor schema or migrate data that way.
- dpapathanasiou 9y agoNice project! If you need more data, check out this: https://github.com/dpapathanasiou/recipebook https://github.com/dpapathanasiou/recipebook I've also enabled it to talk to this via TOTP, if you ever decide to switch to/want to enable mongo as your recipe doc store: https://github.com/dpapathanasiou/ARMS https://github.com/dpapathanasiou/ARMS Good luck with it, and keep us posted!
- keithasaurus 9y agoThanks, but we have our own importer. BTW, I'd suggest writing a metadata fallback in your library. You'd be surprised how many sites will work just on parsing json linked data or schema.org's Recipe format. Good luck!