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 Ellipal metadata #1190

Merged
merged 1 commit into from
Oct 27, 2021
Merged

Add Ellipal metadata #1190

merged 1 commit into from
Oct 27, 2021

Conversation

xdzurman
Copy link
Contributor

No description provided.

@xdzurman xdzurman requested a review from PeterBenc October 26, 2021 06:51
@mlenik mlenik temporarily deployed to adalite-ellipal-metadat-gc5vg1 October 26, 2021 06:52 Inactive
@@ -0,0 +1,7 @@
{
Copy link
Collaborator

@refi93 refi93 Oct 26, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get that we have the pools metadata in public due to historical reasons and it's tricky to switch because we'd have to update the pool registrations, but I'd consider at least moving in the codebase the metadata to public/pools_metadata subfolder so it's reasonably organized at least in the code, and serve them directly from our express backend, leaving there a clarifying comment why we are overriding the path when serving

as discussing offline, probably worth a follow-up issue so I'm creating it: #1191

@xdzurman xdzurman merged commit 0be5eba into develop Oct 27, 2021
@xdzurman xdzurman deleted the ellipal-metadata branch October 27, 2021 14:21
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

Successfully merging this pull request may close these issues.

3 participants