| Name | Modified | Size |
|---|---|---|
| .. | ||
| errors | ||
| app.rb | 10 years ago | |
| sync_project_service.rb | 10 years ago |
| Change | User | Description | Committed |
|---|---|---|---|
| 15098 | tjuricek | Revised project services to GET-only forms. With Helix Sync revising to integrate purel...y with Helix Cloud, this is the only thing we can reasonably define. « |
10 years ago |
| 15078 | tjuricek |
clients spec method revisions Updated some other documentation. |
10 years ago |
| 15077 | tjuricek | Add new 'model' technique, revised branch spec operations, test Auth::Middleware. The R...uby client now does *not* strictly type anything, but extends OpenStruct with helper methods to help deal with inconsistent data formats. See the OpenModel class documentation for more details. The Auth::Middleware class is also *finally* implemented as well. This does not take into account all possible variations of server behavior (yet), but that will happen in follow-up work. « |
10 years ago |
| 15032 | tjuricek | Starting config and doc revisions. System is now broken while revisions underway. Conf...iguration of the p4d connection is now done via a single HWSSettings middleware object injected into the Rack env. The HWSP4Cleanup middleware now cleans up any p4 injected into the Rack env. The Auth::App class now mostly just contains one method to generate a p4 ticket. /auth/v1/login. Added yard documentation for the main project. Yard docs have been reconfigured to dump into build/ directories. This should probably be done with each release. Hm... The top level rake file contains a task, 'all:doc', to update our documentation. This should probably be run for each checkin. Hm... Specs are now using Rack::Test on top of a 'live' p4d. I'd suggest you still use the p4util mechanism, which now dumps to a /tmp folder, so we can safely add P4IGNORE rules back into your local .p4config file. Old 'perforce' application now called 'helix_versioning_engine'. Removing cache data. Helix Sync may be slow. It may also get axed. We'll see. « |
10 years ago |
| 14174 | tjuricek | Call the underlying service with a second named parameter, even if it's nil | 10 years ago |
| 14152 | tjuricek | Allow 'depot_dir' argument to be nil by default | 10 years ago |
| 14151 | tjuricek | Add depot tree control and selection to the create projects page. Styling and error che...cking is kept to a minimum for the time being. Our goal is just internal workflow and feedback. « |
10 years ago |
| 14049 | tjuricek | Add methods to generate client workspaces for a user. The Qt SDK was updated based on i...mmediate need. Also, add Ruby client SDK documentation to the docs site. Everything is early, but there's *some* reference available at least. « |
10 years ago |
| 13941 | tjuricek | Re-implemented the sync project methods at the HTTP level. The Qt API is missing the "m...embers" concept, but it's likely not quite usable just yet. It's existing logic does work, however. « |
10 years ago |
| 13939 | tjuricek | First pass at sync project service. Includes a first pass at validating projects enable...d for Sync. (There's only one branch check at the moment.) Does not include the HTTP layer. « |
10 years ago |
| 13891 | tjuricek | Added a 'member' concept to projects. members is the start of a basic project 'role' de...finition. In Helix sync, this is mostly just used to indicate this is a "my Project" in the UI and a project member can have the ability to leave the project or add someone else. Eventually, we expect "members" to mean more, like, is part of a group that has write access to the files of the project. But that sort of definition is very TBD. « |
10 years ago |
| 13884 | tjuricek | Add Project extension classes models, and the ability for the Project to handle before- an...d after- create callbacks to other services. « | 10 years ago |
| 13839 | tjuricek | Conversion of the p4_project_service microservice to new monolithic system. This may no...t have an HTTP front end in the monolithic system. Project services are really just about how the core object model is structured. It's likely that each application will add their own wrinkles and extensions to the system, so it's unlikely we'll need a generic "project model". Exactly how extensions are registered and used is still a bit TBD at the moment. Previously they were to be registered webhooks, that model may change. Does not include tests yet. « |
10 years ago |