You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update_Docs scans the files in the lib folder and runs perldoc on the files. The resulting documentation files are stored in a user defined folder and accessible from the mh web interface at http://localhost/docs. Update_Docs can be configured to run on a specific schedule.
However, the current code in Update_Docs will not scan subdirectories in the lib folder, namely the Insteon directory. But we need to avoid the extensive non-MH libraries that are stored there in the site***** directories.
A couple questions:
Is this still a good feature? [I think it is nifty, but may not be needed as we could just push updated docs to the stable branch as well.]
If kept, how should subdirectories be handled? Option 1. Hard code Insteon as a subdirectory? Option 2. Hard code any directory starting with site as an excluded directory?
The text was updated successfully, but these errors were encountered:
Update_Docs scans the files in the lib folder and runs perldoc on the files. The resulting documentation files are stored in a user defined folder and accessible from the mh web interface at http://localhost/docs. Update_Docs can be configured to run on a specific schedule.
However, the current code in Update_Docs will not scan subdirectories in the lib folder, namely the Insteon directory. But we need to avoid the extensive non-MH libraries that are stored there in the site***** directories.
A couple questions:
The text was updated successfully, but these errors were encountered: