Moved the admonition text for gettext to the top of the section so that a user can see that installation of this utility is optional before they get to the installation instructions [skip ci]. Refs issue #728
@David Platten have you been able to make any progress with the windows in-place upgrade docs?
@Ed McDonagh I set up a 0.10 test system on Windows, and then upgraded it in-place to 1.0, following the existing upgrade docs. It all worked, but the documents are a little clunky, and are missing information on how to clean up the 0.10 bits that are no longer required.
@David Platten should the 728 branch be pulled in? I think it should?
A note for me to update the Windows docs:
I updated my test system yesterday so had to add Huey workers. The services created by the queue-init.bat refused to run - they tried to start, and then immediately failed. I examined the log files and found that the failures were due to my non-standard installation location for python and the OpenREM code. I had to edit the queue-init.bat file and change these two lines to make them reflect my setup:
I then ran queue-init.bat again and the new services were successfully installed and were able to start.
I had a further problem in that imports for incoming DICOM objects failed. The task page helpfully stated that this was due to a permissions issue with the folder that Orthanc was putting the files in. I had to give the IIS_IUSRS Windows user permission to write and modify the orthanc\dicom folder. After I had done this the imports worked.
Updated section on creating a Windows user to run the Huey workers. Corrected the .bat file to reflect default locations of python.exe and manage.py. Refs issue #728
Another question @David Platten - do you get warnings when importing a database in Windows? I’m going to merge in issue939installdocs branch and in the linux install page in the database import box there is an example of an expected error message. I have a comment in the Windows version but no example. Do you have one?
When running the restore command as written in the docs I get an error about the database not existing:
C:\Users\dplatten>"c:\Program Files\PostgreSQL\15\bin\pg_restore.exe" --no-privileges --no-owner -U openremuser -d openrem -W d:\Temp\2023-03-09_0832_OpenREMdatabase.backupPassword:pg_restore: error: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: database "openrem" does not exist
After a Google search, it turns out that I need to specify the -C option, and use -d postgres. That then gives the following, complete with the errors about the public scheme already existing:
C:\Users\dplatten>"c:\Program Files\PostgreSQL\15\bin\pg_restore.exe"--no-privileges--no-owner-Uopenremuser-C-dpostgres-Wd:\Temp\2023-03-09_0832_OpenREMdatabase.backupPassword:pg_restore:error:couldnotexecutequery:ERROR:schema"public"alreadyexistsCommandwas:CREATESCHEMApublic;pg_restore:error:couldnotexecutequery:ERROR:mustbeownerofschemapublicCommandwas:COMMENTONSCHEMApublicIS'standard public schema';pg_restore:error:couldnotexecutequery:ERROR:mustbeownerofextensionplpgsqlCommandwas:COMMENTONEXTENSIONplpgsqlIS'PL/pgSQL procedural language';