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.

Sign up for GitHub

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

Jump to bottom

Automated devnet deployment with Kurtosis #56

Closed
unnawut opened this issue Jan 31, 2025 · 1 comment
Closed

Automated devnet deployment with Kurtosis #56

unnawut opened this issue Jan 31, 2025 · 1 comment
Assignees
@unnawut
Labels
Networking p3 Low priority wontfix This will not be worked on
Milestone
v0.1.0

Comments

@unnawut
Copy link
Contributor

unnawut commented Jan 31, 2025

Blocked by #11, #38

Criteria

  • One can run a command to spin up their own local devnet of ream clients
  • Potentially using Kurtosis
@unnawut unnawut self-assigned this Jan 31, 2025
@unnawut unnawut added Networking p3 Low priority labels Jan 31, 2025
@unnawut
Copy link
Contributor Author

unnawut commented Feb 5, 2025

Closing as we don't need Kurtosis for the time being

I can set Kurtosis config in 5 mins but it doesn't really work anyway? We need working VC, CL and EL but we have decided to not make a beacon node. I think just unit tests are enough.

yeah no i dont think we need kurtosis now, maybe until we have some sort of p2p networking working? nice to have for demo’ing

I think docker compose would work for that purpose

@unnawut unnawut closed this as completed Feb 5, 2025
@unnawut unnawut added the wontfix This will not be worked on label Feb 5, 2025
@KolbyML KolbyML added this to the v0.1.0 milestone Feb 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@unnawut unnawut

Labels
Networking p3 Low priority wontfix This will not be worked on
Projects
Ream Client
Status: Done
Milestone
v0.1.0
Development

No branches or pull requests
2 participants
@unnawut @KolbyML