Some fixes to allow running echo sql app in one go

[hp77-creator]

Changes:

1. Changed network name to keploy-network since that is what keploy creates when we install keploy
2. Changed host name to postgres from postgresDB because docker uses service name

There will be some changes that will need to be added in docs as well to ensure that user is able to run this app in one-go

Some suggestions like adding --rm command in keploy record ... command so that user doesn't see the error that container is still up/or change the app name.
Open to suggestions. For now this also seemed good so sending a PR for the same.

[Sarthak160]

Hey @hp77-creator, Since user can use its custom network as well , keploy will automatically use that network instead of using keploy-network specifically . In the alias as well user is free to change the network name , so here keploy-network seems to be good for simplicity . But reason to use some random network name was to showcase automatic custom network interception feature of keploy.

[Sarthak160]

So i think, in this you can rename this to custom-network instead of baba and add in comments that if user doesnt provide any network by default .

[hp77-creator]

But reason to use some random network name was to showcase automatic custom network interception feature of keploy.

I see but on the docs that I was following, keploy record was passing --network flag as keploy-network, Either one of the two should be changed imo. I felt changing network is better, given docker might change name of the container and based on the network if more containers are spinned up.

So i think, in this you can rename this to custom-network instead of baba and add in comments that if user doesnt provide any network by default .

I didn't get this. Do you want me to rename keploy-network to custom-network? Doing that will work given that we are expecting a new user to run following command: keploy record -c "docker run -p 8082:8082 --name echoSqlApp --network keploy-network echo-app:1.0"

[Sarthak160]

But reason to use some random network name was to showcase automatic custom network interception feature of keploy.

I see but on the docs that I was following, keploy record was passing --network flag as keploy-network, Either one of the two should be changed imo. I felt changing network is better, given docker might change name of the container and based on the network if more containers are spinned up.

So i think, in this you can rename this to custom-network instead of baba and add in comments that if user doesnt provide any network by default .

I didn't get this. Do you want me to rename keploy-network to custom-network? Doing that will work given that we are expecting a new user to run following command: keploy record -c "docker run -p 8082:8082 --name echoSqlApp --network keploy-network echo-app:1.0"

yea, that's true that if container name changes we have to change the host name but since service name is mapped we can consider using that. And at the docs it has been mention to run with docker run command. But above I was talking about docker-compose file only in case of docker compose even if you don't provide any network it will still work. Because keploy creates a kdocker-compose file where it automatically creates a keploy-network for that user container.