Converting some existing code from another project over into slapdash, it seems like Input('url','pathname') cannot be used?

Am I missing something? ...Is there another way to use the url in a callback?

@app.callback(Output('api-connections', 'children'),
              [Input('submit-settings-button', 'n_clicks'),
               Input('url','pathname')])
def update_api_connection_status(n_clicks, pathname):
    if n_clicks and n_clicks > 0:
        print(pathname)
        return html.Div(children=[
            html.Div(className='twelve columns', children=[check_oura_connection()]),
            html.Div(className='twelve columns', children=[check_strava_connection()]),
            html.Div(className='twelve columns', children=[check_withings_connection()])
        ])

Slapdash is setup to use the Flask instance's config object to store Dash parameters. These are updated after Dash.init is called, so that they are safe to be used at runtimem via Flask's convenient current_app global. This means we can access Dash config without having to worry about import order

Hey! This is an amazing example and I have been finding it super useful. But I'm looking for each page to have their own subpages. How would I go about that using your infrastructure?

Thanks!

Slapdash is great! Thanks for making this, and for all your other work on Dash.

I'm pretty new to Flask but I've figured out how to implement login, registering, etc. in basic Dash+Flask using flask-login. But in Slapdash it's not super clear to me how I can implement my own functions for login, logout, etc. and use extension decorators - for example, to protect certain pages with @login_required but leave others open (e.g. a public blog for a private product).

How would I go about doing that? Explanations and links appreciated equally.

Hey @ned2 - first off thanks for this amazing repo, it has helped me organize my own project substantially.

I'm working on a project that would let users self-host an analytical fitness application:
https://github.com/ethanopp/fitly

I'd like to add the ability for the users to be able to deploy via docker, and I currently have it working with the following docker-compose, but saw some benefits in your readme on using the apache prod script instead of an external (gunicorn in this case) server:

version: '3'
services:
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt 
    cap_add:
      - NET_ADMIN
    restart: always
    ports:
      - "80:80"
      - "443:443"
    environment:
      - PUID=1000
      - PGID=100
      - TZ=America/New_York
      - EMAIL=<your email>
      - URL=<website.com>
      - SUBDOMAINS=fit # this would give a website like fit.website.com
    volumes:
      - /share/CACHEDEV2_DATA/Container/LetsEncrypt:/config
  fitly:
    build:
      dockerfile: Dockerfile
    container_name: fitly
    restart: always
    depends_on:
      - letsencrypt
    ports:
      - "8050:80"
    environment:
      - MODULE_NAME=src.fitly.app
      - VARIABLE_NAME=server
      - TZ=America/New_York
      - TIMEOUT=1200
      - PUID=1000
      - PGID=100
      - DASH_DEBUG=true
    volumes:
      - /share/CACHEDEV2_DATA/Container/Fitly-Slap/fitness.db:/app/fitness.db
      - /share/CACHEDEV2_DATA/Container/Fitly-Slap/config.ini:/app/config.ini
      - /share/CACHEDEV2_DATA/Container/Fitly-Slap/log.log:/app/log.log
      - /share/CACHEDEV2_DATA/Container/Fitly-Slap/gunicorn_conf.py:/gunicorn_conf.py
      - /share/CACHEDEV2_DATA/Container/LetsEncrypt/keys:/app/keys

where fitly is built on the following Dockerfile:

