Forum Activity for @brian

brian
@brian
02/08/18 08:55:08AM
10,158 posts

Send attachment in mail
Jamroom Developers

The fourth parameter to the jrCore_send_email function is an "options" array - you can send attachments by including them in the "attachments" key for the options array - i.e.

$_options = array(
    'attachments' => array(
        '/full/path/to/attachment1',
        '/full/path/to/attachment2'
    )
);
jrCore_send_email(address, 'subject', 'message', $_options);

Let me know if that helps.
brian
@brian
02/03/18 08:00:29PM
10,158 posts

new server (very fast) still some issues remain
Installation and Configuration

Correct- if you need profile domains then use Apache with mod_php if you can. If you really need the per-user process handling of fastcgi then you'll want to play with it - it's not something we develop or test on.
brian
@brian
02/03/18 07:56:38PM
10,158 posts

Jamroom Handling Huge Traffic flawlessly
Off Topic

I saw this come in last week and wanted to say "thanks" for the awesome report. I do a lot of low level optimization work on JR and it makes me happy to see it pay off :)

Thanks!
brian
@brian
02/03/18 07:55:33PM
10,158 posts

new server (very fast) still some issues remain
Installation and Configuration

Also - here's the JR system requirements page:

https://www.jamroom.net/the-jamroom-network/documentation/getting-started/774/server-requirements

It's not going to talk about fastcgi since we would never recommend it. I will get something on there that specifically tells you to NOT use it.
brian
@brian
02/03/18 07:54:11PM
10,158 posts

new server (very fast) still some issues remain
Installation and Configuration

I've only got 2 minutes here so can't follow up much but you should NOT be using fastcgi. You need to be using Apache with mod_php OR nginx with php-fpm - both of these work really well with JR with minimal fuss.

I've built literally hundreds of servers and have not had any of the issues you are posting. If you want to go witth php-fpm I can post the nginx.conf file and www.conf file I personally use.
brian
@brian
01/22/18 06:49:02PM
10,158 posts

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.
brian
@brian
01/21/18 09:58:37AM
10,158 posts

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.
brian
@brian
01/21/18 08:59:35AM
10,158 posts

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.
brian
@brian
01/18/18 03:13:47PM
10,158 posts

Text in email notification of Support Ticket needs change
Using Jamroom

lornawebber:@brian, no, not at all - I wasn't aware of webhook as an option. Thanks for the template update.

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.
brian
@brian
01/18/18 03:12:32PM
10,158 posts

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.
  84