CSS assets do not seem to load when running in PyCharm

[brylie]

I notice the bootstrap.min.css and custom.css files in the slapdash/assets folder, along with FontAwesome. However, these assets do not seem to load when running the app:

When I navigate to the /assets route in the browser, it says "no page '/assets'".

I ran the project in PyCharm by running the run_flask.py file after installing slapdash in the virtual environment.

[ned2]

Could you try running it from the command line without PyCharm? I've seen issues previously about Dash infrastructure breaking when run through IDEs.

[brylie]

Sure. FWIW, I am able to run 'regular' Dash project(s) via PyCharm.

[ned2]

Ah ok. I'll try and run Slapdash in PyCharm and see if I can work out what's going on.

[brylie]

The CSS loads fine when I follow these steps:

1. clone repo
2. cd to repo root
3. run pipenv install then pipenv shell
4. run pip install -r requirements.txt
5. run pip install -e .
6. run ./run_flask.py
7. open URL in browser

[brylie]

I will also test using the WSGI approach described in the README.

[brylie]

Woohoo! The 'package-less' approach works with the following, somewhat convoluted, steps:

1. clone repo
2. cd to src
3. run virtualenv venv
4. run source venv/bin/activate
5. pip install -r ../requirements.txt
6. pip install dash-core-components
7. pip install dash-html-components
8. gunicorn slapdash.wsgi
9. open URL

I somewhat prefer this approach, were the requirements.txt to be in the src directory and include the dash-core-components and dash-html-components.

[ned2]

Great :) I'm curious, any reason(s) in particular why you prefer to not install it as a package? Yeah, that's the catch; I don't want to maintain two separate lists of dependencies that then both have to be synchronised for package and non-installation of dependencies. One thing I've seen projects do is to have `setup.py` programatically extract the list of dependencies from a separate `requirements.txt` file.

…

On Wed, 31 Oct 2018 at 01:22, Brylie Christopher Oxley < ***@***.***> wrote: Woohoo! The 'package-less' approach works with the following, somewhat convoluted, steps: 1. clone repo 2. cd to src 3. run virtualenv venv 4. run source venv/bin/activate 5. pip install -r ../requirements.txt 6. pip install dash-core-components 7. pip install dash-html-components 8. gunicorn slapdash.wsgi 9. open URL I somewhat prefer this approach, were the requirements.txt to be in the src directory and include the dash-core-components and dash-html-components. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACs1GHxmHr6tq4Uo7fsbRXfzNb82V6wXks5uqGCPgaJpZM4X-1NL> .

-- nedned.net

[brylie]

Well, I am just thinking it could be easier for a new developer to simply run

1. pip install -r requirements.txt
2. python app.py or something similar,

rather than

1. pip install -r requirements.txt
2. pip install -e .
3. python run_server.py, which is somewhat ambiguous.

Otherwise, this is so new to me I haven't formed a richer opinion.

[ned2]

Not sure if it makes any difference, but you don't actually need the `pip install -r requirements.txt` in the current set up. That's just for development purposes, but not really used. I should probably remove it.

…

On Wed, 31 Oct 2018 at 01:29, Brylie Christopher Oxley < ***@***.***> wrote: Well, I am just thinking it could be easier for a new developer to simply run pip install -r requirements.txt && python app.py or something similar, rather than pip install -r requirements.txt && pip install -e . && python run_server.py, which is somewhat ambiguous. Otherwise, this is so new to me I haven't formed a richer opinion. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACs1GCq5AjDY8XzJC33lGKgKkYZknTdfks5uqGJfgaJpZM4X-1NL> .

-- nedned.net

[brylie]

Ah, thanks for clarification.

[ned2]

I can't replicate the issue, running run_flask.py with PyCharm 2018.2.4 (running on Ubuntu 18.10). What OS are you running on?

Note that /assets is not exposed as a route, only the direct routes to the assets themselves, so that is actually expected, even when the CSS files are being picked up correctly.

Maybe also check that you have the latest Dash installed.

[ned2]

Closing this for now

[drewes]

Sorry for coming late to the party. Have the same issue on MacOS with PyCharm 2018.3.

Would prefer to install it as a package.

Tried the following from the command line after cloning repo:

1. mkdir venv
2. python3 -p python3 venv
3. source venv/bin/activate
4. pip install -e .
5. python run-flask.py --debug

Server starts. Assets don't seem to load.

Any suggestions?

[drewes]

Managed to solve it by passing __name__ into the Dash instantiation in your create_dash(server) function.

@ned2 Any advice on best practice? I assume related to your post plotly/dash#198.

[ned2]

Oops, good catch!

It used to be that Dash would take the name parameter from the Flask instance if one was passed in as through the server parameter, but that was removed with plotly/dash#547 to decouple the Dash instance from the Flask instance, in case multiple Dash instances (potentially in different directories) are configured to use the same Flask server. I forgot that slapdash was relying on this behaviour.

This is now fixed in 75f443c

Thanks!

[drewes]

Thanks for your library! Has helped us tremendously.

[ned2]

Wonderful to hear :)