I am getting an error relating to copy-webpack-plugin when trying to run make prepare-host:
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient…
npm WARN old lockfile
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: suttacentral@2.0.0
npm ERR! Found: copy-webpack-plugin@4.6.0
npm ERR! node_modules/copy-webpack-plugin
npm ERR! copy-webpack-plugin@“8.0.0” from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! copy-webpack-plugin@“8.0.0” from the root project
npm ERR!
npm ERR! Conflicting peer dependency: webpack@5.24.3
npm ERR! node_modules/webpack
npm ERR! peer webpack@“^5.1.0” from copy-webpack-plugin@8.0.0
npm ERR! node_modules/copy-webpack-plugin
npm ERR! copy-webpack-plugin@“8.0.0” from the root project
npm list copy-webpack-plugin gives;
copy-webpack-plugin@10.2.4
Any suggestions from those who a knowledgeable in this area?
OK, I’ve made a little progress, I just ignored the conflict and ran the production environment so now i have:
Welcome in SuttaCentral environment setup script!
You are going to be prompted for a bunch of information.
If you want to set the value to the random one enter ‘R’.
You will be prompted back with the generated value. eg.
< R
Xu@+$;*ed3||,zfuP7kw%e0!c<`e^PLC
By default
If you want to leave current value just leave the answer blank.
Thanks again Bhante! I got much further than I thought I might this morning, so fingers crossed if i can figure out this webpack/copy-webpack-plugin thing I will be right!
Ok, so another update, I have gotten even further but am still running into problems:
12: Load blurbs from sc_bilara_data
8809 blurbs added or updated
Traceback (most recent call last):
File “manage.py”, line 93, in
manager.run()
File “/usr/local/lib/python3.7/site-packages/flask_script/init.py”, line 417, in run
result = self.handle(argv[0], argv[1:])
File “/usr/local/lib/python3.7/site-packages/flask_script/init.py”, line 386, in handle
res = handle(*args, **config)
File “/usr/local/lib/python3.7/site-packages/flask_script/commands.py”, line 216, in call
return self.run(*args, **kwargs)
File “manage.py”, line 48, in load_data
run(no_pull=no_pull)
File “/opt/sc/sc-flask/server/data_loader/arangoload.py”, line 402, in run
sc_bilara_data.load_blurbs(db, sc_bilara_data_dir)
File “/opt/sc/sc-flask/server/data_loader/sc_bilara_data.py”, line 41, in load_blurbs
db[‘blurbs’].import_bulk(blurbs)
File “/usr/local/lib/python3.7/site-packages/arango/collection.py”, line 2245, in import_bulk
return self._execute(request, response_handler)
File “/usr/local/lib/python3.7/site-packages/arango/api.py”, line 66, in _execute
return self._executor.execute(request, response_handler)
File “/usr/local/lib/python3.7/site-packages/arango/executor.py”, line 82, in execute
return response_handler(resp)
File “/usr/local/lib/python3.7/site-packages/arango/collection.py”, line 2242, in response_handler
raise DocumentInsertError(resp, request)
arango.exceptions.DocumentInsertError: [HTTP 409][ERR 1210] unique constraint violated
make: *** [Makefile:78: load-data] Error 1
Well, in the end I was unable to get the site actually serving me the suttas, but I got heaps further along than I have ever managed before, and I am learning a heap about linux, git, docker, flask, python and all sorts of things so I will take a bit of a pause, regroup and give it another go next weekend.
I’m so excited! I cannot believe how many stupid things I did to prevent myself from actually setting up this environment!! did not have an ssh key, did not give docker group or user permissions, did not put the folder in opt, sudo’d every command, thought that I needed to go to sc-frontend’s container IP and port so wasn’t even looking at local-host, ran make run-dev immediately after running make-preview-env, and then immediately ran make load-data! I think I even ran a couple of the makes in concurrent terminals after mistakenly thinking a process had stalled… sheesh…
Anyway, I guess there where quite a few cobwebs to blow off after not being in web development for more than ten years, but I am very very happy to have gotten this far.
Now I will start to explore Arango and getting my head around elasticsearch and arangosearch and see if I can tinker on my local machine and get familiar!
Well, as I was reading this comment, I lifted up my fresh morning cup of coffee to take the first sip; my thumb slipped a little and hot coffee spilled all over me. So yeah.
That’s awesome. Our engineers love ArangoDB. It’s super-well engineered, robust, and highly capable.
FYI, we aim to replace elasticsearch with ArangoDB search as soon as we can. That will massively reduce our dependencies, and enable us to do kinds of searches that are currently impossible. For example, since ADB understands “segments”, we could search for instances where “dhamma” is translated as “thing”. That’s just not possible in elastic.
Technically it is “segments where ‘thing’ appears in translation and ‘dhamma’ appears in root”. But practically it’ll usually give you instances where dhamma is translated as thing.
