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

Update stacks-node and add stacks-signer #1379

Closed
hugocaillard opened this issue Mar 11, 2024 · 1 comment · Fixed by #1384
Closed

Update stacks-node and add stacks-signer #1379

hugocaillard opened this issue Mar 11, 2024 · 1 comment · Fixed by #1384
Assignees

Comments

@hugocaillard
Copy link
Collaborator

  • update stacks-node image
  • update stack-stx (new arguments in pox-4 for stack-stx and extend)
  • add the signer image to the devnet
@hugocaillard hugocaillard self-assigned this Mar 11, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Mar 11, 2024
@hugocaillard hugocaillard moved this from 🆕 New to 📋 Backlog in DevTools Mar 11, 2024
@sabbyanandan
Copy link
Contributor

@hugocaillard: It is probably too early right now, but when the time is right, it'd be good to get a sense of the Docker daemon's compute requirements (i.e., what is a reasonable CPU, disk, and memory defaults?), including the additional resources (for instance, a new "signer image") that need to be spun up. We can add/update the pre-requisite section in docs/README.

In the Platform, we will automatically apply and handle the dynamic allocation of new resource requirements for each user.

@hugocaillard hugocaillard moved this from 📋 Backlog to 🏗 In Progress in DevTools Mar 18, 2024
@github-project-automation github-project-automation bot moved this from 🏗 In Progress to ✅ Done in DevTools Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants