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

[Chore]: Production docker compose #785

Open
2 tasks
AshtonStephens opened this issue Nov 6, 2024 · 2 comments · May be fixed by #813
Open
2 tasks

[Chore]: Production docker compose #785

AshtonStephens opened this issue Nov 6, 2024 · 2 comments · May be fixed by #813
Assignees
Labels
chore unplanned An issue that was originally not part of the Milestone planning

Comments

@AshtonStephens
Copy link
Collaborator

Chore - Production docker compose

1. Description

Create a docker compose that spins up all the necessary containers for a signer to run sBTC in production.

2. Why It's Necessary

People running signers need to be able to spin up the infrastructure quickly and smoothly. This GitHub issue is to make the docker compose that sets all the entities up.

3. Execution Checklist

  • Create a docker compose that can run all the necessary production infrastructure
  • Have that docker compose in a PR and merged
@AshtonStephens AshtonStephens added chore unplanned An issue that was originally not part of the Milestone planning labels Nov 6, 2024
@AshtonStephens AshtonStephens added this to the sBTC Release Ready milestone Nov 6, 2024
@AshtonStephens AshtonStephens self-assigned this Nov 6, 2024
@github-project-automation github-project-automation bot moved this to Needs Triage in sBTC Nov 6, 2024
@AshtonStephens
Copy link
Collaborator Author

@aldur what do we envision to be the immediate purpose of this docker compose? Is this to give people an idea of what's necessary or be exactly what they anticipate using in prod?

Additionally, I'd like to propose that we don't include a stacks node in this, and we expect them to have that already running so we separate this compose from any changes made to the stacks core images. WDYT?

@AshtonStephens AshtonStephens moved this from Needs Triage to Todo in sBTC Nov 6, 2024
@aldur
Copy link
Collaborator

aldur commented Nov 6, 2024

@aldur what do we envision to be the immediate purpose of this docker compose? Is this to give people an idea of what's necessary or be exactly what they anticipate using in prod?

Let's assume that signers will use this either verbatim or as a base (e.g., if deploying through K8).

Additionally, I'd like to propose that we don't include a stacks node in this, and we expect them to have that already running so we separate this compose from any changes made to the stacks core images. WDYT?

I agree. Would it be feasible for signers that are not already running their node to rely on a node provider?

@AshtonStephens AshtonStephens linked a pull request Nov 11, 2024 that will close this issue
4 tasks
@AshtonStephens AshtonStephens linked a pull request Nov 11, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore unplanned An issue that was originally not part of the Milestone planning
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

2 participants