Bug 766400 - CSProcessor instance on skynet.bne.redhat.com
Summary: CSProcessor instance on skynet.bne.redhat.com
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Joshua Wulf
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-12 00:47 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-30 05:26:11 UTC

Attachments (Terms of Use)
This is the recipe I used to set up the webservice (4.67 KB, text/plain)
2011-12-12 00:50 UTC, Joshua Wulf 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Joshua Wulf 2011-12-12 00:47:54 UTC 
I set up an instance of the content spec processor on
skynet.bne.redhat.com. 

It is in /opt/contentspec-processor.

It's running on port 8180; it has read-only
access to the skynet database, and read/write access as user csprocessor
to the CSProcessor schema.

I've created a service script for it, and it's set to autostart. It can
be started with "service csprocessor start", but requires termination
from the process ID to stop, because I couldn't figure out how to get
the remote management interface to run on a port that doesn't clash with
the skynet AS 7 instance.
Comment 1 Joshua Wulf 2011-12-12 00:50:59 UTC 
Created attachment 545465 [details]
This is the recipe I used to set up the webservice
Note You need to log in before you can comment on or make changes to this bug.