I took a look at this

https://github.com/zeit/now-builders

It seems that it might be possible to write a bulder like @now/jupyter to automatically deploy Jupyter notebooks with a requirements.txt. The questions are:

1. Is your team going to write it?

2. Is it possible for a third party to write it and put in the now.json?

    {
      "version": 2,
      "builds": [
        { "src": "*.py", "@thirdparty/jupyter" }
      ]
    }

Not to speak for @rauchg and the team, but I think the answers are 1: no (or not soon) and 2: yes

I made a proof of concept project to wrap a Jupyter Notebook with Now 1.0 via Dockerfile

https://now-befdojuvlz.now.sh

How could I achieve it in Now.2.0? Should I wrap Jupyter server with a custom gateway index.py? Before I give it a try, I’d like to hear advice from your team.

I don't understand why so many people cling to VMs/containers.

I think you did the right thing

Now v2 requires a fundamental change in how development happens and how the application is architected. It is too prescriptive.

VM/Containers allow people to develop and structure the app however they want, largely decoupled from deployment/infra.

I don't understand how many people have no issue being told to rewrite your apps so they fit inside lambdas...

If they were marketed as different products then there didn't be quite as much panic but since this is V2 and V1 people are afraid that the product they like will be unsupported soon since it's an older version.

Also, while V1 still exists for the time being it is fair to assume that future updates will only apply to V2. One user on here already found this to be true because although a new region was added, GRU, they could not deploy to it with V1 and was told it only supported V2.