Configuring Nikita Noark 5 Core for remote web access
Petter Reinholdtsen
pere at hungry.com
Sat Jun 10 23:24:32 CEST 2017
[Ole Aamot]
> I am successfully running Nikita Noark 5 Core on a Debian server
> (nikita) and the node.js web service accessed in the Chrome web
> browser on a remote client machine (portable).
Very glad to hear it is working for you. Note, the node.js web service
(on port 3000) is as far as I can tell a simple web server, and you can
use apache or any other web server to service the files under web/ if
you want to.
> diff --git a/web/package.json b/web/package.json
> index 67ec2e0..3bf976f 100644
> --- a/web/package.json
> +++ b/web/package.json
> @@ -14,7 +14,7 @@
> "devDependencies": {},
> "scripts": {
> "test": "echo \"Error: no test specified\" && exit 1",
> - "start": "node server.js"
> + "start": "nodejs server.js"
> },
> "author": "Alexander Alemayhu",
> "license": "TBD"
I believe this is due to the 'node' binary name in Debian already being
used by another package, and thus the javascript engine had to re
renamed to nodejs on Debian.l
> # git clone https://github.com/oleaamot/noark5-parser.git
> # cd noark5-parser
> # ./runparser
>
> Edit /etc/hosts on your Chrome web client and enter the IP-address of
> your Debian server ("nikita"):
>
> # sudo vi /etc/hosts
>
> 192.168.1.102 nikita
>
> In my case 192.168.1.102 is the local network address of my Debian
> server ("nikita").
Why did you have to modify /etc/hosts? I would expect it to work to use
the IP address in the URL?
> You should be able to login with the username 'admin' and the password
> 'password' and navigate and view two example journals imported with
> the noark5-parser in the web GUI.
>
> 2011/230 Byggsaker
> 2012/200 Vei og trafikk
Very cool to see your import working. I look forward to testing it on
larger data sets. :)
--
Happy hacking
Petter Reinholdtsen
More information about the nikita-noark
mailing list