esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Jewett <>
Subject Re: ESME in Thingamy - short report and a question
Date Tue, 05 Jan 2010 14:50:57 GMT
I think in the long run we need to make this stuff configurable via
the property files. The questions are what needs to be configurable
and where is the Jira ticket? ;-)

Sig, do you guys have a Jira account? You should probably get one set
up if you don't. (

My thoughts on what should be turned on and off via property:

1. Web interface (for Sig)
2. Twitter API
3. Original API
4. API2

I think it's important that the availability of the APIs be
configurable for security reasons.


On Tue, Jan 5, 2010 at 9:38 AM, Richard Hirsch <> wrote:
> On Tue, Jan 5, 2010 at 1:23 PM, Sig Rinde <> wrote:
>> Hi everybody,
>> thanks to many members of this group, ESME now working nicely
>> inside/beside Thingamy using latest (untouched ;)) commit (Thanks
>> again Ethan, excellent and fast work!).
>> (Video coming, but have a flu/headachy thing today so head's too mushy)
>> In Thingamy:
>> - (our own) JS client incorporated using API2.
>> - Messages are tagged by one or more objects in Thingamy (tick box in
>> each object enables that).
>> - Messages are filtered by same method from tasks and/or reports.
>> - Multiple tags/relationships enabled - both adding and filtering, but
>> limited to the 50 last messages for now, need to include everything
>> (search?).
>> - Reply "button" in message client adds name (as in Twitter) in
>> response field and tags new message with same tags/relations.
>> - Enable/disable ESME for system in full and for each user role.
>> - Uses pools and names the pool by application name which is set in
>> Thingamy setup interface (under admin) allowing us to use one ESME
>> instance for multiple Thingamy instances.
>> - Messages also shows object(s) it's related to (cryptic name for now)
>> which are links to a graph display of the object and all it's
>> relations to other Thingamy objects.
>> ESME server:
>> - Adding one line to default.props to set admin user
>> - Sign up as that user
>> - Create a token, that's all
>> - In Thingamy setup one sets the application name (names pool) and add
>> the token.
>> - When adding users to Thingamy each will (tick box to enable) be
>> allocated a token and be added to pool
>> Question: After having set up the ESME server once we do not need the
>> 8080 interface anymore. Anybody have an idea as how to disable the
>> ESME webinterface? Preferably without restarting it please :)
>> I might have missed this from earlier mails though... and just
>> "emptying" the default.html file does not cut it security-wise I would
>> think.
> Either lift based changes (Boot.scala?) or just delete all the html
> files from WEB-INF directory. The user trying to access via the web
> would get an lift error but no access.
>> Next step from my side is to implement at our Amazon server (see some
>> image building coming up) for the current pilots.
>> When there, if anybody would fancy a pilot instance including the
>> whole generic Work Processor template gimme a shout and I'll give you
>> one. BTW, quite useful to run whatever group your working in, and as
>> IT consultant/department it's free use to boot.
>> Questions, demos, discussions are what I live for so any time - skype
>> or twitter or mail...
>> Cheers,
>> Sig

View raw message