FROM tiangolo/meinheld-gunicorn:python3.7
LABEL maintainer="maintainer"
RUN git clone https://github.com/ethanopp/fitly.git
RUN pip install -U pip && pip install -r ./fitly/requirements.txt
RUN mv ./fitly/* /app/ && rm -rf ./fitly
ENV NGINX_WORKER_PROCESSES auto

Would you happen to have any docs on how to get a docker container stood up which leverages the run-slug-prod script in your repo? Also just in general, is it worth it to switch over towards leveraging that approach or given that the users will most likely just be pulling the repo and deploying (not editing prod_settings, etc.), is the above okay?

Can then make it a CLI script for the slapdash package

Love the boilerplate mate! Keep up with the good work.

I am trying to implement one of the datatables (via import dash_table_experiments ) but they do not seem to work. Take the code from this example:

_pages.py_

import dash
import dash_core_components as dcc
import dash_html_components as html
import dash_table_experiments as dt

import pandas as pd
import json
import pandas as pd
import plotly

from .components import Col, Row

page1 = html.Div([
    dt.DataTable(
        id='datatable',
        rows=[
            {'x': 1, 'y': 3},
            {'x': 2, 'y': 10}
        ],
        columns=['x'],
        filterable=True,
        filters={
          "x": {
            "column": {
              "sortable": True,
              "name": "x",
              "filterable": True,
              "editable": True,
              "width": 673,
              "rowType": "filter",
              "key": "x",
              "left": 673
            },
            "filterTerm": "2"
          }
        }
    ),
    html.Div(id='content')
])

_callbacks.py_

@app.callback(Output('content', 'children'), [Input('datatable', 'filters')])
def display_filters(filters):
    return html.Pre(json.dumps(filters, indent=2))

When I run this, I not seem to get any errors but it doesnt display the table as it should. Could you perhaps have a quick look?

Events are being phased out from Dash. Need to remove the various references throughout Slapdash to them.

Probably?

Rather than just providing Row and Column, by including dash-bootstrap-components, you could provide a default sidebar layout or something like that.

People starting out with Shiny tend to get shown nice bootstrap layouts in the getting-started guides, so it has more of a wow factor for beginners.

Hi @ned2, I appreciate this is issue might be related to #27 but the error is a bit different and I'm not sure it's related. Apologies if this is an error related to my system (Windows 10 pro, Python 3.8.3) and not slapdash.

I ran almost exactly the same commands as chubukov:

python -m venv slap_env
slap_env\Scripts\activate
python -m pip install cookiecutter
cookiecutter https://github.com/ned2/slapdash
python -m pip install -e slapdashed_app/

I can run-slapdashed_app-dev fine but if I try to run-slapdashed_app-prod I get this error, which seems odd:

'run-slapdashed_app-prod' is not recognized as an internal or external command, operable program or batch file.

Adding the path to my environment variables, which is what I'd normally do, doesn't seem like the right solution to me. I've read through your readme file but I feel like I'm missing something.

Slapdash comes with some round-trip tests to verify that the cookiecutter recipe, when baked, will successfully create a functioning Dash app and eg its multi-page routes work.

The recipe should be enhanced so that after baking your app, it comes with analogous smoke tests so that you can verify your app at least runs and all expected routes are accessible.

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.

great project.

Getting set up was tricky, partly because the readme is incorrect.

Installing this package into your virtualenv will result into the run-slapdash-dev executable being installed into the same virtualenv.

the script is called run-<project-name>-dev . the same for prod.

Also, maybe its because I'm running pyenv or virtualenvwrapper, but the virtualenv exists in ~/.virtualenvs/<venv-name> and therefore running the command takes extra steps - either type the path to the venv, or add my venv to PATH.

Your instructions mention to update slapdash.py, but it doesn't exist in the source code.

The Slapdash project is very nice for getting started quickly. However, it might be useful to document some of the design decisions that went into the project structure. For example, how does the file structure allow callbacks to be separated into their own file? The monolithic file structure of default Dash apps is of shared concern, and it is particularly difficult to separate out callbacks.

The router now accepts callables for layout values. These callables take a single argument which is a werkzeug.datastructures.MultiDict containing the parsed URL query parameters (eg the things after the '?' in pathname?param1=foo&param2=blah)

Need to document this

This many not be an issue or belong here, but I was wondering if you can help in documenting how one can deploy this to Heroku

Hi,

This is fantastic and perfect for our needs. One challenge I am having (with Dash in general) and hoping there might be a way to address it as part of a config or set up parameter: Flask's default behaviour is to keep the server running when a Python exception is raised. You then get to see the exception in the browser. For some reason, Dash's Flask blueprint does not do this and the server process terminates. Any ideas on how to "fix" this? As a Python newbie, I would tend to make more mistakes in development than most. Having to restart the server every time I hit a syntax or other soon becomes very onerous.

I must be doing something wrong during installation. I set up a virtualenv and then followed all the commands, with defaults when prompted. I can get run-slapdashed-app-dev to work fine, but when I try to run run-slapdashed-app-prod I get ModuleNotFoundError: No module named 'slapdash' (and also mod_wsgi errors). Also, I don't see any reference to project_slug.wsgi as mentioned in the docs.

Here's exactly what I did:

python3.6 -m venv slap_env
slap_env/bin/python -m pip install cookiecutter
slap_env/bin/cookiecutter https://github.com/ned2/slapdash
slap_env/bin/python -m pip install -e slapdashed_app/

Out of the box, a dynamic multi-page app like Slapdash requires callback validation to be turned off as callbacks will need to be defined that don't yet exist in the layout. the Dash docs have an example in the section titled "Dynamically Create a Layout for Multi-Page App Validation" that show how you can not suppress callback validation.

Needs more investigation

Introspect the available kwargs for Dash.__init__ and only take valid params from server.config into the init

Slapdash is great for developing my Dash app.
Unfortunately, I am too much of a newbie to get slapdash working with waitress, on Windows 10 and Mac OSX.
I tried to point to the wsgi.py file.
I suppose I have to import waitress there, but I don’t know how.
Can you help me with that?

Best regards, Rob

The README says to install slapdash with the command pip install -s .. However, that command gives an error:

no such option: -s

Environment

pip version: 18.1