Father by day, hacker by night.
You should launch
docker-compose upat the root of the project. I do not know an other way of doing that. Do you have defined some volumes?
It is totally normal that there is a
newspipedirectory in it. It's quite classic in Python (especially if you use Poetry or even with Flask).
It works for me. This is the output I had when npm is installing the JS dependencies in the container:Step 15/19 : RUN npm install ---> Running in 7bcf7b0a5e30 npm WARN lifecycle firstname.lastname@example.org~postinstall: cannot run in wd email@example.com cd newspipe/static/ ; ln -sf ../../node_modules npm_components (wd=/newspipe) added 9 packages from 16 contributors and audited 12 packages in 8.66s 2 packages are looking for funding run `npm fund` for details found 0 vulnerabilities Removing intermediate container 7bcf7b0a5e30 ---> 31ab044896e1 Step 16/19 : RUN mkdir -p newspipe/static/npm_components ---> Running in 2177f6523f57 Removing intermediate container 2177f6523f57 ---> 40165bdf267b Step 17/19 : RUN cp -R node_modules/* newspipe/static/npm_components/ ---> Running in fbe44adf0ce5 Removing intermediate container fbe44adf0ce5
Did you try from scratch (with a new container)?
Thanks, I am checking that with a new container.
Thank you for the report. The issue is fixed. I am testing it right now.
The problem has been introduced recently with Flask-Talisman. In the configuration file of the Flask app DEBUG must be set to True, else it will force the use of HTTPS.
It should be fixed now: https://git.sr.ht/~cedric/newspipe/commit/2a9176fb233e7816cde43fd92903952e6ca3dfd2