4. If you know in advance that it will be impossible for the web server to
write or create files in the config/ subfolder, create an empty file called
4. If you know in advance that it will be impossible for the web server to
write or create files in the config/ subfolder, create an empty file called
5. Visit your website with a web browser and follow the instructions. Please
note any error messages and correct these before continuing.
5. Visit your website with a web browser and follow the instructions. Please
note any error messages and correct these before continuing.
- - "config/local.ini.php" exists
- If not, edit local-sample.ini.php and change system settings. Rename
-to local.ini.php
+ - "config/local.config.php" exists
+ If not, edit local-sample.config.php and change system settings. Rename
+to local.config.php
Registration errors should all be recoverable automatically.
If you get any *critical* failure at this point, it generally indicates the
database was not installed correctly. You might wish to move/rename
Registration errors should all be recoverable automatically.
If you get any *critical* failure at this point, it generally indicates the
database was not installed correctly. You might wish to move/rename
tables, so that you can start fresh.
****************************************************************************
tables, so that you can start fresh.
****************************************************************************
database or whatever you can think of. So once the installation of your
Friendica node is done, you should make yoursef a backup plan.
database or whatever you can think of. So once the installation of your
Friendica node is done, you should make yoursef a backup plan.
As it stores all your data, you should also have a recent dump of your
Friendica database at hand, should you have to recover your node.
As it stores all your data, you should also have a recent dump of your
Friendica database at hand, should you have to recover your node.
due to permissions issues:
#####################################################################
create an empty file with that name and give it world-write permission.
For Linux:
due to permissions issues:
#####################################################################
create an empty file with that name and give it world-write permission.
For Linux:
Retry the installation. As soon as the database has been created,
******* this is important *********
Retry the installation. As soon as the database has been created,
******* this is important *********
#####################################################################
- Some configurations with "suhosin" security are configured without
#####################################################################
- Some configurations with "suhosin" security are configured without
proc_open. These scripts themselves also use proc_open and fail, because they
are NOT called with -d suhosin.executor.func.blacklist=none.
proc_open. These scripts themselves also use proc_open and fail, because they
are NOT called with -d suhosin.executor.func.blacklist=none.
-[config]
-; Location of PHP command line processor
-php_path = "/usr/bin/php -d suhosin.executor.func.blacklist=none -d suhosin.executor.eval.blacklist=none"
+ 'config' => [
+ //Location of PHP command line processor
+ 'php_path' => '/usr/bin/php -d suhosin.executor.func.blacklist=none -d suhosin.executor.eval.blacklist=none',
+ ],
This is obvious as soon as you notice that the friendica-cron uses proc_open to
execute php-scripts that also use proc_open, but it took me quite some time to
This is obvious as soon as you notice that the friendica-cron uses proc_open to
execute php-scripts that also use proc_open, but it took me quite some time to