Yes, Docker provides a simple way to incorporate stellar-core and horizon into your infrastructure so long as BUCKET_DIR_PATH, TMP_DIR_PATH, and the database are stored on persistent volumes.
First, decide whether you want your container to be part of the public, production Stellar network (referred to as the pubnet) or the test network (called testnet) ...
Version 9.2 does not support version 10 of the protocol.
You can import a subset of the historical data (with command line catch-up), install the latest release candidate (10.0.0rc2 labeled "testing" in the quickstart image) or wait for a stable build (should be out in the next couple weeks).
a) I guess the easiest way should be to run your testnet node in a non persistent ephemeral mode and simply restart the container.
b) You could as well open a shell into your container and manually recreate everything similar to the package way.
# open container shell
docker exec -it [CONTAINER ID] /bin/bash
# stop core + horizon
You will need to run a Stellar Core + Horizon instance. However it probably won't help you to install and configure these by hand for your use case and timeline.
Check out the summary doc here for a short list of the paths you can take: https://github.com/stellar/go/tree/master/services/horizon
To start out quickly, I would definitely recommend the Docker ...
Had the same problem but it seems I figured it out. If you want the full history available on your horizon you need to do the following.
Run your stellar-core with CATCHUP_COMPLETE=true. On your horizon side you need to manually tell it to ingest historical ledgers. Just starting horizon with --ingest=true is not enough as it will only ingest ledgers that ...
This is kinda old question, but can be of help to others.
For what you want to do, you need to remove current container with docker rm stellar to clear stellar namespace or just use a different name.
Then, for starting a persistent stellar node, run
docker run -dit --restart always -v "/str:/opt/stellar" -p "8000:8000" --name stellar stellar/quickstart --...
So the problem is that the standalone configuration does not allow access to the network. Therefore, the node can not talk to other connecting nodes.
If you want other nodes to connect to the standalone node, make sure you set the RUN_STANDALONE=true to RUN_STANDALONE=false in your
The adapted standalone config should look like this:
It looks like your Postgres server is either not installed or mis-configured. Can you connect to it from the command line?
You need to configure it to allow local connections. See https://www.postgresql.org/docs/9.1/auth-pg-hba-conf.html for more info.
Ran into this issue today. I was able to check what the DATABASE_URL value that cmd horizon db migrate up expected by looking at horizon.env within the stellar/quickstart docker container. I then ran the command export DATABASE_URL=postgres://stellar:mypass@localhost/horizon && horizon db migrate up and migration was successful. Seems the env vars in ...
I struggled with this as well because basically the documentation is a bit fuzzy on what is what and on the overall architecture.
All you need to be an anchor is to use the public horizon endpoint + tools like the API explorer. You don't need any software running on your own servers other than a tiny stellar.toml file that defines your token. This can live ...
Put a loadbalancer, nginx, or apache in front of it. E.g. in amazon you would terminate https on the load balancer typically. You should not deploy your https private key to individual docker containers.
You can enter the docker container with docker exec -it stellar /bin/bash
Then enter supervisorctl
and then enter stop stellar-core. This will stop stellar-core.
Enter exit to exit supervisor.
Then edit the stellar-core.cfg file in the base directory of the docker container.
Type supervisorctl again and type start stellar-core
We have successfully customized our stellar-core configuration by following the documentation of https://hub.docker.com/r/stellar/quickstart/
To customize the configurations that both stellar-core and horizon use, you must use persistent mode. The default configurations will be copied into the data directory upon launching a persistent mode container for ...
Based on supervisorctl you are running the docker/quickstart image.
I had a similar issue recently. The cathup was running in circles and could not finish in days. I found the real issue by setting the LOG_FILE_PATH variable in core config and read the log for more information.
I had the DB in a corrupt state and the core could not apply the transactions ...
As I read from your supervisor uptime, it seems your instance had run for less than an hour, which is rather new. It takes many hours to finish "catch up" with the running network.
You may check your Horizon main page http://localhost:2011/, and look for information at the bottom like:
You can setup SSL offloading on the nginx server. Actually, it's one of the most common nginx use-cases. Browser interacts with your nginx server via HTTPS protocol, and then requests get proxied to the Horizon docker instance via HTTP.
Check the detailed guide for Let'sEncrypt with nginx on Ubuntu 16.04 by DigitalOcean.
When you run the docker image it should automatically start stellar-core.
In the container, can you try running ps aux | grep stellar-core | grep -v "grep" to see if stellar-core is already running?
If you are already running something on port 8000 (i.e. bound to port 8000) on your localhost then it will not work. You can change your command to use a ...
For just federation -- no compliance -- the above sounds correct. As outlined in the docs, which you mentioned you have read through, this is easily done via Stellar's prebuilt federation server which can hook into an existing database. Once it is connected, it
essentially translates a federation request into a SQL query. The
server supports MySQL, ...
The Federation server would return some value with the memo field that can be used by the service provider (you) to uniquely identify the receiving user. A database ID does match this requirement but you can use anything else that makes sense in your domain as long as it's unique (also in the future).
The bridge server does also help to participate with the ...
Are you sure you are using the latest image available? It's possible that your image is cached on your disk while a new version is available in docker repository. Try this to remove the image:
docker rmi -f stellar/quickstart:latest
and then run your the container using a standard command.