Hey Branden,
I think my point was more toying with "my own" instance ;)
Andrew
-----Original Message-----
From: Branden Visser [mailto:mrvis...@gmail.com]
Sent: 30 January 2014 11:47
To: Andrew Martin
Cc: oae-dev@collab.sakaiproject.org
Subject: Re: [oae-dev] Basic Hilary start up question...
Hi Andrew,
It would be possible, but I'm not sure it's necessary. Presumably when setting
up a system just to become familiar and test with, the administrator interface
does not need to be blocked and is available straight away through the browser.
The Administrative UI is part of the OAE experience for both global and tenant
administrators, so rather than treating it as an obstacle to get started with
OAE, it's part of process becoming familiar.
If you want to toy around with OAE and the administrative interface to have
some perspective about what I'm talking about, you can do so on our QA server:
Administrative Interface: admin.oae-qa0.oaeproject.org (Username /
Password: administrator / administrator) Example Tenant:
oae.oae-qa0.oaeproject.org
Hope that helps,
Branden
On Thu, Jan 30, 2014 at 5:32 AM, Andrew Martin <andrew.mar...@newcastle.ac.uk>
wrote:
> All,
> Just thinking a little more... would it be possible to make a csql
> script that pre-populated Cassandra with some tables that would make an
> example tenant? i.e. just something quick and dirty so that us newbies can
> get to grips with "something" that works straight away?
>
> Andrew
>
>
> -----Original Message-----
> From: oae-dev-boun...@collab.sakaiproject.org
> [mailto:oae-dev-boun...@collab.sakaiproject.org] On Behalf Of Andrew
> Martin
> Sent: 30 January 2014 10:24
> To: 'Nicolaas Matthijs'
> Cc: 'oae-dev@collab.sakaiproject.org'
> Subject: Re: [oae-dev] Basic Hilary start up question...
>
> Hello (again?) Nicolaas... think we may have briefly met at sakai paris some
> time ago?
>
> Thanks, I saw your reply before Brendan's, I'll try the curl route
> and I'll try Brendan's suggestions too, having an admin url you could expose
> externally (temporarily) would be my preferred choice, although I'm not
> unfamiliar with REST interfaces so may be able to figure it out....
>
> I'm "very" encouraged that oae has been re-written in js + node, as much as I
> like Java (amongst other languages) and have a background in it, I've been
> doing a lot of work recently with phonegap/cordova and node.js and have grown
> a fondness to it.... however if I had a pound for every time I told someone I
> was writing something in javascript and that person rolled their eyes I would
> be a very rich man right now.
>
> I'm yet to dig too deeply (or get a working service) yet but I'm hoping this
> incarnation of sakai is what I think it might be (REST/JSON based, node
> plugins, better documentation, more open community), my dev experience with
> CLE so far can be simply summed up with the word "frustrating".
>
> Andrew
>
> -----Original Message-----
> From: Nicolaas Matthijs [mailto:nicolaasmatth...@googlemail.com] On
> Behalf Of Nicolaas Matthijs
> Sent: 30 January 2014 09:38
> To: Andrew Martin
> Cc: oae-dev@collab.sakaiproject.org
> Subject: Re: [oae-dev] Basic Hilary start up question...
>
> Hi Andrew,
>
> If you did want to use cURL to create a tenant, you should be able to follow
> these steps:
>
> 1) Get a session cookie by logging in as the global administrator:
>
> ADMIN_COOKIE=$(curl -s -e "/" --cookie-jar -
> -d"username=administrator" -d"password=<adminPassword>"
> http://<youradminhost>/api/auth/login | grep connect.sess | cut -f 7)
>
> 2) Create the new tenant through the REST API:
>
> curl -d "alias=newcastle&displayName=University of
> Newcastle&host=ncl.oae.com" --cookie connect.sess=${ADMIN_COOKIE} -e
> "/" http://<youradminhost>/api/tenant/create
>
> Hope that helps,
> Nicolaas
>
>
> On 30 Jan 2014, at 08:56, Branden Visser <mrvis...@gmail.com> wrote:
>
>> Hi Andrew,
>>
>> Exposing the global administrative console publicly should be fine
>> but not mandatory -- assuming you have locked it down with a
>> sufficiently complex password and have put in provisions for brute-force
>> attempts.
>> It will be much easier for you to have admin access through a browser.
>> Technically you could use cURL to interact with it, but you'll have
>> to manually mingle with a cookie.
>>
>> In order to have a tenant that you can host users on, you'll need to
>> log in to the administrative interface and create one.
>>
>> Hope that helps,
>> Branden
>>
>> On Wed, Jan 29, 2014 at 7:53 AM, Andrew Martin
>> <andrew.mar...@newcastle.ac.uk> wrote:
>>> Hello all,
>>>
>>> I have a question that I suspect has a simple answer
>>> but I'd like to check....
>>>
>>>
>>>
>>> I've followed the big readme at
>>> https://github.com/oaeproject/Hilary/blob/3.0.0/README.md and
>>> managed to get all the dependencies working (I "think"), I'm
>>> currently at the bit where you have to set up tenants and I'm
>>> hitting the "418 status code" problem
>>> (http://collab.sakaiproject.org/pipermail/oae-dev/2013-September/003606.html).
>>> This seems to be remedied by going to admin.oae.com on the local machine...
>>> however my install is on a headless centos, so how do I login to the
>>> administrative console without a GUI? Stuff like lynx/links borks
>>> and says I need javascript, which is kinda what I expected! I don't
>>> know whether I should have made the admin url externally available....
>>> somehow (which doesn't sound like a good idea) or whether you just
>>> "can't" set up oae without a GUI browser?
>>>
>>>
>>>
>>> Regards
>>>
>>>
>>>
>>> Andrew Martin
>>>
>>>
>>>
>>> Research and Collaborative Services
>>>
>>> Newcastle University
>>>
>>>
>>> _______________________________________________
>>> oae-dev mailing list
>>> oae-dev@collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>>>
>> _______________________________________________
>> oae-dev mailing list
>> oae-dev@collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>
> _______________________________________________
> oae-dev mailing list
> oae-dev@collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
> _______________________________________________
> oae-dev mailing list
> oae-dev@collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev
