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.

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

Add support for using unfurl export api instead of running unfurl export locally #148

Open
aszs opened this issue Aug 18, 2022 · 0 comments

Comments

@aszs
Copy link
Member

aszs commented Aug 18, 2022

In https://github.com/onecommons/unfurl-gui/blob/handover/apollo-server/utils/iterate_projects.js getBlueprintJson() loads the exported json from the locally cloned projects unfurl.json file. Before it does that it checks if the ensemble's yaml files are newer than unfurl.json and, if so, regenerates it by running unfurl export. Let's an config option that points to an unfurl api service url and if set use that instead of trying to load unfurl.json. To support automatic reexporting when the ensemble changes, keep a timestamp of the last time the api was hit. We also should add support for an url parameter that forces hitting the api for a re-export.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant