| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 15791 | tjuricek | Removing very old p4ws branch | ||
| #1 | 13266 | tjuricek |
Reorganized depot to avoid stream/main in path. This may be re-imported. |
||
| //guest/tjuricek/p4ws/stream/main/Gemfile | |||||
| #14 | 13235 | tjuricek |
Setup God to manage both the p4 web api and p4 project services processes. Apparently, there can only be one true god per machine. |
||
| #13 | 13230 | tjuricek |
Created a 'cluster' build procedure that creates an installer on build, and executes the install on a test instance. The main change is to package all gem dependencies via 'vendor/cache' (using the 'bundle package' command). Right now, there appears to be an issue with test data initialization, which may need a revised approach. |
||
| #12 | 13210 | tjuricek |
Reorganizing Vagrant definitions. Each platform should allow developers to launch environments for development, builds, or 'production', so the entire CD process can be evaluated by anyone wiht access to the source tree. This may eventually bring up a transient vSphere machine up and down, which may be necessary for sandboxing Omnibus related builds. |
||
| #11 | 13209 | tjuricek |
Simple p4_web_api omnibus installer. Successfully built using a test-kitchen VM for debian ubuntu 14.04. |
||
| #10 | 13191 | tjuricek |
Tests for the p4 web api and p4 project services now pass against a development setup both in and out of the docker cluster. Note that configuration *has not* been finalized, so conventions to dealing with development vs production need to be organized a bit. |
||
| #9 | 13190 | tjuricek |
Creating several Rake tasks for our "hsm" configuration that are based on a Ruby API config file. The config file points to machines and services in the system which then takes care of setting up the docker-machine environment and docker-compose configuration. |
||
| #8 | 13180 | tjuricek |
Phoenix notification services, client API, including new phoenix_updater This is an interim commit containing a first pass implementation of the phoenix_updater. Notably missing parts: - The Qt API doesn't yet actually interact with the phoenix_updater - The phoenix_services web service doesn't filter out notifications I *may* end up creating another web application *just* to filter out notifications, since this may end up taking up a lot of background workers. |
||
| #7 | 13177 | tjuricek | Add a basic notification_services endpoint that can setup a trigger entry and accept basic POST requests. | ||
| #6 | 13131 | tjuricek |
Skeleton of the p4 phoenix services It's very likely that real 'business logic' will need to happen, but a lot of that is TBD. This is mostly to get the infrastructure in place before we start adding details, like, 'every new project lives under //phoenix/[project]/...', yada yada yada. |
||
| #5 | 13130 | tjuricek |
Setup the main directory to launch specs in subprojects and a unicorn-based daemon via rake. See rake -T for details, but this should allow for CI builds to collect output. |
||
| #4 | 13128 | tjuricek | Added p4_project_services to development config.ru, and reconfigured p4 web api client tests to use the new paths. | ||
| #3 | 13127 | tjuricek |
Added a 'rake work/config.ru' task, that creates a local rack configuration. This now includes the project services, which is not yet mounted. The p4 web api tests still pass though. |
||
| #2 | 13126 | tjuricek |
Set up the p4_web_api related projects to be loaded by the parent Gemfile to make it a little easier to launch a test p4d with different seed data. Also fixed a couple of minor issues related to the client api. You'll notice that the 'rake api_reset api_init' task sets up a p4d for the p4_web_api tests, where the 'rake proj_reset proj_init' tasks set up p4d for project services testing. An example p4_web_api.ru that can be used for launching just the p4_web_api: require 'p4_web_api' # Do *not* let your development environment variables pollute how the p4 web api runs! ENV.keys.select { |k| k =~ /^P4/ }.each { |k| ENV.delete(k) } api = P4WebAPI::App.new puts 'changing paths' api.settings.token_path = '/Users/tjuricek/dev/p4ws/work/tokens' api.settings.workspace_folder = '/Users/tjuricek/dev/p4ws/work/workspaces' api.settings.p4 = {'port' => 'localhost:1666', 'charset' => 'auto'} run api |
||
| #1 | 13125 | tjuricek | Add some basic utility methods to the top level. | ||