# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 16345 | tjuricek | Removing candidate branch | ||
#1 | 16342 | tjuricek |
Create candidate branch. This branch is mostly here to start work on our release infrastructure. |
||
//guest/perforce_software/helix-web-services/main/source/doc/03_configuration.asc | |||||
#10 | 16332 | tjuricek |
Update documentation for new configuration, deployment. Also, fix default location for hws_console. |
||
#9 | 16280 | tjuricek |
Adjustments for Helix Cloud settings Several tests are now disabled due for Helix Cloud since they won't work on streams, which HC only uses. |
||
#8 | 16095 | tjuricek | Shorten /helix_versioning_engine URLs to /p4 | ||
#7 | 16090 | tjuricek |
Rename ENABLE_AUTOMATIC_TRUST to ENABLE_MAN_IN_MIDDLE_ATTACKS and remove documentation. Only use this option for allowing developers to regenerate fingerprints on their own p4ds. |
||
#6 | 16076 | tjuricek |
Use a TRUST_FINGERPRINTS file to decide which p4 trust fingerprints to accept. If we receive a request that is *not* in this file, and this setting is used, we reject it. This is our recommendation for production servers. The ENABLE_AUTOMATIC_TRUST is only to be used for testing servers. We need this because of a high-cost of the Qt test framework. Revised upon request of Alan Teague and Doug Scheirer. |
||
#5 | 15969 | tjuricek |
Add support for repo creation/update and deletion, same for SSH keys. Add util module for supporting methods, modify temp client to dissapear. (Modified submit of review 15549 by @ptomiak) |
||
#4 | 15717 | tjuricek |
Added notes on post-install configuration and uninstallation. It's unclear to me if we should invest significant time into configuration yet or not. |
||
#3 | 15700 | tjuricek | Allow custom scripts to be loaded into the process in order to modify HWS or add some functionality. | ||
#2 | 15698 | tjuricek |
Added a /helix_versioning_engine/v[api]/login method This is used by the Helix Sync client to differentiate the auth source of HWS from that of P4D (to be used for projects). |
||
#1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
//guest/perforce_software/helix-web-services/main/doc/03_configuration.asc | |||||
#11 | 15545 | tjuricek | Place in config and hooks for Helix Cloud authentication. | ||
#10 | 15483 | tjuricek |
Add a new 'hws_console` application to the deployment. This should give users the ability to use the Ruby client for quick and dirty debugging of issues with HWS. Since it's so easy, I've added it to the deployment guide. |
||
#9 | 15437 | tjuricek |
Basic "HVE Project" implementation. This will allow directories in a HVE instance to host 'projects' for use by helix sync. There are no methods defined for creating the projects, however. This does not include any specialization or testing in the Qt API yet. I may investigate creating a "higher level" interface for Qt client apps. |
||
#8 | 15297 | tjuricek |
Implement of 'cluster services' configuration. The configuration will be stored in a local JSON file, which is expected to be maintained by the systems admin. Eventually, it's expected to have this sort of thing implemented via Helix Admin. |
||
#7 | 15257 | tjuricek |
Added stress test, corrected per-request header config. Apparently using underscores is a "special" mechanism for HTTP headers, and requires adjusting nginx to allow such things. Might as well just recommend using hyphens, which get converted to underscores anyway. The current test just hits a listing of 20000 files against p4play. Returns a 2.5 MB response, which doesn't seem to cause problems (yay). |
||
#6 | 15240 | tjuricek |
Set api level via request path on all Helix Versioning Engine methods. This will allow migration of applications to different P4D versions. Our internal methods (like project API) should attempt to handle backward compatibility similarly. P4WEBAPI-118 |
||
#5 | 15229 | tjuricek | Remove incorrect default setting for P4HOST | ||
#4 | 15208 | tjuricek |
Revise 'command' implementation, tests, and documentaiton. This includes a change from a command blacklist to a whitelist. See P4WEBAPI-21 |
||
#3 | 15110 | tjuricek | Revise changes methods for new p4 connection handling, add server specs, remove model references in client, and update asciidoc documentation. | ||
#2 | 15090 | tjuricek |
Update _proposed_ API for project services. This is *very likely* to change, and will not be implemented until reviewed. |
||
#1 | 15038 | tjuricek | Document 'login' auth method and client programming overview. |