setup.cmd for windows environment

teksi / district_heating

Future TEKSI distance heating module

GNU General Public License v3.0

0 stars 0 forks source link

setup.cmd for windows environment #7

Closed sjib closed 1 month ago

sjib commented 1 month ago

Please note that we work in a windows environment and I had to copy the setup.sh (for linux environment) to setup.cmd. I do not know if this environment must be taken into account for TEKSI users according to the product strategy. If not, this would be an advantage.

_Originally posted by @sjib in https://github.com/teksi/distance_heating/issues/1#issuecomment-2110255021_

sjib commented 1 month ago

@jpdupuy send windows script

jpdupuy commented 1 month ago

@sjib I am still working on it. I cannot find the correct syntax to invoke psql with the pgservice. I try to figure out the correct syntax to avoid to enter the password for each psql execution. I currently have to enter the password since I had to setup the host, port and dbname.

jpdupuy commented 1 month ago

The setup_windows.cmd needs some review since I do not know how to convert the 2 following commands :

PGSERVICE=${PGSERVICE:-pg_tdh}
DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )/.. by
set DIR=%CD%
set PGSERVICE=sitecom_edit_dev_service The setup_windows.cmd uses the setup_windows_sql_script.txt (list of psql scripts to import and execute) in order to call only once PSQL

TEKSI_CAD.zip

sjib commented 1 month ago

psql -U %user% -p %port% -d %db% -h %host% -f 060_dss_interlisimport2-halt.sql> 060_2haltuae.log 2>&1