I wanted to delete the notification module and re-install it again, hoping to help the push notification issue, however, I deleted it from studio the usual way, but it is still showing in the "installed module" still as "installed - see image" , but not in the active module, hence I cannot "reinstall it" or "reactivate it".

Any suggestions? is there a way to uninstall it without studio?

Hello @Alexey

What is the correct way to upgrade my Jot Server (v1.0.3) to the latest version (v2.0.0). I would like to use the JWT auth and rooms features.

1. Can I just download the lastest Jot server from GitHub and upload it to my server via FTP to overwrite my existing Jot server files/installation and I done?

Or Do I need to stop Jot Server first using:

forever stop app.js

2. Will I need to reinstall all necessary dependencies using:

npm install

3. Will it be necessary to make Jot Server watch for changes in the certificate folder again using:

forever -w --watchDirectory=/path/to/certificates start app.js

4. Where/how to generate the 'secret' mentioned in the config.json? Is the the same with the JWT token App id in the Messenger settings? Also Where to get the JWT token App id?

5. Are the following lines no longer in used in the new congig.json file (Jot Server v2.0.0)?:

"OFFLINE":0,

"ONLINE":1,

"AWAY":2

6. Does this installation tutorial found here https://unacms.com/wiki/jot-server-installation still apply to the new Jot Server? I am a bit confused since there is another and completely different tutorial here: https://github.com/unacms/jot-server

Do we still need to create a /primus folder with a .htaccess file in it on the server?

Do we still need to 'Register/Deploy Application' in the 'Application Manager' of cPanel using Phusion Passenger as requested in the installation tutorial in the first link?

Thanks and happy holiday season! 😀

The Power Behind the Solution

Elevate Your Application with the Coozila! Memcached Cluster

In the dynamic world of modern applications, speed and scalability are essential for success. Coozila! introduces the Docker Package for Memcached Cluster 1.0.0, a revolutionary solution designed to enhance caching efficiency. This package integrates DragonflyDB and McRouter, offering a state-of-the-art distributed caching layer to optimize performance and simplify infrastructure management.

Why Choose Coozila! Memcached Cluster?

Simplified Scalability

Quickly deploy a distributed caching layer using pre-configured Docker packages, minimizing complexity and maximizing performance.

Blazing-Fast Performance

Powered by DragonflyDB, the solution delivers unparalleled speed and fault tolerance, handling high-throughput demands effortlessly.

Intelligent Request Routing

With McRouter at its core, leverage advanced features like prefix routing, replicated pools, and failover mechanisms for seamless cache operations.

Dynamic Configuration

Update and scale your caching infrastructure in real-time with zero downtime.

Multi-Level Caching

Implement tiered caching for efficient data retrieval by combining local and remote caching.

Rich Monitoring Tools

Access detailed metrics and debugging tools for complete visibility into caching performance.

Cost-Effective Operation

Reduce database load by offloading query-intensive operations to the cache, optimizing resource usage, and cutting costs.

Core Technologies

DragonflyDB: A Next-Generation Caching Core

At the heart of the solution lies DragonflyDB, a high-performance database offering:

• Multi-Threaded Architecture for maximum efficiency.
• Fault Tolerance ensuring uptime even under heavy load.
• Scalability to meet growing demands.

McRouter: Intelligent Traffic Manager

Developed by Facebook, McRouter routes Memcached requests efficiently, offering:

• Load Balancing to optimize traffic distribution.
• Failover and Replication for high availability.
• Custom Routing for tailored application needs.

Ideal Use Cases

The Coozila! Memcached Cluster is perfect for:

• Web Developers: Creating high-traffic websites and APIs.
• E-Commerce Platforms: Managing real-time product data and pricing.
• Streaming Services: Delivering personalized user experiences.
• Enterprises: Running data-intensive applications that require high availability and fast response times

Important Compliance Notice

This package adheres to the Dragonfly Business Source License 1.1 (BSL 1.1):

• Permitted Use: Installation and configuration for private infrastructure.
• Prohibited Use: Hosting as a managed service accessible to third parties.

For managed solutions, please contact DragonflyDB for direct cloud service options.

Licenses and Trademarks

• Coozila!: MIT License
• DragonflyDB: Business Source License 1.1
• McRouter: Apache License
• Memcached: BSD License

All trademarks belong to their respective owners. Use does not imply endorsement.

Ready to Transform Your Application?

Elevate performance and reliability with the Coozila! Memcached Cluster—a robust, scalable caching solution combining DragonflyDB and McRouter. Perfect for high-demand environments, this package ensures effortless deployment and future-proof scalability.

To learn more or contribute to the project, visit:

• GitHub Repository for DragonflyDB Cluster
• Fallow us on Coozila!
• Introducing mcrouter: A memcached protocol router for scaling memcached deployments
• DragonflyDB Official Website

Don’t want the hassle of installation? Order our professional installation service today:

• Coozila! Docker Package App for Memcached

Pricing Notice: The price mentioned is indicative. For a tailored offer based on your requirements, please contact our team: lab@coozila.com

Jitsi has been discussed here for about 5 years. Most questions on the subject were answered but many were not. Yes, we know that Jitsi has changed their usage terms over this timeframe. And like every other internet thing, it becomes a moving target.

Needless to say, today's social site users expect easy to navigate, seamless video of all kinds. If they don't find it, they will keep moving on to sites which do.

Users, however, have no idea how complicated coding is for internet video, audio, and streaming... For example, the video engine here on UNA is based on FFmpeg - which has dozens of pages of just settings. The documentation would fill a large book.

Anyway, it appears that UNA did the heavy lifting and successfully integrated Jitsi into their Messenger app. At present, it connects for video calls which are subject to a five minute limit. A link is provided to "Jitsi As a Service" or JAAS and there is an offer for a free "starter package". The free service is limited to a small group of users, of course. Which is much, much better than nothing.

So for self-hosters, the question is: How do the Jitsi required settings correspond or interface with those in the Messenger settings? I cannot get them to work. Jitsi states that: "All you need to do is to copy the integration code snippet and paste it into your app or website." 

I realize that for the full video services a dedicated server with ample resources is needed. So, I guess the free service is the iFrame variety. But how? And why does it seem so complicated?