Introduction to Filesystem Operations Demo (v4.1)

A simple project to download a zip file from the internet, and perform a number of filesystem operations on it.

Project overview.

Here is a summary of what this project wil achieve.

This project is designed to download a zip file from the MidVision support site to a Linux /tmp directory and perform a number of operations on it, demonstrating some of the RapidDeploy filesystem plugin tasks.

One target environment is configured in the project to perform the job on the localhost (RapidDeploy server). 

This project is configured for use on Linux/Mac only.

What is preconfigured and demonstrated.

The project demonstrates the following configurations:
  • Target server for Linux using localhost
  • Use of the Remote agent plugin
  • Windows batch file or shell script depending on target 
  • Move , Copy DiskSpaceCheck Wget , DirectoryWriteCheck CheckFileZipChmod, SearchReplace, XPathReplace, MkDir, Delete tasks

How to use this project.

  1. Download the project to your desktop by clicking on one of the links. The file will be saved as FileSystem-Demo-41.zip
  2. Log into your RapidDeploy instance as mvadmin.
  3. Navigate to Resources-> Projects.
  4. In the top right hand corner click on the Upload Project button.
  5. Select the zip file you downloaded in step 1.
  6. You are guided through a project import wizard. The important thing to check and change (if necessary) here is the path to the project storage directory. Ideally this should be under the projects directory in your RapidDeploy installation. E.g.
    1. /usr/midvision/projects/Filesystem-Demo-41
  7. More information on this projects orchestration tasks can be found on the Explore the Filesystem Demo Project page.
  8. Once the project is imported, you'll need to create a package to deploy.
    • Firstly, navigate to Resources-> Projects and edit the project (pencil icon on the tool menu). 
    • Navigate to the Packages tab and click the Create Package  button. A new package is created with a version number. This is the package you'll deploy later, containing all the environment definitions, actions and paylod (scripts) to allow the jobs to be run on all defined servers. 
    • Over time, as you update the configuration or payload (script), you'll create more packages, which are a versioned snapshot of the configuration and payload at the time they are created. 
  9. Now you can run a new job to the environment of your choice. 
    • Navigate to Jobs-> New Job
    • Double click on the 'Empty' project job box, and select the project you created earlier from the droplist. 
    • Select the Target  you want to deploy from the droplist. 
    • Select the  Version  (package version) you want to deploy from the droplist. 
    • Since there is only one package, it is preselected. The latest package will always be preselected by default. 
    • Click on the  Run  button in the bottom right corner, enter a comment for this run and click and click Yes 
    • The deployment is started. Click on the Running Jobs icon in the top right corner and you see the tasks executed and job log in real time.

Further Reading

The following links will help you gain a deeper understanding of the tasks used in this project: