You already have a docker image built and pushed to your registry.
Docker Image
in the Service Deployment form.Your code is in a git repository and the Git repository is integrated to TrueFoundry. You have written a dockerfile to build your code
Dockerfile (I already have DockerFile)
in the Build section."./"
, however, if you have multiple services in the same repo, you can specify the path to the directory containing the service you want to deploy - for e.g. "my-service/"
.Path to Build Context
. For e.g. if the Dockerfile is present in the my-service
directory, and you have provided the build context as "my-service/"
, then the path to the Dockerfile is "./Dockerfile"
. However, if the Path to Build Context
is "./"
, then the path to the Dockerfile should be "./my-service/Dockerfile"
.Your code is in a git repository and the git repository is integrated with TrueFoundry. You don't have a Dockerfile in the Git repository
Python Code (I don't have Dockerfile)
in the Build section."./"
, however, if you have multiple services in the same repo, you can specify the path to the directory containing the service you want to deploy - for e.g. "my-service/"
.Path to Build Context
. For e.g. if the requirements.txt is present in the my-service
directory, and you have provided the build context as "my-service/"
, then the path to the requirements.txt is "./requirements.txt"
. However, if the Path to Build Context
is "./"
, then the path to the requirements.txt should be "./my-service/requirements.txt"
.Your code is only on your laptop and you want to deploy it
Code From Laptop
in the Service Deployment form.Dockerfile (I already have DockerFile)
, else choose the option Python Code (I don't have Dockerfile)
. The second option will work if you have Python code locally and a requriements.txt file containing the dependencies. The description of the fields can be found in the previous sections.