![]() ![]() Web Distributed Authoring and Versioning (WebDAV) First up, we will look at the WebDav protocol and using it as an alternative for handling live code updates to a running application. In this post we will start looking at how other more standard protocols might be used with OpenShift to handle file transfer. In the case of a different filesystem layout, you would need to first download a copy of the directories you want to work on from the container to your local filesystem, then set up the file synchronisation using that copy as the source.Īs much as oc rsync is useful for transferring files in and out of containers, it also is a mechanism specific to OpenShift and doesn't have support in third-party client tools users may be familiar with, for uploading and downloading files to or from other machines. One scenario where this may not work is where the building of the application image reorganised the original source code so that it didn't match the layout of the original in the local code repository, or a compilation process was performed as part of the build process. This was achieved only by making changes on your local computer, without having to re-build the application image, or manually upload changes each time. If the container was running a web server, or other web application which was able to automatically detect the updated file and use it, you could use this mechanism to perform live code updates in more or less real time. This worked by virtue of the oc client monitoring the local filesystem directory for file changes and when they were detected copying the changed files to the running container, replacing the version of the file in the container. In a recent blog post we covered how you can use the oc rsync -watch command to perform live synchronisation of code changes between a local filesystem and a container. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |