Thanks Ian,
Out of interest - why have you fallen out of love with it all?
Toby
On 20 April 2015 at 13:35, Ian Turton <[email protected]> wrote:
> For example to set up a workspace (ian) you can GET
> http://localhost:8080/geoserver/rest/workspaces/ian.xml and then when
> setting up a new one POST that xm l to
> http://localhost:8080/geoserver/rest/workspaces
>
> The same follows for the other resources - I haven't yet found out how to
> create a new grid set for GWC but I suspect that I need to change my
> endpoint.
>
> Ian
>
> On Mon, Apr 20, 2015 at 1:07 PM Tobias Reinicke <[email protected]>
> wrote:
>
>> Thanks Ian, good to know.
>> When you say grab the REST output - from where would I theoretically be
>> grabbing this? The logs?
>>
>> Thanks
>> Toby
>>
>> On 20 April 2015 at 12:57, Ian Turton <[email protected]> wrote:
>>
>>> I've been doing something similar with Chef, though I'm falling out of
>>> love with it. I went with the configuring with REST - once you have the
>>> data loaded the first time you can grab the REST output and then edit as
>>> needed and store it for upload later.
>>>
>>> Ian
>>>
>>> On Mon, Apr 20, 2015 at 11:53 AM Tobias Reinicke <[email protected]>
>>> wrote:
>>>
>>>> Hello All,
>>>>
>>>> I am working on a new project and part of it is to use Puppet for
>>>> deploying machines, some of which are to have geoserver on them.
>>>>
>>>> It's not that complex, basically puppet allows you to provision hosts
>>>> with files / data / packages etc - whatever you want.
>>>>
>>>> When it comes to geoserver, I am just getting to a point where I need
>>>> to basically tackle configuration. What I am doing at the moment is
>>>> building a machine (linux) and installing the pre-reqs (tomcat etc) and
>>>> then installing geoserver (all via aptitude). Once that is all up and
>>>> running I need to configure it with the data and layers I want. Data isn't
>>>> an issue - it's how the config works.
>>>>
>>>> Currently I am building up my required layers manually via the gui the
>>>> way I want, and then take a copy of the 'workspaces' folder which I then
>>>> want to inject into any new build of my geoserver machine. (as well as the
>>>> data source obviously, local tiff files for now).
>>>>
>>>> Is this something that might theoretically work?
>>>>
>>>> What I have found is that my workspace is created as required - as long
>>>> as I have;
>>>> /workspaces/default.xml
>>>> /workspaces/[myworkspace]/namespace.xml
>>>> /workspaces/[myworkspace]/workspace.xml
>>>>
>>>> But continuing down this route, and adding my layers and coverages in
>>>> the same way doesn't work.
>>>>
>>>> I'm aware I could do all this with REST API commands (as well as with
>>>> GUI) - and the REST interface is my next port of call, but I'd be
>>>> interested in any insights to the above.
>>>>
>>>> Thanks
>>>>
>>>> Toby
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>>>> Develop your own process in accordance with the BPMN 2 standard
>>>> Learn Process modeling best practices with Bonita BPM through live
>>>> exercises
>>>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>>>> event?utm_
>>>>
>>>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
>>>> Geoserver-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>>
>>>
>>
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
