Closed ayodeji closed 2 months ago
Add ability to log errors in a file. Make sure its not too verbose. Add the Error logging to your catch. and Specify the file name it will log to.
Ok. I will work on that.
Add ability to log errors in a file. Make sure its not too verbose. Add the Error logging to your catch. and Specify the file name it will log to.
So I have added the error log file. But I have an issue with directory. It seems not to write to the file if the log file is placed outside the public folder. Still working on that.
What's wrong with putting it in public?
On Wed, Sep 4, 2024, 7:26 PM Samuel Oladipo @.***> wrote:
Add ability to log errors in a file. Make sure its not too verbose. Add the Error logging to your catch. and Specify the file name it will log to.
So I have added the error log file. But I have an issue with directory. It seems not to write to the file if the log file is placed outside the public folder. Still working on that.
— Reply to this email directly, view it on GitHub https://github.com/dumelacorp/dumela-recruit/issues/4#issuecomment-2330316076, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKE2XJFH3TYAOQNVRKO3TDZU6JI7AVCNFSM6AAAAABNSHFSOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGMYTMMBXGY . You are receiving this because you authored the thread.Message ID: @.***>
What's wrong with putting it in public? … On Wed, Sep 4, 2024, 7:26 PM Samuel Oladipo @.> wrote: Add ability to log errors in a file. Make sure its not too verbose. Add the Error logging to your catch. and Specify the file name it will log to. So I have added the error log file. But I have an issue with directory. It seems not to write to the file if the log file is placed outside the public folder. Still working on that. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKE2XJFH3TYAOQNVRKO3TDZU6JI7AVCNFSM6AAAAABNSHFSOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGMYTMMBXGY . You are receiving this because you authored the thread.Message ID: @.>
What's wrong with putting it in public? … On Wed, Sep 4, 2024, 7:26 PM Samuel Oladipo @.> wrote: Add ability to log errors in a file. Make sure its not too verbose. Add the Error logging to your catch. and Specify the file name it will log to. So I have added the error log file. But I have an issue with directory. It seems not to write to the file if the log file is placed outside the public folder. Still working on that. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKE2XJFH3TYAOQNVRKO3TDZU6JI7AVCNFSM6AAAAABNSHFSOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGMYTMMBXGY . You are receiving this because you authored the thread.Message ID: @.>
There's nothing wrong with that, I just want it to be at the root of the project so other component outside the public folder can easily reference it.
I have pushed the error logs file
Add ability to log errors in a file. Make sure its not too verbose. Add the Error logging to your catch. and Specify the file name it will log to.