streams/view/en/htconfig.tpl

170 lines
7.2 KiB
Smarty
Raw Normal View History

2010-08-16 04:49:29 +00:00
<?php
PostgreSQL support initial commit There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
// Set the following for your database installation
2010-08-16 04:49:29 +00:00
// Copy or rename this file to .htconfig.php
2013-05-16 04:21:44 +00:00
$db_host = '{{$dbhost}}';
$db_port = '{{$dbport}}';
$db_user = '{{$dbuser}}';
$db_pass = '{{$dbpass}}';
$db_data = '{{$dbdata}}';
2024-05-12 00:03:37 +00:00
$db_type = '{{$dbtype}}'; // Integer. 0 or unset for mysql, 1 for postgres
$db_vrsn = '{{$dbvrsn}}'; // Required for doctrine
2010-08-16 04:49:29 +00:00
2013-02-10 08:13:34 +00:00
/*
* Notice: Many of the following settings will be available in the admin panel
* after a successful site install. Once they are set in the admin panel, they
* are stored in the DB - and the DB setting will over-ride any corresponding
* setting in this file
*
* The command-line tool util/config is able to query and set the DB items
* directly if for some reason the admin panel is not available and a system
* setting requires modification.
*
*/
2010-08-16 04:49:29 +00:00
// Choose a legal default timezone. If you are unsure, use "America/Los_Angeles".
// It can be changed later and only applies to timestamps for anonymous viewers.
App::$config['system']['timezone'] = '{{$timezone}}';
2010-08-16 04:49:29 +00:00
2016-10-30 19:34:00 +00:00
// What is your site url? DO NOT ADD A TRAILING SLASH!
2010-08-16 04:49:29 +00:00
2016-03-31 23:06:03 +00:00
App::$config['system']['baseurl'] = '{{$siteurl}}';
2022-07-19 21:57:55 +00:00
App::$config['system']['sitename'] = '{{$sitename}}';
2016-03-31 23:06:03 +00:00
App::$config['system']['location_hash'] = '{{$site_id}}';
2010-08-16 04:49:29 +00:00
// These lines set additional security headers to be sent with all responses
// You may wish to set transport_security_header to 0 if your server already sends
// this header. content_security_policy may need to be disabled if you wish to
// run the piwik analytics plugin or include other offsite resources on a page
2016-03-31 23:06:03 +00:00
App::$config['system']['transport_security_header'] = 1;
App::$config['system']['content_security_policy'] = 1;
App::$config['system']['ssl_cookie_protection'] = 1;
2010-08-16 04:49:29 +00:00
// Your choices are REGISTER_OPEN, REGISTER_APPROVE, or REGISTER_CLOSED.
// Be certain to create your own personal account before setting
// REGISTER_CLOSED. 'register_text' (if set) will be displayed prominently on
// the registration page. REGISTER_APPROVE requires you set 'admin_email'
// to the email address of an already registered person who can authorise
// and/or approve/deny the request.
2024-06-14 21:55:48 +00:00
App::$config['system']['register_policy'] = REGISTER_APPROVE;
2016-03-31 23:06:03 +00:00
App::$config['system']['register_text'] = '';
App::$config['system']['admin_email'] = '{{$adminmail}}';
2010-08-16 04:49:29 +00:00
// Recommend you leave this set to 1. Set to 0 to let people register without
// proving they own the email address they register with.
2016-03-31 23:06:03 +00:00
App::$config['system']['verify_email'] = 1;
// Site access restrictions. By default we will create private sites.
// Your choices are ACCESS_PRIVATE, ACCESS_PAID, ACCESS_TIERED, and ACCESS_FREE.
// If you leave REGISTER_OPEN above, anybody may register on your
// site, however your site will not be listed anywhere as an open
// registration hub. We will use the system access policy (below)
// to determine whether or not to list your site in the directory
// as an open hub where anybody may create accounts. Your choice of
// paid, tiered, or free determines how these listings will be presented.
2016-03-31 23:06:03 +00:00
App::$config['system']['access_policy'] = ACCESS_PRIVATE;
// This software has a focus on online safety and user privacy. The default
// channel configuration is a restricted role where all posts are private to
// your connections and one needs to change the audience manually in order to
// create a public post ('social_restricted'). You might want to instead
// change this to post publicly by default, and require a manual change to
// restrict the audience to only your connections. To do that, change this
// to 'social'.
App::$config['system']['default_permissions_role'] = 'social_restricted';
// This setting affects the quality of the site directory and friend suggestions.
// It controls how many "friends of friends" to import into your site from connections
// that are made on this site. Every digit increase can have a dramatic effect on disk
// and database use depending on the size of your site and the number of connections that
// have been made. If set to 100 or more and you have more than a dozen local accounts,
// each with a modest number of connections, your directory could ultimately discover most
// of the known fediverse, or tens of millions of entries.
// The default setting of 10 will provide you with a very well connected fediverse instance
// with an interesting and well-rounded directory, and provide good quality friend suggestions.
// You might wish to reduce this or change it to 0 if resource use is a concern.
// The quality of your directory and friend suggestions will decrease accordingly. If you
// raise it, it is recommend that you raise it incrementally and not make large or sudden
// jumps, as this could quickly mushroom into millions or tens of millions of new
// directory records.
App::$config['system']['max_imported_follow'] = 10;
// If you operate a public site, you might wish that people are directed
// to a "sellpage" where you can describe for features or policies or service plans in depth.
// This must be an absolute URL beginning with http:// or https:// .
2016-03-31 23:06:03 +00:00
App::$config['system']['sellpage'] = '';
// Maximum size of an imported message, 0 is unlimited
2010-08-16 04:49:29 +00:00
2016-03-31 23:06:03 +00:00
App::$config['system']['max_import_size'] = 200000;
2010-08-16 04:49:29 +00:00
// Location of PHP command line processor
2016-03-31 23:06:03 +00:00
App::$config['system']['php_path'] = '{{$phpath}}';
// Configure how we communicate with directory servers.
2023-12-23 21:02:43 +00:00
// Deprecated. Please do not change.
2016-03-31 23:06:03 +00:00
App::$config['system']['directory_mode'] = DIRECTORY_MODE_NORMAL;
// default system theme
2023-10-16 19:32:06 +00:00
App::$config['system']['theme'] = 'fresh';
2023-12-23 21:02:43 +00:00
// Allow local test environments with unverified SSL certs using Lando
App::$config['system']['ssl_exceptions'] = 'lndo.site';
2023-12-23 21:02:43 +00:00
// Mail configuration
// By default, uses local sendmail service
// Only change these settings if you require SMTP transport
// App::$config['phpmailer']['mailer'] = 'smtp';
// App::$config['phpmailer']['host'] = 'example.com';
2023-12-23 21:02:43 +00:00
// Leave this line commented if using SSL or STARTTLS and set the port in the next sections
// App::$config['phpmailer']['port'] = 25; // (or 587 or 465 if using ssl)
2023-12-23 21:02:43 +00:00
// If using smtp authentication:
// App::$config['phpmailer']['smtpauth'] = 1;
// App::$config['phpmailer']['uername'] = 'your_username';
// App::$config['phpmailer']['password'] = 'your_secret_password';
2023-12-23 21:02:43 +00:00
// If using starttls:
// App::$config['phpmailer']['smtpsecure'] = 'tls';
// App::$config['phpmailer']['port'] = 587;
2023-12-23 21:02:43 +00:00
// If using ssl:
// App::$config['phpmailer']['smtpsecure'] = 'ssl';
// App::$config['phpmailer']['port'] = 465;
2023-12-23 21:02:43 +00:00
// If the server has a self-signed cert:
// App::$config['phpmailer']['noverify'] = 1;
2023-12-23 21:02:43 +00:00
// For debugging
// App::$config['phpmailer']['smtpdebug'] = 2; // valid values are 0-4
2023-12-23 21:02:43 +00:00
// These settings should work for 99% of use cases
// If you encounter any issues, please see https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
// If you need to extend these configuration options, please submit a pull request with your changes.
// PHP error logging setup
// Before doing this ensure that the webserver has permission
2016-10-30 19:34:00 +00:00
// to create and write to php.out in the top level web directory,
// or change the name (below) to a file/path where this is allowed.
2021-03-09 01:51:41 +00:00
ini_set('display_errors', '0');
// Uncomment the following lines to turn on PHP error logging.
//error_reporting(E_ERROR | E_PARSE );
//ini_set('error_log','php.out');
//ini_set('log_errors','1');