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

Investigate deploying the application with Solo #1207

Open
SimiHunjan opened this issue Nov 19, 2024 · 3 comments
Open

Investigate deploying the application with Solo #1207

SimiHunjan opened this issue Nov 19, 2024 · 3 comments
Labels
P1 High priority issue. Required to be completed in the assigned milestone.
Milestone
v0.7

Comments

@SimiHunjan
Copy link
Contributor

Problem

The application is not currently deployed with Solo.

Solution

Review Solo and identify how the Transaction Tool can be deployed with it.

Alternatives

No response
@SimiHunjan SimiHunjan added the P1 High priority issue. Required to be completed in the assigned milestone. label Nov 20, 2024
@RAMTO RAMTO added this to the v0.4.3 milestone Nov 22, 2024
@RAMTO
Copy link
Contributor

RAMTO commented Nov 27, 2024

@SimiHunjan Please provide more details regarding this issue.

@SimiHunjan
Copy link
Contributor Author

Yes, this is the Solo project: https://github.com/hashgraph/solo. We want to spin up the backend of the Transaction Tool when a new Solo network is created just like the services are automatically deployed like consensus node, mirror node, etc. This way the backend of the Transaction Tool can automatically be setup for use. The expectation is that our team would contribute a PR to Solo that adds this functionality, I believe this will entail creating a helm chart etc.

@SimiHunjan SimiHunjan modified the milestones: v0.5, v0.6 Dec 4, 2024
@SimiHunjan SimiHunjan added P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. P3 Low priority issue. Will not impact the release schedule if not complete. and removed P1 High priority issue. Required to be completed in the assigned milestone. P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. labels Dec 4, 2024
@SimiHunjan SimiHunjan modified the milestones: v0.6, v0.7 Dec 18, 2024
@SimiHunjan SimiHunjan added P1 High priority issue. Required to be completed in the assigned milestone. and removed P3 Low priority issue. Will not impact the release schedule if not complete. labels Jan 2, 2025
@jbair06
Copy link
Member

jbair06 commented Jan 7, 2025

Work has begun, see #1424

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P1 High priority issue. Required to be completed in the assigned milestone.
Projects
None yet
Milestone
v0.7
Development

No branches or pull requests
3 participants
@RAMTO @SimiHunjan @jbair06