p4ws - Perforce Web Services ---------------------------- ## Project Structure Perforce Web Services is actually a suite of several different kinds of applications, client libraries, and utilities (like installers) that form a kind of microservice system for applications. Projects that are simple (they make one thing), have all their code directly underneath this directory. Projects that have clients, or are broken up into multiple related projects, have a subdirectory under this that groups these related projects together. See the p4_project_services tree as an example. ## Project Naming Because these projects may be distributed via RubyGems for heavily customized deployments, prefix everything with 'p4_'. ## Versioning Each project is versioned independently. The underlying p4_web_api is actually quite tied to the underlying P4 server version, since that's what defines all data. This will need to match the major/minor version of the Perforce instance. Other projects do *not* have to follow this convention. Instead, they should attempt to follow a strict semantic versioning mechanism: - Major version number indicate a breaking change in the API. - Minor version numbers indicate an addition, that shouldn't break any existing clients. - Release numbers just indicate a new release, probably for bug fixes.
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 13514 | tjuricek |
Revised some of the p4_web_api tests to work under the installed 'production' perforce system. Notes on data resets: sudo p4dctl stop helix-evaluation sudo rm -rf /var/lib/perforce/p4d sudo /opt/perforce/sbin/configure-perforce-server.sh helix-evaluation -n -p 1666 -r /var/lib/perforce/p4d -u super -P 'superuser1A!' --unicode sudo su webservices /home/webservices/.rvm/wrappers/ruby-2.2.2@p4webapi/p4util init -p :1666 /home/vagrant/p4ws/p4init |
||
#1 | 13412 | tjuricek |
Initial version of the web-services mainline. This is a collection of several projects, that will likely often get released together, though many of them may not always be relevant. See the README for more information. |