Add Deno to Rocket.Chat for Apps to work
-
@jeaninerenee we have opened an issue internally for fixing this. Will update when we have a fix.
@girish Thank you. We appreciate your work.
-
RocketChat is becoming really problematic. We only know RocketChat on Cloudron and we are running the 7.2 version. Our iOS apps don't notify reliably and don't keep a persistent login.
Desktop is much better.
We've noticed notifications about limits to the free version of 50 or 25 users (how is this FOSS?) but that doesn't affect us.
The steady degradation of RocketChat (we were delighted with RocketChat already at v3) has been frustrating. It's over ten years of RocketChat for us and it's now almost unusable. We hosted our RocketChat on the development team's paid servers, but the offer kept changing from flat $50/month to per user pricing (that would have affected us negatively at the time). What moved us off the RocketChat servers finally was the insistence on AWS infrastructure.
Keeping our private, open source chat application on the CIA's cloud providers didn't make much sense. It seems to me that outside of the commercial pressure, somehow the American intelligence community entered into a relationship with RocketChat where RocketChat gets some money/support in exchange for making sure everyone's RocketChat can be monitored. All RocketChat installs are federated with the development team server, which at least lets them know who is where and who is sending messages on a given server. That's a lot of information.
After ten years of RocketChat, five of which were very happy, not sure where to go now. Matrix, Zulip, Mattermost or even back to IRC. Or try to keep fighting RocketChat.
My point about fighting RocketChat is that Cloudron should probably be looking for a forked version of RocketChat which doesn't include all this monitoring software and limitations. I'll take a quick check now.
-
RocketChat is becoming really problematic. We only know RocketChat on Cloudron and we are running the 7.2 version. Our iOS apps don't notify reliably and don't keep a persistent login.
Desktop is much better.
We've noticed notifications about limits to the free version of 50 or 25 users (how is this FOSS?) but that doesn't affect us.
The steady degradation of RocketChat (we were delighted with RocketChat already at v3) has been frustrating. It's over ten years of RocketChat for us and it's now almost unusable. We hosted our RocketChat on the development team's paid servers, but the offer kept changing from flat $50/month to per user pricing (that would have affected us negatively at the time). What moved us off the RocketChat servers finally was the insistence on AWS infrastructure.
Keeping our private, open source chat application on the CIA's cloud providers didn't make much sense. It seems to me that outside of the commercial pressure, somehow the American intelligence community entered into a relationship with RocketChat where RocketChat gets some money/support in exchange for making sure everyone's RocketChat can be monitored. All RocketChat installs are federated with the development team server, which at least lets them know who is where and who is sending messages on a given server. That's a lot of information.
After ten years of RocketChat, five of which were very happy, not sure where to go now. Matrix, Zulip, Mattermost or even back to IRC. Or try to keep fighting RocketChat.
My point about fighting RocketChat is that Cloudron should probably be looking for a forked version of RocketChat which doesn't include all this monitoring software and limitations. I'll take a quick check now.
@foliovision Look into Revolt, there's an App request for it in this forum as well.
-
RocketChat is becoming really problematic. We only know RocketChat on Cloudron and we are running the 7.2 version. Our iOS apps don't notify reliably and don't keep a persistent login.
Desktop is much better.
We've noticed notifications about limits to the free version of 50 or 25 users (how is this FOSS?) but that doesn't affect us.
The steady degradation of RocketChat (we were delighted with RocketChat already at v3) has been frustrating. It's over ten years of RocketChat for us and it's now almost unusable. We hosted our RocketChat on the development team's paid servers, but the offer kept changing from flat $50/month to per user pricing (that would have affected us negatively at the time). What moved us off the RocketChat servers finally was the insistence on AWS infrastructure.
Keeping our private, open source chat application on the CIA's cloud providers didn't make much sense. It seems to me that outside of the commercial pressure, somehow the American intelligence community entered into a relationship with RocketChat where RocketChat gets some money/support in exchange for making sure everyone's RocketChat can be monitored. All RocketChat installs are federated with the development team server, which at least lets them know who is where and who is sending messages on a given server. That's a lot of information.
After ten years of RocketChat, five of which were very happy, not sure where to go now. Matrix, Zulip, Mattermost or even back to IRC. Or try to keep fighting RocketChat.
My point about fighting RocketChat is that Cloudron should probably be looking for a forked version of RocketChat which doesn't include all this monitoring software and limitations. I'll take a quick check now.
@foliovision All three are good solutions, lattermost probably being the most closed one. Alternatively I can also highly recommend NC Talk
-
With the recent update to Rocket.Chat (2.54.2), app installs are breaking again. This issue did not occur in version 2.54.1.
Below is the error message encountered:
Caused by: 0: Error creating '/app/code/bundle/programs/server/npm/node_modules/@rocket.chat/apps-engine/.deno-cache/npm/registry.npmjs.org/uuid/8.3.2'. 1: Read-only file system (os error 30)According to this forum post, only the
/app/data,/run, and/tmpdirectories are writable. However, Deno (or Rocket.Chat) attempts to write to/app/code, which is read-only.Is there a workaround or temporary solution to allow writing to
/app/codeuntil this issue is resolved? -
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on
