Skip to content

Commit 93073ca

Browse files
author
Teodor Kostadinov
authored
Update README.md (#3)
1 parent ce3ad33 commit 93073ca

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ We have the following templates available:
100100
#### Step 4 - Run Docker Compose
101101

102102
```shell
103-
docker-compose -f docker-compose.<template>.yml -d
103+
docker-compose -f docker-compose.<template>.yml up -d
104104
```
105105

106106
You can monitor the status of the container(s) by using `docker-compose ps` command.
@@ -157,4 +157,4 @@ This repository was heavily inspired by what was already done [here](https://git
157157
## Future Improvements
158158

159159
- [ ] Add a Github workflow to automatically build and publish new versions
160-
- [ ] Add a self-termiantion logic that would automatically terminate the Docker Host instance if running in Azure or AWS. This would help in scenarios where the self-hosted integration runtime is deployed via Azure Functions/Lambda only for a job that is needed and then automatically terminated when no jobs are pending for execution. There isn't any better way of using the Docker image natively in Azure/AWS with the benefit of VNET/VPC integration and keeping the costs low by terminating the instance after every run.
160+
- [ ] Add a self-termiantion logic that would automatically terminate the Docker Host instance if running in Azure or AWS. This would help in scenarios where the self-hosted integration runtime is deployed via Azure Functions/Lambda only for a job that is needed and then automatically terminated when no jobs are pending for execution. There isn't any better way of using the Docker image natively in Azure/AWS with the benefit of VNET/VPC integration and keeping the costs low by terminating the instance after every run.

0 commit comments

Comments
 (0)