npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

chatcola-server

v3.1.8

Published

<p align="center"> <img src="https://chatcola.com/images/logo.png" /> </p>

Downloads

9

Readme


This repository hosts the chatcola server needed to self-host reliance and storage of your messaging.

Getting started

With docker (the easier way)

  • run docker install chatcola/chatcola
  • run docker run -e THIS_INSTANCE_ADDRESS={{your instance address here}}

Without docker

  • Install node.js 14:

    Linux / MacOS:

    curl -s https://install-node.now.sh | bash -s --

    Windows:     download installer from here

  • Install chatcola p2p server:

    npm install -g chatcola-server
  • Run the server

    chatcola-server
  • If you plan to use the server for longer (i.e. raspberry pi), daemonize it with some process manager, for example:

 $ npm install -g pm2 
 $ pm2 run "chatcola-server"

you will be asked for instance address, give it a string that's easy for you to remember (it can be anything provided no one has taken it before, i.e. "foobar") -

To host the chatroom on your instance insert webrtc:{{YOUR INSTANCE ADDRESS GOES HERE}} when creating a chatroom at chatcola.com/start

For example, if you have address foobar, then you will have to insert webrtc:foobar

If you want to change the address later run the server with the --resetAddress flag:

chatcola-server --resetAddress

you will be then guided through the process of assigning address again. Note that all chatrooms created beforehand will be left fatherless and impossible to use again.

Hosting a http instance

This comes a bit harder than hosting a webrtc instance, but provides a more performant and probably more stable experience.

You'll need a linux computer (probably a VPS) with a public IP

  1. Point your domain name (you can get a free one at Freenom.com) to the VPS.

  2. Make a ~/.chatcola-http directory

  3. Copy your SSL cert files (they need to be named fullchain.pem for the cert and privkey.pem for the private key) to ~/.chatcola-http directory

  4. At this point you should have already installed chatcola-server from npm and prepared your home directory to look like so:

/home/<your-username>/
├── .chatcola-http/ # <----- notice the dot
│    ├── privkey.pem
|    |── fullchain.pem

You are now ready to launch the chatcola server.

  • Run

    chatcola-server-http

Available options are:

  • PORT - if using this, then also remember to change the port from 7777 in THIS_INSTANCE_ADDRESS. So if you set PORT to be, for example, 5050 and you have domain example.com, you have to set THIS_INSTANCE_ADDRESS to example.com:5050. You can do a reverse proxy with nginx/apache/caddy and bind port 443 to your chatcola instance, then you won't have to specify the port in this variable.

  • SHOULD_REPORT_ERRORS Set this to false to disable our sentry.

Both of them should be set as environent variables.

Building from source

  1. Clone the repository and run npm install
  2. Make the script executable - chmod +x ./scripts/build
  3. Either run ./scripts/build to build for webrtc or ./scripts/build http for http. Your build will be in build/p2p or build/http.

License

This program is free software. For alternate licensing arrangements contact us at [email protected]