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

Support for Testnet parameterization #131

Closed
bdchatham opened this issue Oct 14, 2024 · 3 comments
Closed

Support for Testnet parameterization #131

bdchatham opened this issue Oct 14, 2024 · 3 comments
Labels

Comments

@bdchatham
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Today, there is no configurability to run this infrastructure on a testnet. As a blockchain engineer, it would be very helpful to have a best-practice setup selectable via a parameter.

Describe the solution you would like

I would like to be able to specify an environment variable which instructs the stacks to use different runtime parameters in the docker-compose files.

Describe alternatives you have considered

As a blockchain engineer, I can manually change these values, but begs the question if other changes are needed unique to those networks/codifying this is then not possible because it requires a local change.

Additional context

@frbrkoala
Copy link
Contributor

Thank you for this suggestion! I'll put it into our backlog to research.
If you have a suggestion on how this can be implemented in more details, please don't hesitate to suggest as well!

Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Nov 17, 2024
Copy link
Contributor

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants