Skip to content

Community/Selfhosted Teletype Fork for Pulsar Editor - Share your workspace with team members and collaborate on code in real time

License

Notifications You must be signed in to change notification settings

teletype-diy/teletype-diy

Repository files navigation

⚠ This is beta software, expect problems. ⚠

The code will probably change and stuff will break.

Teletype DIY for Pulsar

You might remember the teletype package for Atom. This is a self-hosted version of it, for Pulsar.

Never heard of Teletype. What is it?

An Pulsar package that lets developers share their workspace with team members and collaborate on code in real time.

How is this different from the original Teletype?

The original teletype was backed by Github and as such could host a central signaling-server. To use this package, you will either need to host a signaling-server yourself or you will need to do the signaling yourself. Depending on your network, you may need a ICE/TURN/STUN server (e.g. coturn).

FAQ

What will get shared?

Teletype-DIY will only share the buffers/files that are currently open in your editor instance. Packages that use the Teletype-DIY API might extend this, such as teletype-tree-view.

How to do the manual signal exchange

  1. Enable 'direct p2p' in settings
  2. Connect like normal
  3. Follow instructions in signal-pane: copy signal to peers.

About

Community/Selfhosted Teletype Fork for Pulsar Editor - Share your workspace with team members and collaborate on code in real time

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published