Introduction / FirstSpirit ServerManager / Schedule entry planning / Project-based actions / Execute deployment / In a local file system
Deployment in a local file system
This action is used to deploy a project in a local file system and therefore does not require many settings.
Name: the name of the action displayed in the schedule overview, schedule management and action templates.
Deployment options
Complete adjustment (for full generation only)
This method is used to create a data inventory identical to the generation data inventory on the web server. This means that files that are no longer present on the development server are also deleted on the web server, new files are copied, and old files already present on the server are overwritten by the new ones.
Adjustment (without deleting)
This deployment option is similar to the complete adjustment, but differs in the fact that no files are deleted from the web server, even if they are no longer present on the development server.
Deployment
Path into local file system: here the user can specify in which local directory deployment is to take place. The path can be specified as absolute or relative (to the server's working directory). The path information also activates the OK and Test configuration buttons.
Attach date to directory name: if this option is selected, the current document is attached to the path specified above.
Clicking on the Test configuration button, which is activated by entering information in the “Path into local file system” field, allows the user to test the specified configuration. The server will first verify that all the necessary parameters have been entered. Then the server will attempt to create a folder and write a file to it in the specified “Path into local file system”. It will also attempt to rename the file and then delete all of the data created.
If the test is successful, this message appears: “Test successfully completed”
This message appears if it fails: “The test has failed”
Clicking on the Details button opens a dialog with the corresponding log file showing the errors.
For more information on the "Secure media" concept, see the "Documentation for the FirstSpirit security module".