Closed ericgaspar closed 1 year ago
!testme
!testme
(NB : i don't remember the full story about using Git etc ... Personally I'm in favor of the classic behavior of checking-out a proper tag (implemented in this PR) and not just git pull the latest commit, but there may be reasons to do so ...)
During my tests I got this error in the admin interface:
Error trying to open log/friendica.log log file.
Check to see if file log/friendica.log exist and is readable.
is this log file created at install in the app folder /var/www/friendica/log/friendica.log
or is /var/log/friendica.log
path expected?
!testme
During my tests I got this error in the admin interface:
Error trying to open log/friendica.log log file. Check to see if file log/friendica.log exist and is readable.
is this log file created at install in the app folder
/var/www/friendica/log/friendica.log
or is/var/log/friendica.log
path expected?
It is created at runtime in $install_dir
by the logger based on the application configuration. The default relative path for the log file is log/friendica.log
.
@ericgaspar What was the issue with PHP 8.0 packages?
@ericgaspar What was the issue with PHP 8.0 packages?
It was requirements not match or something like that (is PHP8.0 not yet supported?)
We have reports of Friendica admins successfully using even PHP 8.2, so I'm surprised it didn't work. We still support PHP 7.4 but we strongly recommend using at least PHP 8.0.
let me open a PHP8.0 branch
ok, fixed by adding the PHP8.0-curl
library
!testme
we still have a problem with the daemon not starting...
I'm sorry, I'm not familiar with systemd service configuration 😕
!testme
resources.sources
inmanifest.toml