@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.

Docs: Replace your.install.com with phorge.example.com

Summary:
Numerous other docs also use example.com, and that domain is intentionally meant for such purposes.
Makes grep results more complete for the next project renaming.

Test Plan: None.

Reviewers: O1 Blessed Committers, mainframe98

Reviewed By: O1 Blessed Committers, mainframe98

Subscribers: mainframe98, tobiaswiese, valerio.bozzolan, Matthew, Cigaryno

Differential Revision: https://we.phorge.it/D26254

+9 -9
+5 -5
src/applications/transactions/view/PhabricatorApplicationEditHTTPParameterHelpView.php
··· 34 34 $object = $this->getObject(); 35 35 $fields = $this->getFields(); 36 36 37 - $uri = 'https://your.install.com/application/edit/'; 37 + $uri = 'https://phorge.example.com/application/edit/'; 38 38 39 39 // Remove fields which do not expose an HTTP parameter type. 40 40 $types = array(); ··· 67 67 %s 68 68 ``` 69 69 70 - However, `your.install.com` will be the domain where your copy of this software 71 - is installed, and `application/` will be the URI for an application. Some 72 - applications have multiple forms for creating objects or URIs that look a little 73 - different than this example, so the URI may not look exactly like this. 70 + However, `phorge.example.com` will be the domain where your copy of this 71 + software is installed, and `application/` will be the URI for an application. 72 + Some applications have multiple forms for creating objects or URIs that look a 73 + little different than this example, so the URI may not look exactly like this. 74 74 75 75 To prefill the form, add properly encoded HTTP parameters to the URI. You 76 76 should end up with something like this:
+4 -4
src/docs/user/userguide/forms.diviner
··· 73 73 `projects` parameter to the URI like this: 74 74 75 75 ``` 76 - https://your.install.com/application/edit/?projects=skunkworks 76 + https://phorge.example.com/application/edit/?projects=skunkworks 77 77 ``` 78 78 79 79 The parameters available in each application vary, and depend on which fields ··· 332 332 one: 333 333 334 334 ``` 335 - https://your.install.com/maniphest/task/edit/?projects=android 335 + https://phorge.example.com/maniphest/task/edit/?projects=android 336 336 ``` 337 337 338 338 A slightly more advanced method is to create a template task, then use it to ··· 341 341 the a URI that prefills using the template: 342 342 343 343 ``` 344 - https://your.install.com/maniphest/task/edit/?template=123 344 + https://phorge.example.com/maniphest/task/edit/?template=123 345 345 ``` 346 346 347 347 This is a little easier to use, and lets you update the template later if you ··· 358 358 URI, like this: 359 359 360 360 ``` 361 - https://your.install.com/maniphest/task/edit/form/123/ 361 + https://phorge.example.com/maniphest/task/edit/form/123/ 362 362 ``` 363 363 364 364 You can also combine this with templating or prefilling to further specialize