Change 13476
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.
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.
Tip: Use n and p to cycle through the changes.