hws_configure #11

  • //
  • guest/
  • perforce_software/
  • helix-web-services/
  • main/
  • helix_web_services/
  • bin/
  • hws_configure
  • Commits
# Change User Description Committed
#11 15622 tjuricek Move source code to 'source/' subdirectory of branch.

build/ will remain where it is.
#10 15111 tjuricek Remove references to actually using the SQLite DB in the installation

Still depending on it to avoid shared library dependencies to system packages
#9 14976 tjuricek Bind on port 9000 instead of a local unix socket.

For whatever reason, the CentOS 6 system configuration does not like the local unix socket permissions, even though it seems like it should be allowable.
#8 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".
#7 14877 tjuricek Fix whitespace in generated nginx.conf
#6 14876 tjuricek Add default Helix Sync depots to our default p4d setup.
#5 14873 tjuricek Added default nginx and p4d setup to hws_configure

This should give users that run hws_configure the first time... something... that could be used for testing a basic setup. How we configure the system from here isn't ironed out yet.
#4 14870 tjuricek Add an upstart configuration for helix_web_services.
#3 14842 tjuricek Add helixwebservices user setup to hws_configure
#2 14841 tjuricek Add *very basic* shell script wrappers to configure and launch the unicorn server.

hws_configure: post-install script to setup or migrate the DB

helix_web_services: bash script to point out the embedded Ruby setup

This is far from complete, just the next step in getting to a basic package-based deployment.
#1 13799 tjuricek Start with branch specs hosting in a new monolithic 'helix web services' project.

Converting from a microservice to a monolithic architecture due to resource constraints at getting a deployable system running. Additionally, since it's not expected that people will upgrade often, the major benefit of microservices - being able to add services individually without affecting others - is not really a major benefit.

The Ruby SDK will be consolidated into a single 'helix web services client' project. It may end up being distributed via Rubygems.

This only runs branch specs at the moment. I want to get a CD pipeline setup for the monolithic server before revising more methods.