-
Notifications
You must be signed in to change notification settings - Fork 0
chore: create a docker image using hardhat-node #535
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 15856152040Details
💛 - Coveralls |
…rs in the container deploy flow (required for meta-tx-gateway e2e env)
albertfolch-redeemeum
previously approved these changes
Jun 13, 2025
0xlucian
reviewed
Jun 13, 2025
zajck
reviewed
Jun 17, 2025
zajck
previously approved these changes
Jun 17, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor comments, but otherwise looks good 👍
1c8e7bb
Co-authored-by: Klemen <64400885+zajck@users.noreply.github.com>
…d before merging)
…ntracts into e2e-tests-env
zajck
previously approved these changes
Jun 20, 2025
This reverts commit 13b2a9d.
0xlucian
approved these changes
Jun 24, 2025
albertfolch-redeemeum
approved these changes
Jun 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR creates a fermion-protocol-node container image which:
The container image is tagged with the current commit / release / pr (depending on how the workflow is trigerred - see https://github.com/docker/metadata-action?tab=readme-ov-file#semver), then pushed on Github Container registry of the current repo (https://github.com/fermionprotocol/contracts/pkgs/container/contracts%2Ffermion-protocol-node) + additionally to Docker Hub (at the moment on a temporary personal account - will be replaced with an organisation account - https://hub.docker.com/repository/docker/levalleuxludordm/fermion-protocol-node)
When the container is started, running the chain and deploying the contract are automatically trigerred as background processes (done with supervisord tool).
A few minutes later, the file /app/deploy.done is created to mean the deployment is completed and everything is ready to play with.
NOTE: BOSON PROTOCOL is not fully deployed and functional by itself.
For now, only facets used by FERMION + the MetaTransactionFacet are deployed and configured.
Later on, if we want the fermion-protocol-node container to be useful for BOSON+FERMION joined tests, we would need to have a fully installed and configured BOSON PROTOCOL.