[SAC] Mapbender team is going to set up services on ProjectsVM and AdhocVM

Astrid Emde astrid.emde at wheregroup.com
Thu Aug 5 16:45:06 EDT 2010


Hey Chris,

thanks - you did all the work already.

On Thu, August 5, 2010 8:20 pm, christopher.schmidt at nokia.com wrote:
>

> On Aug 5, 2010, at 4:05 PM, ext Astrid Emde wrote:
>
>
>> Hello,
>>
>>
>> the Mapbender team wants to use the two VMs : * AdhocVM (as a testbed)
>> * ProjectsVM (1. to show our demos and 2. to move mapbender.org after
>> FOSS4G)
>>
>>
>> This is what I want to do in the next days:
>>
>>
>> AdhocVM
>> 1) I would create the directory /osgeo  on adhocvm (like it is on
>> projectsvm)
>
> Already exists.
>
>
>> 2) I would install svn on adhocvm
>>
> Done.
>
>
>> 3) I would install PostgreSQL/PostGIS  on adhocvm
>>
> Done.
>
>
>
>> 4) I would install php on adhocvm
>>
> Done.
>
>
>
>> 5) install gettext
>>
> Done, though I expect you actually want something to hook up PHP to
> gettext, which isn't done, because I don't know what you actually want.

we need both php-gettext and gettext.
we use msgfmt to compile our language mo-files


>> ProjectsVM
>> 1) we want to move mapbender.org to ProjectsVM in the future but not
>> before FOSS4G
>
> This may be better served by being hosted on the wiki.osgeo.org machine,
> depending how much direct access is required; if it's a one-time setup that
> SAC can make, it might make more sense to only have Wikipedia
> installed in one place.

ok - for us wiki.osgeo.org would be fine too. We have an existing
mediawiki with a MySQL database that has to be moved to another server.


>> 2) we want to set up mapbender demos at somthing like
>> projects.mapbender.osgeo.org on the ProjectsVM - which was former on
>> telascience 3) who is already using PostgreSQL on the ProjectsVM? I
>> would like to create a new role and mapbender databases. But I don't
>> have the assword to get access to the database.
>
> createuser -U postgres astrid createdb -U postgres foo_bar
>
> Any user who has local access to the machine can authenticate as the
> postgres user, because users who can access the machine are considered
> trusted by Postgres.

ok - thanks. So I will try this.

Astrid



More information about the Sac mailing list