when a file in the deploy folder isn't supported, log and move to the failed to deploy folder

Description

previously, Lucee would simply just process known files, skipping unknown ones

  • move any unsupported files to the failed_to_deploy folder and log it out

  • log out when importing a .CFconfig.json or config.json from the deploy folder

Activity

Pothys - MitrahSoft 28 March 2025 at 10:11

I have tested this with Lucee version 7.0.0.157-SNAPSHOT. It creates a error log for the unsupported file in the deploy folder, and it works fine.

Zac Spitzer 14 March 2025 at 16:01

I manually ported this to 7.0 can you check it again plz?

Zac Spitzer 14 March 2025 at 16:00

Pothys - MitrahSoft 6 March 2025 at 10:28

I have tested this ticket with Lucee version 6.2.1.48-SNAPSHOT. When I tried to add the unsupported file to the deploy folder, it automatically moved the unsupported file to the failed_to_deploy folder and created error logs in the deploy.log file. It works fine now.

Zac Spitzer 5 March 2025 at 14:11

and

in addition, any unsupported files are also moved to the failed-to-deploy folder

Fixed

Details

Assignee

Reporter

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Fix versions

Priority

Created 5 March 2025 at 12:54
Updated 28 March 2025 at 10:11
Resolved 6 March 2025 at 10:29