You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An approach that was taken to ease the setup for a partner organisation (Lido) was to create a fork of this repository and configure it for their specific needs. However, this is hard to scale solution - this repo is constantly changing and having to replicate that to all future partner repos is not feasible.
It would be beneficial if this repository can accommodate different partners and setups, so that everyone can use it and easily tweak what they want to use. Start with an implementation of the custom setup we have for Lido and make it easy for them to use the CDVN repo, instead of the LCDVN repo.
The text was updated successfully, but these errors were encountered:
🎯 Problem to be solved
An approach that was taken to ease the setup for a partner organisation (Lido) was to create a fork of this repository and configure it for their specific needs. However, this is hard to scale solution - this repo is constantly changing and having to replicate that to all future partner repos is not feasible.
It would be beneficial if this repository can accommodate different partners and setups, so that everyone can use it and easily tweak what they want to use. Start with an implementation of the custom setup we have for Lido and make it easy for them to use the CDVN repo, instead of the LCDVN repo.
The text was updated successfully, but these errors were encountered: