v3.0 Release Schedule - Details

[superhawk610]

Goals

The UI will be rewritten in React + TypeScript + Apollo Client.

The backend will be rewritten with Apollo Server + TypeScript.

The data layer will use SQLite instead of Mongo to facilitate simpler deploys.

Progress

You can track progress on the master branch. The latest stable version will remain available on the v2.x branch.

• UI
  • [x] skeleton
  • [x] channels
  • [x] devices
  • [x] push alerts
  • [x] takeovers
• Requested Features
  • [ ] tags
  • [ ] variable page zoom
  • [ ] CORS access warning
  • [x] configuration UI
  • [ ] authentication
  • [ ] force clear page cache
  • [ ] variable channel timing
• Backend
  • [x] skeleton
  • [x] device scanning
  • [x] GraphQL resolvers
  • [x] data layer interface
  • [x] X-Frame-Options proxy
  • [ ] rotation timer
  • [x] switch from mdns to multicast-dns
  • [x] patch protobuf vulnerability upstream (tracking in https://github.com/superhawk610/node-castv2/issues/1)
• Data Layer
  • [x] skeleton
  • [x] sandbox mode w/ seeds
• Misc
  • [ ] README rewrite
  • [x] common location for config/sqlite files (~/.multicast)

[jonty-comp]

Nice one, I just noticed this branch when updating our local deployment of multicast. Is there any chance you could migrate from mdns to multicast-dns for picking up the Chromecasts? The latter is a pure JS solution and doesn't require any dependencies to be built. I've been looking at running multicast in a Docker container (provided I can get the mDNS stuff passed through) and it would make building images much easier.

[superhawk610]

It would be almost poetic if I could get it to work 😁 I've never loved mdns since it causes that lengthy error message on startup and I always prefer pure JS solutions as well. I'll look into it and see how doable it will be, thanks!

[superhawk610]

Switched to multicast-dns in 0d0269488cc2bb741daeb60cf8ddde5feb34341e. Scans are a bit faster and goodbye annoying error message on startup! :tada:

[jonty-comp]

Nice one! Can't wait for the new release!

[redfive2012]

Are there any plans to allow sending push alerts directly via HTTP POST or GET, and not just through the web page?

[superhawk610]

@redfive2012 The new version is switching to a GraphQL API, which will include a playground and allow you to query against it directly.

[impe91]

Hello, any news about v3 release? I'm using v2 and just love it, really nice work!

[superhawk610]

Glad you're enjoying it :)

I'm away from home (and thus away from any Chromecasts for testing 😢) for the next couple weeks and I've just started a new job, so this project has remained on the backburner, but I am still actively developing, if not as quickly as I'd like.

My original goal for v3 was to rewrite the core codebase and implement every feature requested over v2's lifespan, but I think I may tie off a release for 3.0 without any new features (just way more stable!) and then save new features for minor 3.1+ releases.

I'll post on this thread when I have something usable worth testing for v3, hopefully soon!

[metalcoat]

Any status update on 3.0? Still active? anything I can help with?

[superhawk610]

Hey all! Since my last post I've moved across the country and gotten settled into a new job, but I still haven't had the time I want to dedicate to getting this project into a good state to push an official release. I just merged the last major missing pieces for 3.0 to master, but there are definitely some bugs yet to be worked out and some unit tests yet to be written.

If you want to help get 3.0 in good shape for an official release, it would be super helpful if you could clone master and give it a shot on your local setup. I'm pushing an updated README in the next half hour or so to provide instructions on getting up and running, but it should be pretty straightforward. If you run into any issue or find any missing functionality, please open an issue and assign me. Thanks for your help!

EDIT: README has been updated, master should be ready for testing!

[metalcoat]

I'm getting trouble trying to build this. getting parcel not found.

[superhawk610]

Here's a couple troubleshooting tips, let me know if the issue persists

Make sure you're on the master branch

git clone [email protected]:superhawk610/multicast.git
cd multicast
git checkout master

Make sure yarn is installed

npm instal --global yarn

Make sure to install dependencies

cd client && yarn
cd ../server && yarn

[jonty-comp]

Finally got around to testing this out, and the UI is great - tried it in Docker first, but couldn't get any devices to show up - probably need to mess around with the ports for mDNS etc. Running it on my local (linux) PC it sees the device i'm testing with on my network, but when I try and connect to it I get client errored: Unsupported protocol version: undefined in the log and it doesn't show the screen.

[metalcoat]

I'm also getting an error, but I see no devices I'm getting: Oops! We encountered an error. Network error: Failed to fetch, I filed it under issues.

On Sat, Jun 13, 2020, 9:13 AM Jonty Sewell [email protected] wrote:

Finally got around to testing this out, and the UI is great - tried it in Docker first, but couldn't get any devices to show up - probably need to mess around with the ports for mDNS etc. Running it on my local (linux) PC it sees the device i'm testing with on my network, but when I try and connect to it I get client errored: Unsupported protocol version: undefined in the log and it doesn't show the screen.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/superhawk610/multicast/issues/53#issuecomment-643622130, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRPFSJUFTXBDCP5WPD6JYLRWN3QBANCNFSM4G37LEYQ .