@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.) hq.recaptime.dev/wiki/Phorge
phorge phabricator
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Fixing of the typos

Test Plan: doitlive

Reviewers: epriestley, chad

Reviewed By: epriestley, chad

Subscribers: cspeckmim, Korvin

Differential Revision: https://secure.phabricator.com/D17727

+17 -17
+12 -12
src/docs/contributor/database.diviner
··· 10 10 Phabricator uses MySQL or another MySQL-compatible database (like MariaDB 11 11 or Amazon RDS). 12 12 13 - Phabricator the InnoDB table engine. The only exception is the 13 + Phabricator uses the InnoDB table engine. The only exception is the 14 14 `search_documentfield` table which uses MyISAM because MySQL doesn't support 15 15 fulltext search in InnoDB (recent versions do, but we haven't added support 16 16 yet). ··· 102 102 Primary Keys 103 103 ============ 104 104 105 - Most tables have auto-increment column named `id`. Adding an ID column is 105 + Most tables have an auto-increment column named `id`. Adding an ID column is 106 106 appropriate for most tables (even tables that have another natural unique key), 107 107 as it improves consistency and makes it easier to perform generic operations 108 108 on objects. ··· 134 134 PHIDs 135 135 ===== 136 136 137 - Each globally referencable object in Phabricator has its associated PHID 137 + Each globally referencable object in Phabricator has an associated PHID 138 138 ("Phabricator ID") which serves as a global identifier, similar to a GUID. 139 139 We use PHIDs for referencing data in different databases. 140 140 141 - We use both autoincrementing IDs and global PHIDs because each is useful in 142 - different contexts. Autoincrementing IDs are meaningfully ordered and allow 141 + We use both auto-incrementing IDs and global PHIDs because each is useful in 142 + different contexts. Auto-incrementing IDs are meaningfully ordered and allow 143 143 us to construct short, human-readable object names (like `D2258`) and URIs. 144 144 Global PHIDs allow us to represent relationships between different types of 145 145 objects in a homogeneous way. ··· 154 154 ============ 155 155 156 156 Transactional code should be written using transactions. Example of such code is 157 - inserting multiple records where one doesn't make sense without the other or 157 + inserting multiple records where one doesn't make sense without the other, or 158 158 selecting data later used for update. See chapter in @{class:LiskDAO}. 159 159 160 160 Advanced Features ··· 195 195 196 196 | Variable | Meaning | Notes | 197 197 |---|---|---| 198 - | {$NAMESPACE} | Storage Namespace | Defaults to `phabricator` | 199 - | {$CHARSET} | Default Charset | Mostly used to specify table charset | 200 - | {$COLLATE_TEXT} | Text Collation | For most text (case-sensitive) | 201 - | {$COLLATE_SORT} | Sort Collation | For sortable text (case-insensitive) | 202 - | {$CHARSET_FULLTEXT} | Fulltext Charset | Specify explicitly for fulltext | 203 - | {$COLLATE_FULLTEXT} | Fulltext Collate | Specify explicitly for fulltext | 198 + | `{$NAMESPACE}` | Storage Namespace | Defaults to `phabricator` | 199 + | `{$CHARSET}` | Default Charset | Mostly used to specify table charset | 200 + | `{$COLLATE_TEXT}` | Text Collation | For most text (case-sensitive) | 201 + | `{$COLLATE_SORT}` | Sort Collation | For sortable text (case-insensitive) | 202 + | `{$CHARSET_FULLTEXT}` | Fulltext Charset | Specify explicitly for fulltext | 203 + | `{$COLLATE_FULLTEXT}` | Fulltext Collate | Specify explicitly for fulltext | 204 204 205 205 206 206 **Test your patch**. Run `bin/storage upgrade` to test your patch.
+3 -3
src/docs/flavor/project_history.diviner
··· 52 52 I joined the new Dev Tools team around February 2010 and took over Diffcamp. I 53 53 renamed it to Differential, moved it to a new Alite-based infrastructure with 54 54 Javelin, and started making it somewhat less terrible. I eventually wrote 55 - Diffusion and build Herald to replace a very difficult-to-use predecessor. These 55 + Diffusion and built Herald to replace a very difficult-to-use predecessor. These 56 56 tools were less negatively received than the older versions. By December 2010 I 57 57 started open sourcing them; Haste became //Celerity// and Alite became 58 58 //Aphront//. I wrote Maniphest to track open issues with the project in January 59 - or February and we open sourced Phabricator in late April, shortly after I left 60 - Facebook. 59 + or February, left Facebook in April, and shortly after, we open sourced 60 + Phabricator.
+2 -2
src/docs/flavor/things_you_should_do_now.diviner
··· 134 134 135 135 Hopefully, whatever language you're writing in has good query libraries that 136 136 can handle escaping for you. If so, use them. If you're using PHP and don't have 137 - a solution in place yet, the Phabricator implementation of qsprintf() is similar 138 - to Facebook's system and was successful there. 137 + a solution in place yet, the Phabricator implementation of `qsprintf()` is 138 + similar to Facebook's system and was successful there.