-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
[2.2.7] Logs path is absolute? #1572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It is. use __dirname in your config to construct an absolute path to a folder in your Parse Server project. |
Not fixed, I set the |
Where do you deploy? What's the path to you logs folder (configuration)? What's the behaviour locally? |
I'm using Parse with expressjs on a virtual machine running the latest Ubuntu LTS. The logs path is passed through the constructor of ParseServer. The configuration is attached, personal data is blacked out. As I said before the logsFolder is ignored and new logs are created at /logs (file system root). |
I'll have a look |
Can you reopen this issue then? |
Maybe the logs folder is created by foreverjs. I start my server by:
|
Nope, here is the error with my instance running as www-data
|
I'm using the latest versione of Parse-Server and I keep getting this error:
It seems that the logs path is absolute and not relative to the project, and the logs are created in the absolute path /logs/. My Parse instance is running through foreverjs, maybe this helps?
The text was updated successfully, but these errors were encountered: