Forum Activity for @brian

BUG: Wrong year date in profile list when no value for year has been set.

Genosis

Thanks for the report - I will check this out.

Is There a PDF Version of Documents?

Installation and Configuration


This is really what it is about. The problem with a PDF is that it is basically outdated as soon as it is downloaded, and then the site owner is relying on it being up to date.

Analytics Comparison

Using Jamroom


This is correct - with JR it is who's been active in the last 15 minutes, whereas with GA it is closer to "real time".

FoxyCart / Subscription Welcome Email

Installation and Configuration

Unfortunately the FoxyCart module does not support this at this time - sorry!

Disk space calculation

Jamroom Developers


No plans - there's just no way to even get close to accurate when measuring bandwidth usage at the JR level (PHP). The problem is that when someone clicks to stream an audio file (for example), that file is sent to the web server's buffer in like 2 seconds, so even if the "listener" only streams 20k of the file, all 20mb will be counted as "bandwidth".

Something would have to be created custom at the network level to monitor individual profile bandwidth, and I'm not sure how that would even be done.

Sorry!
updated by @brian: 03/15/17 07:07:22PM

Load balancing multiple servers

Using Jamroom

You're not going to see JR move in the micro services direction - in my opinion microservices just add more overhead, complexity and creates a slower more error prone system (since now your flow overwhelmingly requires network, which is the most prone to problems).

I believe microservices make sense when you have different teams running different parts of infrastructure and you want to "black box" as much stuff as possible, but it makes very little sense for most sites to even move in that direction. I've read a lot on microservices and found this blog post to be one I agree with:

http://basho.com/posts/technical/microservices-please-dont/

The direction we are moving with JRC 2.0 is to make even a large JR cluster easy to admin and run even for a solo site owner. This means less cloud modules and more "it just works". This means running a lot of things as "services" internally, but the site owner just does not need to care. Our goal is that when you feel you need more CPU power you just spin up a new app server, add it to your cluster, and you're done.
updated by @brian: 03/11/17 10:15:18AM

Site Builder Backups

Design and Skin Customization

Not at this time - currently it just backs up your settings every 24 hours.

Load balancing multiple servers

Using Jamroom

Yes - for now.

Note that Jamroom Cloud 2.0 is in active development right now and is getting fairly close to it's first release. We've been doing A LOT of work to make running a JR cloud much, much easier by simplifying many aspects of the system. JRC 2.0 will also run much better when distributed across multiple front ends.

Upgrading from JRC 1 will be pretty straightforward and will mainly involve turning off some of the modules that are no longer used.

More details will be coming in the next few weeks.

Thanks!

Proxima on a different host

Proxima

To be honest I would not worry about Proxima's load - it is much, much lower than regular Jamroom. The big contributor to JR load is Smarty templates, and since Proxima is all JSON you don't have to worry about it.

However you could install Proxima on a separate server and just have it point to the same DB.

Documenting API

Proxima

Proxima is built using Jamroom. There's no documentation API at this time.

Sorry!