[GeoNode-devel] Geonode in vagrant
Toni Schönbuchner
toni.schoenbuchner at csgis.de
Fri Feb 15 03:15:03 PST 2019
Dear Pieter,
assumed your Ubuntu-Box has networking provisioned with 192.168.33.23
you would need to set following vars:
(1) https://github.com/csgis/geonode_ansible/blob/master/hosts#L3
# you can find the correct ansible_ssh_private_key file via $ vagrant ssh-config
192.168.33.23 ansible_ssh_port=22 ansible_ssh_user=vagrant ansible_ssh_private_key_file=/Users/pieter/.ssh/id_rsa
(2) https://github.com/csgis/geonode_ansible/blob/master/group_vars/all#L10
server_name: 192.168.33.23
Optional:
Use a different sudo user for your setup:
-> https://github.com/csgis/geonode_ansible/blob/master/group_vars/all#L3
Use a different name for your project:
-> https://github.com/csgis/geonode_ansible/blob/master/group_vars/all#L16
Best regards,
Toni
> Am 14.02.2019 um 16:16 schrieb Pieter du Plooy <pjduplooy.gis at gmail.com>:
>
> Toni
>
> If I use the ip address as is in the vagrant file, what vars do you recommend I change?
>
>
> On Thu, Feb 14, 2019 at 1:11 PM Toni Schönbuchner <toni.schoenbuchner at csgis.de <mailto:toni.schoenbuchner at csgis.de>> wrote:
> Dear Pieter,
>
> the workflow is like this:
>
> 1) Spin a plain vagrantbox from Ubuntu base box
> https://gist.github.com/t-book/7bafe00d0e0ca1be5669ecbf5e0d6e84 <https://gist.github.com/t-book/7bafe00d0e0ca1be5669ecbf5e0d6e84>
> $ vagrant up
> $ vagrant ssh
> $ sudo apt install python
> 2) install ansible on your host
> 3) clone the ansible repository I´ve sent
> 4) adjust the vars as explained in the readme
> https://github.com/csgis/geonode_ansible#installing <https://github.com/csgis/geonode_ansible#installing>
> 5) Run the playbook with: $ ansible-playbook -v -i hosts site.yml
>
> Voila ansible should install geonode 2.10 at your vanilla vagrant box ;)
>
> Best regards,
>
> Toni
>
>> Am 14.02.2019 um 11:57 schrieb Pieter du Plooy <pjduplooy.gis at gmail.com <mailto:pjduplooy.gis at gmail.com>>:
>>
>> Toni
>>
>> Can I use ansible inside a vagrant box?
>>
>> On Thu, Feb 14, 2019 at 12:41 PM Pieter du Plooy <pjduplooy.gis at gmail.com <mailto:pjduplooy.gis at gmail.com>> wrote:
>> Hi Toni
>>
>> A video would be much appreciated.
>>
>> On Thu, Feb 14, 2019 at 11:27 AM Toni Schönbuchner <toni.schoenbuchner at csgis.de <mailto:toni.schoenbuchner at csgis.de>> wrote:
>> Dear Pieter,
>>
>> I´m currently on travel but can share a vagrant box next week when back in office.
>>
>>> Is it possible that you might have a documentation set that I can print and then follow from there?(I follow that better). I want to see why things are done in a certain way.
>>
>> Well this should be covered by documentations. Unfortuantely it´s a bit outdated.
>> A rework is on my list for a long time. Until then you´re welcome to ask why something is
>> happening when.
>>
>>> Your guidance would be appreciated. (On a side note I have been using your vagrant box since you pushed it to Vagrant Cloud. I also prefer Vagrant over Docker, since I feel I have more control, and can then experiment more).
>>>
>>> But the time has now come for me to build a box by myself, so your guidance will be appreciated.
>>
>>
>> +1
>> The ansible playbook I´ve sent will do exactly that. You can spin your vagrant box from
>> ubuntu image. Configure vars like IP, user etc and ansible will run all needed commands.
>> The nice part about it is that they stay very close to the official docs. It should be easy
>> to understand the ansible tasks also knowing nothing about it. If you want I can
>> share a video guiding you through relevant steps.
>>
>> Cheers,
>>
>> Toni
>>
>>
>>> Am 14.02.2019 um 03:39 schrieb Pieter du Plooy <pjduplooy.gis at gmail.com <mailto:pjduplooy.gis at gmail.com>>:
>>>
>>> Thanks Toni
>>>
>>> Would be much appreciated.
>>>
>>> I was trying to follow your Geonode 2.8 vagrant video, but am struggling to jump between pausing the video, and then actually following the tasks (Just a personal issue).
>>>
>>> Is it possible that you might have a documentation set that I can print and then follow from there?(I follow that better). I want to see why things are done in a certain way.
>>>
>>> Your guidance would be appreciated. (On a side note I have been using your vagrant box since you pushed it to Vagrant Cloud. I also prefer Vagrant over Docker, since I feel I have more control, and can then experiment more).
>>>
>>> But the time has now come for me to build a box by myself, so your guidance will be appreciated.
>>>
>>> Pieter
>>>
>>>
>>>
>>> On Wed, Feb 13, 2019 at 10:10 PM Toni Schönbuchner <toni.schoenbuchner at csgis.de <mailto:toni.schoenbuchner at csgis.de>> wrote:
>>> Dear Pieter,
>>>
>>> for 2.10 on 16.04 you could just use the master branch (ansible) for installation
>>> https://github.com/csgis/geonode_ansible/tree/master <https://github.com/csgis/geonode_ansible/tree/master>
>>>
>>> For 2.10 on bionic:
>>> https://github.com/csgis/geonode_ansible/tree/bionic <https://github.com/csgis/geonode_ansible/tree/bionic>
>>>
>>> In case of questions I´m happy to guide you.
>>>
>>> And yes of course I would be prepared to push a box to
>>> vagrant cloud as well ;)
>>>
>>> Cheers,
>>>
>>> Toni
>>>
>>>> Am 13.02.2019 um 21:00 schrieb geonode-devel-request at lists.osgeo.org <mailto:geonode-devel-request at lists.osgeo.org>:
>>>>
>>>> Message: 2
>>>> Date: Wed, 13 Feb 2019 17:40:59 +0200
>>>> From: Pieter du Plooy <pjduplooy.gis at gmail.com <mailto:pjduplooy.gis at gmail.com>>
>>>> To: geonode-devel at lists.osgeo.org <mailto:geonode-devel at lists.osgeo.org>
>>>> Subject: [GeoNode-devel] Geonode in vagrant
>>>> Message-ID:
>>>> <CADsUavHt8_z6G2mN44DT_XFoKShw2-br7-NyE-d1qdyGSbZyqg at mail.gmail.com <mailto:CADsUavHt8_z6G2mN44DT_XFoKShw2-br7-NyE-d1qdyGSbZyqg at mail.gmail.com>>
>>>> Content-Type: text/plain; charset="utf-8"
>>>>
>>>> Hi guys
>>>>
>>>> I would like to ask if Toni is prepared to update the Vagrant box to have
>>>> Geonode 2.10?
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20190215/af2cde18/attachment-0001.html>
More information about the geonode-devel
mailing list