# Avoid any environmental status pollution from your dev environment ENV.keys.select { |k| k =~ /^P4/ }.each { |k| ENV.delete(k) } require 'p4_web_api' WS_HOST = ENV['WS_HOST'] || 'p4' puts "WS_HOST #{WS_HOST}" DATA_ROOT = ENV['DATA_ROOT'] || '/p4_web_api' Dir.mkdir("#{DATA_ROOT}/tokens") unless Dir.exist?("#{DATA_ROOT}/tokens") Dir.mkdir("#{DATA_ROOT}/workspaces") unless Dir.exist?("#{DATA_ROOT}/workspaces") api = P4WebAPI::App.new api.settings.p4 = { 'port' => "#{WS_HOST}:1666" } api.settings.token_path = "#{DATA_ROOT}/tokens" api.settings.workspace_folder = "#{DATA_ROOT}/workspaces" run api
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#7 | 13528 | tjuricek |
Moved rack and app server configuration to be managed via Salt. Also, only using a single 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. |
||
#6 | 13490 | tjuricek |
Removing external_links configuration references from the p4_web_api. P4WEBAPI-51 |
||
#5 | 13489 | tjuricek |
Add zookeeper service to cluster for development evaluation. It's a little unclear exactly what values need to be distributed via zk, since a lot of the configuration may end up being handled via ports. I wanted to at least provide a way to evaluate this. P4WEBAPI-60 |
||
#4 | 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 |
||
#3 | 13487 | tjuricek |
Pushing host, port, and URL configuration into docker-compose.yml consistently. All other configuration will be figured out by a separate system later. P4WEBAPI-51 |
||
#2 | 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. |
||
#1 | 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. |