Gemfile.lock #2

  • //
  • guest/
  • perforce_software/
  • helix-web-services/
  • candidate/
  • source/
  • helix_web_services/
  • Gemfile.lock
  • Commits
# Change User Description Committed
#2 16345 tjuricek Removing candidate branch
#1 16342 tjuricek Create candidate branch.

This branch is mostly here to start work on our release infrastructure.
//guest/perforce_software/helix-web-services/main/source/helix_web_services/Gemfile.lock
#6 16285 tjuricek Deploy/install improvements

- Include nginx in Omnibus distribution, do not conflict with system nginx install

- Use old-school sysvinit scripts

- Create 'hws_launch' wrapper to initiate nginx and unicorn, which also reads system config file for settings
#5 15972 tjuricek Update Gemfile dependencies for new project
#4 15969 tjuricek Add support for repo creation/update and deletion, same for SSH keys.

Add util module for supporting methods, modify temp client to dissapear.

(Modified submit of review 15549 by @ptomiak)
#3 15724 tjuricek Removed sequel and sqlite dependencies
#2 15719 tjuricek Ensuring the omnibus steps do not fail due to read-only access caused by the p4 client.
#1 15622 tjuricek Move source code to 'source/' subdirectory of branch.

build/ will remain where it is.
//guest/perforce_software/helix-web-services/main/helix_web_services/Gemfile.lock
#8 15513 tjuricek Add a product ID header for debugging purposes.

This will generally display INVALID unless the version file has been created during the build.
#7 15483 tjuricek Add a new 'hws_console` application to the deployment.

This should give users the ability to use the Ruby client for quick and dirty debugging of issues with HWS.
Since it's so easy, I've added it to the deployment guide.
#6 15132 tjuricek Provde a basic submit -e mechanism on classic perforce workspaces.
#5 15120 tjuricek Updating gem dependencies.

p4util required updating might as well update others, seems to work.
#4 15090 tjuricek Update _proposed_ API for project services.

This is *very likely* to change, and will not be implemented until reviewed.
#3 15032 tjuricek Starting config and doc revisions.
System is now broken while revisions underway.

Configuration 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.
#2 14932 tjuricek CentOS 6 deployment support.

I need a reliable way of detecting platform information. So I'm installing ohai, which comes from Chef, and seems to be a stable way of determing things like "I'm running on CentOS 6.5".
#1 14794 tjuricek Omnibus installation framework.

Right now, this mostly just packages up most of the software for use within an embedded ruby distribution. Not everything is working because there are decisions to make I'm not entirely sure about. Things, like, "do we embed postgres", or "do I embed unicorn and generate a stupid init.d script".