Pushing Source Files

During the execution of odo dev, the files of the current directory and its sub-directories are pushed to the container. You can influence which files are pushed with the following methods.

Pushing only specific files

odo uses the dev.odo.push.path related attribute from the devfile's run commands to push only the specified files and folders to the component.

The format of the attribute is "dev.odo.push.path:<local_relative_path>": "<remote_relative_path>". We can mention multiple such attributes in the run command's attributes section.

commands:
  - id: dev-run
    attributes:
      "dev.odo.push.path:target/quarkus-app": "remote-target/quarkus-app"
      "dev.odo.push.path:README.txt": "docs/README.txt"
    exec:
      component: tools
      commandLine: "java -jar remote-target/quarkus-app/quarkus-run.jar -Dquarkus.http.host=0.0.0.0"
      hotReloadCapable: true
      group:
        kind: run
        isDefault: true
      workingDir: $PROJECTS_ROOT
  - id: dev-debug
    attributes:
      "dev.odo.push.path:target/quarkus-app": "remote-target/quarkus-app"
      "dev.odo.push.path:README.txt": "docs/README.txt"
    exec:
      component: tools
      commandLine: "java -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=${DEBUG_PORT},suspend=n -jar remote-target/quarkus-app/quarkus-run.jar -Dquarkus.http.host=0.0.0.0"
      hotReloadCapable: true
      group:
        kind: debug
        isDefault: true
      workingDir: $PROJECTS_ROOT

In the above example the contents of the quarkus-app folder, which is inside the target folder, will be pushed to the remote location of remote-target/quarkus-app and the file README.txt will be pushed to doc/README.txt. The local path is relative to the component's local folder. The remote location is relative to the folder containing the component's source code inside the container.

Ignoring files to push

odo excludes from the push the files present in the .odoignore file, or, if this file does not exist, the files present in the .gitignore file.

By default, odo does not create a .odoignore file and relies on the .gitignore file. Also, during each execution, odo dev adds the .odo entry to the .gitignore file if it is not already present in this file, to avoid an infinite loop on the synchronization, this directory containing a file with the state of the sync.

If you want to use the .odoignore file instead, to have a different set of files ignored for sync and ignored for git, you will need to add the .odo directory to the .odoignore file.