@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
Cleanup some clustering rough edges
Summary: Suppress an unhelpful Almanac transaction and document the location of the secret clustering management capability. I thought maybe implementing `shouldHide` and checking for `isCreate` would work, but the binding apparently gets created before an interface is bound to it.
Test Plan: Looked at a fresh binding and didn't see "Unknown Object(??)", ran bin/diviner and saw expected output.
Reviewers: epriestley
Reviewed By: epriestley
Subscribers: Korvin
Differential Revision: https://secure.phabricator.com/D19917
+28
-6
+16
-5
src/applications/almanac/xaction/AlmanacBindingInterfaceTransaction.php
+16
-5
src/applications/almanac/xaction/AlmanacBindingInterfaceTransaction.php
···
55
55
}
56
56
57
57
public function getTitle() {
58
-
return pht(
59
-
'%s changed the interface for this binding from %s to %s.',
60
-
$this->renderAuthor(),
61
-
$this->renderOldHandle(),
62
-
$this->renderNewHandle());
58
+
if ($this->getOldValue() === null) {
59
+
return pht(
60
+
'%s set the interface for this binding to %s.',
61
+
$this->renderAuthor(),
62
+
$this->renderNewHandle());
63
+
} else if ($this->getNewValue() == null) {
64
+
return pht(
65
+
'%s removed the interface for this binding.',
66
+
$this->renderAuthor());
67
+
} else {
68
+
return pht(
69
+
'%s changed the interface for this binding from %s to %s.',
70
+
$this->renderAuthor(),
71
+
$this->renderOldHandle(),
72
+
$this->renderNewHandle());
73
+
}
63
74
}
64
75
65
76
public function validateTransactions($object, array $xactions) {
+12
-1
src/docs/user/cluster/cluster_repositories.diviner
+12
-1
src/docs/user/cluster/cluster_repositories.diviner
···
98
98
to respond to the user.
99
99
100
100
101
-
Setting up a Cluster Services
101
+
Setting up Cluster Services
102
102
=============================
103
103
104
104
To set up clustering, first register the devices that you want to use as part
···
106
106
107
107
NOTE: Once you create a service, new repositories will immediately allocate
108
108
on it. You may want to disable repository creation during initial setup.
109
+
110
+
NOTE: To create clustered services, your account must have the "Can Manage
111
+
Cluster Services" capability. By default, no accounts have this capability,
112
+
and you must enable it by changing the configuration of the Almanac
113
+
application. Navigate to the Alamanc application configuration as follows:
114
+
{nav icon=home, name=Home >
115
+
Applications >
116
+
Almanac >
117
+
Configure >
118
+
Edit Policies >
119
+
Can Manage Cluster Services }
109
120
110
121
Once the hosts are registered as devices, you can create a new service in
111
122
Almanac: