Spectrum is now read-only. Learn more about the decision in our official announcement.


Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.


clarify future support of docker on now platform

November 8, 2018 at 6:21pm
The ZEIT community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

clarify future support of docker on now platform

November 8, 2018 at 6:21pm
It seems zeit is moving away from allowing customers to utilize Docker as a common 'primitive'; would you kindly clarify this?
Show previous messages

November 9, 2018 at 8:40pm
But that's when you start to realize that the whole enterprise of running things on premise will make little sense.
So deploying a Python Flask app with multiple endpoints will be possible without Now-specific changes?
Between the option of being paged at 3am to restart a server
Or things running quickly on-demand and paying no maintenance costs
The equation becomes quite simple.
that's what we are working on right now
In fact, we are doing that because we want to welcome more devs to our platform
But anyone today could be writing a flask wrapper
How would I go about deploying a "traditional" express server with non filesystem-based endpoints?
I legit just recently switched my NodeJS app to use Docker because that's the advice I was given by the team here when I didn't want to use yarn to install my packages. Now I have to switch to something else?
I feel your pain, I just did that this last week
, It's not recommended because you lose most of the benefits, but you can run your node or express server as a lambda using the now-node-server builder
I tried that, it just shows a directory listing with "src", and I open it, it errors with Internal Server Error
What Zeit should realize is that I'm well willing to accept the tradeoff of having an app that is up 24x7 consuming resources (e.g., Docker-style NodeJS app) and paying a few more dollars/cents if that means I don't have to write code like this. In other words, the need for serverless isn't a problem I currently have. I understand that it's more efficient, but those benefits only make a material difference for really large applications.
If I have a low-traffic app, the serverless model vs docker isn't going to make a ton of difference. I'm already only paying $15 a month. Price isn't a top concern.
Getting an out-of-the-box wrappers for Flask apps would be awesome, but I can also see how it can be done manually, now, that you mention it. I totally agree with your arguments in favor of serverless deployment. I'm thinking of the many companies that cannot (for some data privacy reason or other political reason) deploy on Now or even big cloud providers and for those we need to be able to offer on-premise deployment. But we wouldn't want to write an app twice - one for deployment on Now and one for on-premise deployment. A wrapper sounds like a good compromise, at least for some/many scenarios.
As a developer, I believe in your vision, and have benefitted from the sometimes swift learning curves Now has introduced. All I can say is: damn, Man, keep up the great work! I embrace the new model despite the additional work because I know you've put a lot of time and thought into what's going to work more permanently moving forward. I know Lambdas is a once in a generation technological shift now, and I wasn't sure about that until this announcement. Next with React 16.7 is awesome. Love what you're doing. Keep it up!
Looking at the npm page for now/build-utils,
There is no README or even a link to a GitHub repo.
Good find! We have to improve that
Also, is it possible to deploy an app using puppeteer?
It seems it would exceed the 5MB limit.
How are websocket connections going to work on a serverless architecture? I currently send real-time updates (via websockets) to my clients, which is a really important feature of my application.
Show more messages