aboutsummaryrefslogtreecommitdiffstats
path: root/install
Commit message (Collapse)AuthorAgeFilesLines
* unmatched parensHabeas Codice2015-01-231-1/+1
|
* add db update 1131/1132 to database schemaszottel2015-01-232-0/+4
|
* typo in postgres db update, remove redmatrix.nl from directory servers since ↵friendica2015-01-201-1/+1
| | | | it isn't a directory server any more.
* oauth permissions tablefriendica2015-01-193-2/+58
|
* fix update 1131 for postgres databasesHabeas Codice2015-01-181-1/+14
|
* more backend work on poco ratingfriendica2015-01-151-1/+11
|
* fix driver issue for large dbsHabeas Codice2014-11-201-25/+76
| | | | add rudimentary resume
* simple command-line migrator from mysql to postgresHabeas Codice2014-11-172-0/+361
| | | | provided with the WorksForMe(tm) warranty of fitness for a purpose implied or otherwise
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-133-191/+2488
|\ | | | | | | | | | | | | | | | | | | | | | | Conflicts: boot.php include/dba/dba_driver.php include/diaspora.php include/follow.php include/session.php include/zot.php mod/photos.php mod/ping.php
| * add defaults to database tablesfriendica2014-11-092-190/+2467
| |
| * ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-1/+21
| | | | | | | | | | | | | | | | | | | | the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
* | PostgreSQL support initial commitHabeas Codice2014-11-132-0/+1190
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Doco - some clean up to install - keep politics out of it, 80 columnise it andThomas Willingham2014-10-221-63/+63
| | | | whitespace.
* document store writability requirementszottel2014-10-221-2/+3
|
* missing quotefriendica2014-10-141-1/+1
|
* this is the reason Diaspora forum tagging was brokenfriendica2014-10-141-1/+8
|
* install doc double escapes the store/[data] path.friendica2014-10-061-1/+1
|
* +png supportjeroenpraat2014-10-051-1/+1
| | | https://redmatrix.nl/channel/jeroenpraat/?f=&mid=83603d8f0876c040efafce87755fcd252dbe8da4a75d82fdb230519e3c8dcb72@redmatrix.nl
* store diaspora meta info in the item table. It has to go there or it will ↵friendica2014-09-032-1/+11
| | | | kill us with complex joins. We can phase out the sign table once this all checks out.
* update nl + Friendica>RedMatrix in two text filesJeroen2014-08-301-2/+2
|
* Ability to close comments at a certain date/time - needed for loom.io ↵friendica2014-08-282-1/+12
| | | | emulation (and many other uses)
* mind numbing drudgery continued...friendica2014-08-272-1/+13
|
* place to store multiple choice and select items for extensible profilesfriendica2014-08-262-1/+11
|
* more hard workfriendica2014-08-262-1/+59
|
* We really can't do this without a hubloc. I was hoping we could, but ↵friendica2014-08-222-1/+15
| | | | notifier is setup to take hublocs, not xchans.
* some more work on realmsfriendica2014-08-171-1/+9
|
* provide backend storage and declaration of directory realmfriendica2014-08-162-2/+13
|
* item table upgrade for storing post visibilityfriendica2014-08-062-1/+12
|
* db tables for extensible profile fieldsfriendica2014-08-022-1/+51
|
* block channel removal for 48 hours after changing the account password, ↵friendica2014-07-292-2/+13
| | | | since the password is required to remove a channel. Somebody looking at an open session on somebody else's computer can simply change the password and then proceed to maliciously remove the channel. This change gives the owner 2 days to discover that something is wrong and recover his/her password and potentially save their channel from getting erased by the vandal. This is most likely to happen if a relationship has gone bad, or something incriminating was found in your private messages when you left your computer briefly unattended.
* provide a specific permission for liking profiles (reuse the obsolete ↵friendica2014-07-172-4/+14
| | | | bookmark permission), also remove the unused 'unconnected contacts' view for now.
* provide os_mkdir to workaround permission issues with php mkdirfriendica2014-07-161-2/+2
|
* move smarty compiled files to store/[data]/smarty3 - which puts all ↵friendica2014-07-102-8/+11
| | | | writeable areas of the server except the config file and logs under the "store" directory. We'll do logs at a future time.
* finish implementing email verification. Currently it only applies if ↵friendica2014-07-091-1/+9
| | | | REGISTER_OPEN is in effect.
* ability to like thingsfriendica2014-06-232-2/+12
|
* honour the admin censored flag in the directory, and some slow progress on ↵friendica2014-06-222-2/+14
| | | | extended likes
* likes table for liking things besides posts and commentsfriendica2014-06-222-1/+39
|
* issue #477friendica2014-06-011-1/+5
|
* implement 'requires' on personal appsfriendica2014-05-222-1/+9
|
* try to recover from bad updatefriendica2014-05-201-1/+13
|
* more app backend workfriendica2014-05-192-3/+10
|
* support commerical appsfriendica2014-05-182-2/+17
|
* app DB structurefriendica2014-05-172-1/+48
|
* we seem to have lost any install text mentioning that subdirs and alternate ↵friendica2014-04-121-0/+3
| | | | ports aren't supported
* Don't explicitly deny our strongest features existence.Thomas Willingham2014-04-111-3/+0
|
* Added some more details about why browser-valid SSL certificates must besasiflo2014-04-101-1/+17
| | | | | | | used when SSL is used at all. It is now in the check failure message in the installation routine, the installation readme and in the documentation pages.
* use parent_mid in the parent query for enotify instead of of the parent id. ↵friendica2014-04-062-2/+9
| | | | This should fix the issue with encrypted content in the notification messages (for locally posted replies). The fix was a bit harder than anticipated because we store the parent id as an int in the notify table so this had to be modified to char storage as well.
* more efficient public feed fetchingfriendica2014-04-022-2/+12
|
* finish up the source route storage so we can prevent messages from flowing ↵friendica2014-03-312-12/+20
| | | | upstream in complicated delivery chains
* This should be a slight improvement in setting ciphers - we'll punt on ↵friendica2014-03-251-2/+9
| | | | RedHat but open up the list just for openssl distros which seem to have all the problems at the moment.