| Name | Modified | Size |
|---|---|---|
| .. | ||
| lib | ||
| packaging | ||
| build.sh | 10 years ago | |
| docker-compose.yml | 10 years ago | |
| Dockerfile | 10 years ago | |
| Gemfile | 10 years ago | |
| LICENSE.txt | 10 years ago | |
| p4_web_services_auth.gemspec | 10 years ago | |
| Rakefile | 10 years ago | |
| README.md | 10 years ago | |
| .gitignore | 10 years ago |
| Change | User | Description | Committed |
|---|---|---|---|
| 13972 | tjuricek | Removing old microservice implementations. The system is now mostly a monolith. Eventua...lly there will be a websocket service. « |
10 years ago |
| 13535 | tjuricek | Add notification_services to deployment, and reconfigure build step to exec bash. The e...xecution bit doesn't seem to stay set on config/bash.sh The notification_services service doesn't have advanced tests just yet. « |
10 years ago |
| 13534 | tjuricek | Remove automatically generated license files and unused run.sh files. | 10 years ago |
| 13528 | tjuricek | Moved rack and app server configuration to be managed via Salt. Also, only using a sing...le value "url" to configure how the p4_project_services instance references the p4_web_api. And, removing the Docker setup, since that won't work for a production system. « |
10 years ago |
| 13520 | tjuricek | Created a 'cluster' build procedure that creates an installer on build, and executes the i...nstall 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. « |
10 years ago |
| 13504 | tjuricek | The 'build-ubuntu12' seems to generate the appropriate debian packages for the distributio...n. I had permissions issues (probably related to shared folder usage) with the dpkg tools. So I've removed them. If we happen to need them, we'll have to figure out a build process. This environment probably shouldn't be used to test the packages, since omnibus likes to dirty everything up, leave files in the /opt/perforce directory owned by vagrant, etc. « |
10 years ago |
| 13500 | tjuricek | Reorganizing Vagrant definitions. Each platform should allow developers to launch envir...onments 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. « |
10 years ago |
| 13496 | tjuricek | Complete and seed the setup of the p4webapi in a development mode. This works against t...he local development tree for dev environments. « |
10 years ago |
| 13488 | tjuricek | Added hsm:startworld and hsm:stopworld tasks to do global starts and stops. This is not... without apparent issues. It appears bundler or ruby is pausing before the nginx launch task happens. I'm not sure if there's some kind of resource issue first. P4WEBAPI-49 « |
10 years ago |
| 13481 | 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. « |
10 years ago |
| 13477 | tjuricek | More docker-compose configuration for projects in research for HSM. Added a geminabox h...ost for the cluster, which allows for quick rebuilds. Each cluster will cache the gems it needs, and publish as well. We may want to put the overwrite commands for all publish steps by default. Note: referencing "external links" can only be done 'at runtime', so "bundle install" really needs to be run in the context of 'docker-compose up' not 'docker-compose build'. This was edited in all configured libraries so far. Finally, added the p4_project_services projects to configuration, which is running under it's own puma instance. The postgres instance is a little tricky to figure out the exact workflow. Right now I'm using the host rake db:migrate task and calling createdb manually, since we need to pass the password along. « |
10 years ago |
| 13476 | tjuricek | Some initial concepts for 'hsm' Using docker-machine and docker-compose for a basis is... very useful, instructions are documented in hsm/hsm/README.md Currently uses the installer for perforce, doesn't have to. We *very likely* want to consider a way to set up a Docker image with data. Probably should change the Docker image for perforce to use an internal 15.x release. We may want to have all other web services just use the p4_web_api for auth, and alter our shared middleware approach. It's likely that we'd want a library of 'docker images' for our components, since not every component will get touched frequently. This will save a lot of startup time, just download and go. This may be step #1 even of hsm. « |
10 years ago |
| 13474 | tjuricek | Corrected regressions that broke the API and Project services specs. | 10 years ago |
| 13470 | tjuricek | Phoenix notification services, client API, including new phoenix_updater This is an int...erim 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. « |
10 years ago |
| 13441 | tjuricek | As an interim step, allow the application/json Accept type to return the p4d ticket for th...e server. In the future, there will likely be an adjustment to the POST request to store a separate host we attempt to generate a ticket for. Right now, these are host unlocked tickets, and not the production solution. « |
10 years ago |
| 13416 | tjuricek | Set up the p4_web_api related projects to be loaded by the parent Gemfile to make it a lit...tle 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 « |
10 years ago |
| 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. « |
10 years ago |