As part of our (Fhenix) integration of all things Celestia into our nitro-testnode docker compose (similarly to https://github.com/celestiaorg/nitro-das-celestia/pull/2), we integrated Apollo as a service instead of running it locally.
There were a few small changes needed to make things easier to work with. In no particular order:
Added automatic funding of genesis accounts from the faucet using init scripts (there's probably a better way to do this, but without familiarity with the code I didn't want to go too deep)
Added celestia and cel-key binaries to the runner for easier debugging/operations in runtime
Fixed the Dockerfile build (the latest changes to the file names/etc break it). Also added a .dockerignore for good measure
Added optional listening address and changed it to be 0.0.0.0 so it can accept external connections instead of localhost
This makes it so you can build the docker and just throw it into the nitro-testnode docker-compose and have it work out of the box, which saves a bit of setup.
As I said in the other PR - feel free to close it or not merge if this doesn't align with what you want to do, or use some/all/none of it as you see fit. Just trying to contribute back a little to make someone's life a bit easier :smile:
As part of our (Fhenix) integration of all things Celestia into our nitro-testnode docker compose (similarly to https://github.com/celestiaorg/nitro-das-celestia/pull/2), we integrated Apollo as a service instead of running it locally.
There were a few small changes needed to make things easier to work with. In no particular order:
This makes it so you can build the docker and just throw it into the nitro-testnode docker-compose and have it work out of the box, which saves a bit of setup.
As I said in the other PR - feel free to close it or not merge if this doesn't align with what you want to do, or use some/all/none of it as you see fit. Just trying to contribute back a little to make someone's life a bit easier :smile: