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
{{ message }}
This repository has been archived by the owner on Nov 21, 2022. It is now read-only.
As a community developer, i want to customize a new Stack with Heighliner tools, what should i do ?
Currently, all stacks are created by Heighliner team and the source code of which existed in h8r-dev/stacks GitHub repo.
What developers want is: he want to owns the created stack repo, Heighliner Stacks just an engine to him, he create custom chain components in his own stack repo, import 'h8r-dev/stacks' library, and then build his own stack.
Solution
All chain components used by a stack should be imported directly in plan.cue file, and then customization part of a stack should reside with plan.cue file and imported in plan file.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Background
As a community developer, i want to customize a new Stack with Heighliner tools, what should i do ?
Currently, all stacks are created by Heighliner team and the source code of which existed in
h8r-dev/stacks
GitHub repo.What developers want is: he want to owns the created stack repo, Heighliner Stacks just an engine to him, he create custom chain components in his own stack repo, import 'h8r-dev/stacks' library, and then build his own stack.
Solution
All
chain
components used by a stack should be imported directly inplan.cue
file, and then customization part of a stack should reside withplan.cue
file and imported in plan file.The text was updated successfully, but these errors were encountered: