The publish files are generated when publish scripts are run in PageSeeder. They are temporary files, don’t need to be backed up and are cleared regularly by PageSeeder processes.
They are not to be modified directly on the file system, but if disk space is an issue, they can be safely cleared when the PageSeeder server is stopped.
The session files are the output files from the publish scripts.
They are located under a sub-folder named after the session ID used to run the script and are accessed by PageSeeder when presenting the output after the publish script is completed (for example, a report or a Zip archive document to download).
Once the script is completed, the output file isn’t needed so it can in theory be removed safely, but that is not needed as a PageSeeder process is checking once a day and removing any session file/folder that was not created in the last 12 hours.
The working folder contains all the temporary files used by the publish scripts (export, process, publish or upload). Each running script has its own working folder based on the object it is running on: a group, a document or folder, an uploaded document:
- For a group:
- For a document/folder:
/[host]/[path]/[ps-uri or ps-folder]
- For an uploaded document:
These are valid examples:
/ps.pageseeder.com/project1-group1/ps-group /ps.pageseeder.com/ps/project1/group1/documents/mydoc1.psml/ps-uri /ps.pageseeder.com/ps/project1/group1/documents/ps-folder /ps.pageseeder.com/ps/project1/group1/documents/newdoc.docx/ps-upload
These working folders are always emptied before the corresponding script is run to make sure that script uses the correct data.
These files can be useful for debugging purposes and, therefore, have a longer lifespan than session files – a PageSeeder process is checking once a day and removing any working file/folder that was not created in the last three days.
They can also safely be removed manually once the publish script is completed.