mirror of
https://github.com/aljazceru/python-teos.git
synced 2025-12-17 14:14:22 +01:00
updates
This commit is contained in:
@@ -5,7 +5,4 @@ WORKDIR /srv
|
|||||||
RUN mkdir ~/.teos && git clone https://github.com/aljazceru/python-teos.git && cd python-teos && pip install -r requirements.txt && python generate_keys.py -d ~/.teos
|
RUN mkdir ~/.teos && git clone https://github.com/aljazceru/python-teos.git && cd python-teos && pip install -r requirements.txt && python generate_keys.py -d ~/.teos
|
||||||
ENV PYTHONPATH=$APP_PATH
|
ENV PYTHONPATH=$APP_PATH
|
||||||
WORKDIR /srv/python-teos
|
WORKDIR /srv/python-teos
|
||||||
#COPY entrypoint.sh /srv/python-teos/entrypoint.sh
|
|
||||||
RUN chmod +x /srv/python-teos/entrypoint.sh
|
|
||||||
ENTRYPOINT [ "/srv/python-teos/entrypoint.sh" ]
|
ENTRYPOINT [ "/srv/python-teos/entrypoint.sh" ]
|
||||||
|
|
||||||
|
|||||||
@@ -4,14 +4,6 @@
|
|||||||
|
|
||||||
There are two ways of running `teos`: running it as a module or adding the library to the `PYTHONPATH` env variable.
|
There are two ways of running `teos`: running it as a module or adding the library to the `PYTHONPATH` env variable.
|
||||||
|
|
||||||
## Running `teos` as a docker container
|
|
||||||
`teos` container can be build from Dockerfile attached to the repo. ENV variables are optional, if not set defaults are used.
|
|
||||||
|
|
||||||
git clone https://github.com/talaia-labs/python-teos
|
|
||||||
cd python-teos
|
|
||||||
docker build . -t teos
|
|
||||||
docker run -it -e BTC_RPC_USER=<rpc username> -e BTC_RPC_PASSWD=<rpc password> -e BTC_RPC_HOST=<hostname> -e BTC_RPC_PORT=<port> teos
|
|
||||||
|
|
||||||
## Running `teos` as a Module
|
## Running `teos` as a Module
|
||||||
The **easiest** way to run `teos` is as a module. To do so you need to use `python -m`. From the teos parent directory run:
|
The **easiest** way to run `teos` is as a module. To do so you need to use `python -m`. From the teos parent directory run:
|
||||||
|
|
||||||
|
|||||||
@@ -36,6 +36,14 @@ The configuration includes, amongst others, where your data folder is placed, wh
|
|||||||
To run `teos` you need a set of keys (to sign appointments) stored in your data directory. You can follow [generate keys](#generate-keys) to generate them.
|
To run `teos` you need a set of keys (to sign appointments) stored in your data directory. You can follow [generate keys](#generate-keys) to generate them.
|
||||||
|
|
||||||
|
|
||||||
|
## Running `teos` as a docker container
|
||||||
|
`teos` container can be build from Dockerfile attached to the repo. ENV variables are optional, if not set defaults are used.
|
||||||
|
|
||||||
|
git clone https://github.com/talaia-labs/python-teos
|
||||||
|
cd python-teos
|
||||||
|
docker build . -t teos
|
||||||
|
docker run -it -e BTC_RPC_USER=<rpc username> -e BTC_RPC_PASSWD=<rpc password> -e BTC_RPC_HOST=<hostname> -e BTC_RPC_PORT=<port> teos
|
||||||
|
|
||||||
### Configuration file and command line parameters
|
### Configuration file and command line parameters
|
||||||
|
|
||||||
To change the configuration defaults you can:
|
To change the configuration defaults you can:
|
||||||
|
|||||||
0
entrypoint.sh
Normal file → Executable file
0
entrypoint.sh
Normal file → Executable file
Reference in New Issue
Block a user