Difference between revisions of "Windows 10 PKC Installation"
Line 19: | Line 19: | ||
===GNU TAR might not work=== | ===GNU TAR might not work=== | ||
We found that tar command may not work on certain machines. Therefore, we put a file <code>unzip.exe</code> in the <code>resources</code> directory. We also made sure that a initial data package, namely mountPoint.zip is included in the <code>resources</code> directory, so that the <code>up.bat</code> script will be able to conduct the automatic installation and initial launch process completely. | We found that tar command may not work on certain machines. Therefore, we put a file <code>[[unzip.exe]]</code> in the <code>resources</code> directory. We also made sure that a initial data package, namely mountPoint.zip is included in the <code>resources</code> directory, so that the <code>up.bat</code> script will be able to conduct the automatic installation and initial launch process completely. | ||
=Kick off the microservice launch process= | =Kick off the microservice launch process= |
Revision as of 05:29, 21 August 2021
For Windows 10, you need to use Command Prompt.
Download PKC to your local machine
Once you had Git and Docker installed on your Windows 10 machine, you may launch Command Prompt and see the following prompt:
C:\Users\userName\Workspace>
Download the entire package using the git
command. You may copy the instruction (after the >
sign) as follows:
C:\Users\userName\Workspace>git clone https://github.com/benkoo/PKC.git
Caveats
Thanks to Mitch Altman, he identified the following scenarios for PKC installation on Windows 10, which indicate that Windows users will face many unexpected problems during installation, the following lists are some important ones.
Choosing adequate directories
Make sure that you don't pick a directory outside of your usual Users/Documents directory. If you choose some directories outside of your User/Documents directory, it is possible that certain batch script commands will stop to work, due to file right access authority issues.
GNU TAR might not work
We found that tar command may not work on certain machines. Therefore, we put a file unzip.exe
in the resources
directory. We also made sure that a initial data package, namely mountPoint.zip is included in the resources
directory, so that the up.bat
script will be able to conduct the automatic installation and initial launch process completely.
Kick off the microservice launch process
- After the
git clone
instruction copied relevant data to your working directory, using the commandcd
to the PKC directory that contains the scriptup.sh
, and type:up.sh
to execute the script. Note that Windows 10 requires the script command to beup.sh
, not./up.sh
.
C:\Users\userName\Workspace>cd PKC C:\Users\userName\Workspace\PKC>up.sh
- After you submitted the
up.sh
in your command prompt, you will need to launch one more command to make Semantic MediaWiki work properly. - Depends on your network connection, this process will download around 3GB of data, so that it will take a while.
Copy and paste the following command to your command prompt.
docker exec pkc_mediawiki_1 php /var/www/html/maintenance/update.php
- It will first wait for 5 seconds before updating content in the database, so that the whole process will take up to a minute to finish.
- Open a browser: type the following URL to the browser's URL field: http://localhost:9352.