Feature #1839
closed
Collecting the Steps for Windows Setup
Description
The Reason¶
In the process of setting up OpenAtlas on Windows, we encountered some things that need to be done differently from Linux. Should we collect the steps, so that in case we do end up adding a Windows installation guide to the install.md at some point, we already have a base of which to build upon.
Created Documentation¶
See: Windows Installation
Collection of Important Steps (WIP)¶
Install PostgreSQL and PostGIS¶
The download link for the newest PostgreSQL Version Windows installer can be found on [[https://www.postgresql.org/download/windows/]] in the first line under "Download the installer".
Choose the appropriate version and use the installer to install all the needed tools (@Bernhard, I'd need to ask you here again what the steps would be + I'm unsure if you need to install PostGIS separately or if it is included in the installer).
Install ImageMagik¶
Download the newest version from [[https://imagemagick.org/script/download.php#windows]] and install it.
Important: Install the dll version, not the static one!
SetUp with PgAdmin4¶
- Set initial Password
- Set DB Password
- Set up Initial DB
- Creation:
- Right click on Databases then choose Create > Database
- Set name (openatlas)
- Set owner to openatlas
- Save
- Add extensions:
- Right click on created DB > Create > Extension..
- Select "postgis"
- Repeat with "unaccent"
- Creation:
- (optional) Import existing Dataset
Setup process for the tests¶
Installing the required packages:¶
Run the following commands:
- pip install coverage and pip install nose
OR
Uncomment the lines following "# Used for testing" in "requirements.txt" then execute the following command:
- pip install -r requirements.txt
For testing run:nose2 --with-coverage --coverage tests/ --coverage openatlas/ --coverage-report html --pretty-assert --verbose
Updated by Bernhard Koschiček-Krombholz over 1 year ago
- Description updated (diff)
- Status changed from New to Assigned
- Assignee set to Moritz Großfurtner
One important thing is to have Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
Without it, several packages will not be installed through pip (e.g. numpy, psycopg2)
If you install postgresql via the installer, you can choose to use the stack builder tool to install additional extensions. This should be used to get postgis. But there are other ways too. I will test it with a clean installation of Windows.
I think we will also need to adapt the requirement.txt to newer packages.
Updated by Alexander Watzinger over 1 year ago
- Tracker changed from Question to Feature
- Status changed from Assigned to In Progress
- Target version set to 7.12.0
This is a great idea, I can't do it myself (not a Windows user) but would appreciate if you could share your installation experiences. I created a Wiki page, copied some of the text from here: Windows_installation. Feel free to continue there and of course all other Windows user are welcomed to join the effort.
Updated by Moritz Großfurtner over 1 year ago
Updated it again. @Bernhard, do you have a plan when you will test it with a clean windows version, maybe I can sit next to you then and document the process?
Updated by Bernhard Koschiček-Krombholz over 1 year ago
Sure, this would be great. I will write to you in Mattermost.
Updated by Moritz Großfurtner over 1 year ago
- Status changed from In Progress to Closed
Updated by Alexander Watzinger over 1 year ago
- Status changed from Closed to Resolved
- Target version changed from 7.12.0 to 7.9.0
Thanks a lot for taking care of this. Sorry but I somehow missed, that this issue was closed 3 days ago.
It's better that when closing an issue with a target version to move it to the next upcoming version. That way I won't miss it.
Anyway, since I just released 7.8.0 it would be awkward to move it there now.
Also I'm not sure if this specific issue belongs on the roadmap. It really depends, e.g. if it is reflected in the OpenAtlas code it should. If it is "just" documentation (not visible in manual or application) it should be copied somewhere to the Wiki (documentation in issues would be hard to find) and the target version should be empty.
So options would be:- In the Redmine wiki (without target version)
- As a .md file in the OpenAtlas repository
- As an entry in the Sphinx application manual
So I set it to resolved for now and kindly ask for feedback on this.
Updated by Moritz Großfurtner over 1 year ago
- Description updated (diff)
- Target version deleted (
7.9.0)
Updated issue description to include Link to Wiki site with the set up steps.
Updated by Alexander Watzinger over 1 year ago
- Status changed from Resolved to Closed
Thanks a lot, closing issue.