Publishing extension: Project upload to the server

The publishing extension is able to upload to the server any project generated in local.

Visually, the menu is very similar to the publishing tool, except for the fact that all that refers to the generation of the project have disappeared, because it will not generate the definition of any other service, only it will upload an already existing one. Therefore, we need to indicate the local project folder which we want to upload to the server and set the connection parameters.

Advanced options: Server connection by WebDAV

This process of publishing the project generated on the server can be done automatically at the time the project is created, or can be upload after with another tool extension.

In the first case (automatically), you need to indicate the destination address to establish the WebDAV connection. If it is a directory authentication, you must also provide the username and password.

E01_Publish

With all the information provided, the ‘Connect‘ button will check that connection and also it will fill the left menu with the subfolders that exist in the specified path.

Advanced options: Paths

For a correct operation of services, it is necessary that the access to resources are properly defined. To do this, there are three possibilities to define the routes to them:

E02_publish

  • Default paths: This option does not alter the paths to resources, setting them such in the definition files of the different services..

  • Absolute paths: adequate if there is a correspondence between the location of the files on both machines (eg, the shapes are inside a folder called ‘data‘ and have identical directory structure inside), but the access to that folder has different routes on each machine (for instance, local directory is ‘/home/user/data‘ and the server is in ‘/mnt/data‘).

    This option will replace in the configuration, the access paths to the local machine for the server ones.

  • Relative paths: taking as origin the service configuration file (the mapfile if it is MapServer), you can set a route to resources from it using a ShapePath variable.

    From that file and adding the indicated for the ShapePath variable, the rest of the resources accesses will be built.

With this post, we finish with the series dedicated to the publishing extension (view 1 and 2),first add-on released on “On the road to gvSIG 2.2”.

This entry was posted in english, gvSIG Desktop, gvSIG development, testing and tagged , , . Bookmark the permalink.

2 Responses to Publishing extension: Project upload to the server

  1. Pingback: gvSIG Publishing extension: Project upload to the server | Geo-How-To News

  2. Pingback: gvSIG 2.2 available! | gvSIG blog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s