Opened 5 years ago

Closed 21 months ago

#165 closed task (wontfix)

Specify rasimport connection on the command-line

Reported by: pcampalani Owned by: abeccati
Priority: minor Milestone: 9.0.x
Component: rasgeo Version: 8.3
Keywords: Cc: pbaumann, herziga@…
Complexity: Very Hard

Description

Currently rasimport creates and refers to a file called connectfile for configuration.
This file — see <rasdaman_install>/applications/rasgeo/README — is created with make connectfile and is saved into $HOME/.rasdaman/ by default.

Configuration files of rasdaman and all its applications should be harmonized into the etc folder.

Change History (6)

comment:1 Changed 5 years ago by dmisev

  • Cc pbaumann added
  • Version set to 8.3

We have discussed this previously, and decided it's better if it goes in .rasdaman.

It's a client application, and it doesn't make sense it's configuration to go to the server directories.

So it's configuration should be either local to the user, or as is the case with rasql it should be specified with command-line options every time.

comment:2 Changed 5 years ago by dmisev

  • Summary changed from rasimport configuration to be moved in rasdaman `etc' folder to Specify rasimport connection on the command-line

To not get it lost:

In my opinion it would be best to get it in sync with rasql, i.e. make it possible to specify the connection details on the command line.
If nothing is specified, then it could still look in the .rasdaman/rasconnect, if it exists. We could get rasql to work this way too, to make them consistent.

Postgres psql for example works like this, you can specify credentials in ~/.pgpass, or in some environment variables PGDATABASE, PGHOST, PGPORT and/or PGUSER, as the defaults.

comment:3 follow-up: Changed 5 years ago by dmisev

  • Cc herziga@… added

comment:4 in reply to: ↑ 3 Changed 5 years ago by herziga@…

rasimport provides the --conn parameter for passing a file with connection details as in rasconnect.

comment:5 Changed 5 years ago by pbaumann

  • Milestone set to 9.0
  • Owner set to abeccati
  • Status changed from new to assigned

to be chacked: are user, password etc. also handled this way? see rasql utility for comparison.

comment:6 Changed 21 months ago by dmisev

  • Complexity set to Very Hard
  • Resolution set to wontfix
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.