#9

Contents

• Workshop Improvements
• Proxy a Target with a port
• Guide on Local HTTPS Proxy
• Apps over infrastructure
• Cloud Going Global

Workshop Improvements

Since the release of Workshop, we’ve received tons of great feedback, bug reports and feature requests! The best place to get involved in these discussions is our Github Community Forum. The past month has seen improvements in the speed and stability of Workshop, reduction in the desktop application binary size, and minor UI updates.

For a more technical view of our Desktop releases, including Workshop, see our Github releases page.

Proxy Target Port Configuration

Cloud and Workshop both received an update that enables lots more flexibility with regard to what an Endpoint proxy can target. Specifically, the Endpoint proxy target can now include a port configuration. This is useful for any service using a non-standard HTTP port. And notably, in local development it’s now possible to integrate services running outside Noop with a Workshop Endpoint. The external target (webserver) will receive the same HTTPS and routing capabilities as any Noop Environment target.

We published a guide that outlines how to take advantage of the Proxy Target Port config on localhost, see below.

New Guide: Add HTTPS to Existing Local Server

To help developers transition from their current local development processes and environments to Noop, we wrote a guide to add some of the benefits of Workshop without fully adopting the platform.

The update to targetting proxy endpoints, outlined above, enables HTTPS on localhost without changing the existing development setup or sending local traffic over the Internet.

Apps Over Infrastructure

As we continue developing the Noop software, we’re also developing the Noop story. Why are we building Noop? What does Noop offer that’s different than everything else?

We published a post last month to start communicating the “Why?” behind Noop. This first post shows how infrastructure is only one part of Application development. It continues to show how the prevailing industry best practices complicate the relationship between applications and infrastructure. Finally, it outlines the Noop approach. Enjoy!

Cloud Going Global

We’ve alluded to it in the past, now we’re on the verge of releasing Noop Cloud globally. To start we will roll out the distributed router to Virginia. This will increase the geographic footprint of Cloud Internet Endpoints. This has substantial performance benefits resulting in lower latency for users when establishing connections. Noop Router accepts traffic globally via Anycast IPs and forwards streams across our secure internal network for maximum performance.

In addition to the benefit we get with the Virginia deployment, the work we have done allows us to roll out to other regions with far greater ease.