menu

ZEIT

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

Channels
Team

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 9:26pm
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!
like-fill
5
  • reply
  • like
Looking at the npm page for now/build-utils,
  • reply
  • like
like-fill
1
  • reply
  • like
There is no README or even a link to a GitHub repo.
like-fill
1
  • reply
  • like
Good find! We have to improve that
like-fill
1
  • reply
  • like
Also, is it possible to deploy an app using puppeteer?
  • reply
  • like
It seems it would exceed the 5MB limit.
  • reply
  • like
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.
like-fill
3
  • reply
  • like
Regardless websocket connections, i prefer something like Pusher.js for the architecture and API for all platforms.
like-fill
1
  • reply
  • like
we'll definitely make that possible. We have many super interesting use-cases for it in mind
  • reply
  • like
Also, in response to feedback here about finding the v1 plans, the great just shipped an improvement:
  • reply
  • like
  • reply
  • like
I meant it when I wrote in the blog post that my main priority is to address all the customer workloads perfectly.
My usecase requires docker so 🤷‍♂️.
  • reply
  • like
What I don't need is yet another external service for my application to depend upon. What I need is an always-on NodeJS application instance (minimum 1, with the ability to scale as needed) that can handle persistent websocket connections -- unless I'm mistaken and the new architecture will support this.
  • reply
  • like
what happens when you use v1 apps on a v2 plan?
like-fill
1
  • reply
  • like
What i mean is looking at Pusher.JS as a successful real-time story to learn from. So we could utilize something like that right from Now v2 !
  • reply
  • like
seems like you're billed on-demand
  • reply
  • like
$0.025/hr
  • reply
  • like
oh yikes, I'll need to downgrade then...
  • reply
  • like
I tried, there doesn't seem to be a way to do that
  • reply
  • like
Gotcha. I suppose then it'd be another proprietary module I'd have to import that would only integrate with Zeit's cloud.
  • reply
  • like
yeah just discovering that too -- that's super concerning. , is there a way to downgrade to a legacy plan? I'm not able to deploy any of my apps to v2 and am now going to be paying $18 per month per deployment
  • reply
  • like
I wonder how many users that upgraded, don't know about this forced on-demand billing and will get a >$50 bill on a supposedly $15 plan
  • reply
  • like
we have a very clear disclaimer on the modal
  • reply
  • like
please email [email protected] and we'll take care of it, no stress
like-fill
1
  • reply
  • like
Show more messages
private
This conversation has been locked
private
This channel has been archived