Forum Activity for @brian

deleting cached images too often?

Using Jamroom

This is normal. Every hour, images that have not been accessed in over 2 days are removed. This allows the module to work on a small amounts of file deletions instead of "saving up" and having to delete a huge chunk of images once per day (which impacts the system more). By doing it hourly it spreads that work out over the entire 24 hours, as well as clears up space as soon as it can.

Let me know if that helps.

jrCloudCore documentation

Using Jamroom

Jamroom Cloud is no longer - it's being replaced with Jamroom Cluster, which requires a minimum of 5 servers. The server needs to be in the same datacenter for best performance. It's a true scalable architecture with support for up to dozens or even hundreds of servers.

It's not something we will be making generally available - it's just too technical for 99% of our user base. It's something we will run for those sites that need it on Jamroom Hosting.

I know that's probably not what you're looking for, but that's what Jamroom Cluster is.

Let me know if that helps.

jrCloudCore documentation

Using Jamroom

Delete the Cloud Core module - it is no longer available, and was only available to sites that had purchased a cloud license. It is not needed on your site.

Text in email notification of Support Ticket needs change

Using Jamroom


The webhook option is nice since your users will be able to simply respond to the email and it will show up as a ticket update.

We can help you get this setup if you want - if you do, open a support ticket and we can help.

Updating Interdependent Modules

Jamroom Developers

There is no "pausing" during an update. Jamroom marketplace updates are "atomic" - that is the new version of the module or skin is fully loaded on the site and validated. Once the marketplace tests it and it is "ready to go" then it swings the existing symbolic link to point to the new directory - there is zero downtime or "in between" time.

They are updated in the order they are listed if you do an "update all". In your case you would want to manually update each module so any dependencies are in place before they are needed (i.e. update A first, then C, then B).

Let me know if that helps.

quota_jrProfile_privacy_changes and admin

Using Jamroom

Yeah that field should probably be hidden if changing it does nothing - I'll check it out.

Text in email notification of Support Ticket needs change

Using Jamroom

The support ticket module really works best with the webhook integration - is there a specific reason you guys don't want to use it? We'll get the templates updated with a check for the webhook to be activated - that should have already been there.

DB and System Backup module now requires the AWS SDK module

Announcements

If you are currently using the DB and System Backup module:

https://www.jamroom.net/the-jamroom-network/networkmarket/22/db-and-system-backup

When you update to the newest release (2.0.0) make sure and install the NEW "AWS SDK" module:

https://www.jamroom.net/the-jamroom-network/networkmarket/537/amazon-web-services-sdk

We have a number of modules that can utilize Amazon web services, and this way we can provide the SDK in a single module and not have to duplicate it in each module that needs it.

You can install the new AWS SDK module from the marketplace, and if you do NOT have it installed your System Check will show you that it is needed.

If anyone has any questions please let us know.

Thanks!
updated by @brian: 09/04/19 10:21:36AM

Video stream in Safari

Jamroom Developers

OK weird - we'll see if we can replicate this.

Make my queue worker create other queue tasks, is this viable?

Jamroom Developers

Since a queue worker is already run offline I think you'd find the flow to be simpler to just have ONE queue entry that runs a series of functions - that way you can test each one and exit if needed. Trying to do it with a subset of queues could make it more complicated than needed.