[GRASS-dev] Final Report

[Blumentrath, Stefan]

Hi Mayank,

Thanks for WebGRASS! I am glad we can test it and thanks also for fixing the compilation issue so fast!

For me it would be absolutely OK that www-users cannot browse the whole server for GRASS DBs. And that all WebGRASS users are forced to work in one DB might be almost a pluss - from the administrators perspective ;-).

What I really like about WebGRASS is the simplicity of installing it. No long configuration and settings to be changed many places. Fast compile and It runs!

A clear drawback however is the Google based authentication, which seems to be the only available authentication method at the moment. Esp. for internal server deployment that does not feel right. Se also: https://github.com/rashadkm/webgrass/issues/19

Another question is: does WebGRASS currently only allow for a single connection at a time?
I opened one login page in one browser, and then tried to access WebGRASS in parallel from another browser, but I got a Connection Refused error...
Is that intentional or a known limitation of the chosen approach? The main aim of the web-UI is to give several users easy-access to GRASS on a server, isn`t it?

Or is the concept that each user should start his/her WebGRASS session (WebGRASS does not require root permissions to start the server process)? Would not that lead to possible issues with port conflicts?

Cheers
Stefan


-----Original Message-----
From: grass-dev [mailto:grass-dev-bounces at lists.osgeo.org] On Behalf Of Yann
Sent: 16. august 2016 18:46
To: grass-dev at lists.osgeo.org
Subject: Re: [GRASS-dev] Final Report

Maybe not the right place to say, but the GRASS GIS data directory is not editable, so cannot change to another GRASSDATA directory name.

On 16/08/2016 02:10, Mayank Agrawal wrote:
> This is my last report of the GSoC project. I would like to thank 
> Rashad and Massimo, my mentors.
> Brief Description My project focussed on the development of web based 
> GUI for the Grass “WebGrass” where people can use Grass modules on 
> their data through a web browser without actually installing GRASS. 
> GRASS is running on a server. The user interface is built using wt web toolkit.
> The state of the project before my GSoC Was not implemented but a proof of concept was there.
> The addition that your project brought to the software A working 
> webapp. People can use data from their system and apply different modules and get output. A Web based UI like GRASS and modules implementation.
> Whole "WebGrass" is a very big project for one gsoc and we try to 
> implement as much as possible.
> Things implemented- * Location and Mapset wizard
>   * UI of the modules
>   * Modules implementation like desktop grass (command line output also)
>   * Authorization of the user
>   * Input/output/processing of raster data
>   * display of raster data
>   * Input/output/processing of vector data
>
>  From this project, a official start of "WebGrass" is done and I hope 
> it will be useful for the people. This has been a very interesting and 
> learning experience. I learned a lot from my mentors. I hope this project keeps on growing and will continue to contribute to this project.
> Links - Github - https://github.com/mayank33/webgrass/commits/gsoc2016 
> https://github.com/mayank33/webgrass/commits/auth
> Project Page - https://trac.osgeo.org/grass/wiki/GSoC/2016/WebGrass
> Images- first page
> second page
> Module UI
>
>
> Mayank Agrawal Lab for Spatial Informatics IIIT Hyderabad India
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

--
-----
Yann Chemin
Address: 3 Toul Melin, 56400 Plumergat
Mobile: +33 (0)7 83 85 52 34

_______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev