-
Notifications
You must be signed in to change notification settings - Fork 13.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Static assets not resolving #226
Comments
Hi, |
Did you follow the instructions here? |
Yes, I ran both. It's really strange as the file it's complaining about exist in the directory as expected. The link is hardcoded in the codebase to: '/static/assets/javascripts/dist/css-theme.entry.js'. This file does exist in the given location. |
I went to the file: basic.html, deleted it's content, and re-run the application. It still worked, which is unexpected. So, there's something that I'm missing. Modifying any file has no effect. This is probably just something fundamental to flask that I'm missing. Any help appreciated. |
I installed the caravel package as well as forked the code. I wanna run the forked code. However, according to the documentation, to run the code you do: caravel runserver -d. This doesn't seem to be running the source code. I'm not very familiar with flask, so some enlightenment would help here. |
Looks like you're running multiple installs |
@mistercrunch thank you. I ended up running it from the build directory, but good to know this. |
I actually have the same problem and not running multiple installs for sure. The javascripts/dist/ files are there after running
in the assets folder and yet the response back for anything in the assets/dist/ is a 404. |
Though I'm new to the Flask project setup, I think I have everything setup properly. When I run the app, I don't get the css theme due to being unable to reference the file: /static/assets/javascripts/dist/css-theme.entry.js. This file does exist in that location, but the browser can't seem to resolve it. Any help highly appreciated.
The text was updated successfully, but these errors were encountered: