Open JoeKage opened 3 weeks ago
jacobtylerwalls
commented
3 weeks ago Hi @JoeKage. AfS does not yet support the latest alpha of Arches 7.6. Support is pending in #1570. One major thing to note is that 7.6 removes yarn as the front-end package manager. See the in-progress version of the Arches 7.6 release notes for more information.
Some sanity commands to completely remove your front end packages and rebuild them:
rm -rf node_modules
rm package-lock.json
npm i
JoeKage
commented
2 weeks ago Hi @jacobtylerwalls , thanks for your reply!
That helped my understanding quite a bit, since I was working with outdated setup instructions. Sadly, the error persists, but if support is still pending, there's no real reason to force it together right now, I think. Especially since there are updated requirements like node 20 which I did not at the time have. So it's probably best for me to wait until AfS support is reestablished.
Afterwards, I tried to install AfS with
pip install arches==7.6.0a1
and after
yarn add -D eslint-webpack-plugin
since, at that point yarn was probably still in, judging from the main AfS installation instructions and
(naively, and perhaps wrongly) rewriting a line in webpack.common.js to
new BundleTracker({ path: __dirname, filename: 'webpack-stats.json' }),
I got to a place where I got the essentially same error as before -- but I guess I'm really mired up in different commit versions right now and also am not sure how much I'm breaking with wild, uninformed hacks. I also don't really see the point in spending a lot of time trying to get an old version based on an outdated alpha online, so I'll probably stop trying at this point and wait a bit.
Thanks again for your help!
Hi,
I've been trying to install AFS from scratch for some time now, but seem to fail at the last step, somewhere at yarn build_development.
My current setup is the following:
Debian 12.5, which is not Ubuntu but I hope it's close enough, especially since node and yarn are installed from the same sources as they would be on Ubuntu. Prerequisites via docker-script that flew around somewhere here or in the main arches github, maybe a little tweaked but it seems to work fine now.
I start with the Arches Install as normal:
As far as I can tell, everything here seems normal. Then I proceed to the AFS-documentation by changing the settings.py file as seen on https://github.com/archesproject/arches-for-science/tree/dev/1.1.x , with the two added lines in settings.py:
archesfs/archesfs/settings.py archesfs/archesfs/urls.py archesfs/package.json
% python manage.py packages -o load_package -a arches_for_science -dev -yFrom what I read now is the best time to build the Database because all the migrations and additions from AFS already exist, so:
% python manage.py setup_dbAfterwards:
In another tab:
%source venv_arches/bin/activateGoing in the directory with package.json, which is not $PROJECT_NAME/$PROJECT_NAME/ in my case, but $PROJECT_NAME, where manage.py exists but settings.py doesn't:Now to the build:
So this fails with these problems and my understanding of frontend-stuff and node in particular is by far not enough to understand it. I can see that the template files are being collected from Django though.
Here is my node_modules folder if it helps:
I can also provide more files about the afs install process as well as the rest of the build_development errors which are another 1100 lines of errors, but it reads to me like a node/yarn/js problem, so I'm not sure if the database state is relevant here. I've been stuck at this problem for quite a while and would really appreciate any help or pointers in the right direction.