Activity Log - Mailgun Error
Using Jamroom
You can ignore this - looks like something hit your "webhook" endpoint, but it wasn't Mailgun (otherwise you would see a bunch of data in the $_post variable).
Forum Activity for @brian
Using Jamroom
You can ignore this - looks like something hit your "webhook" endpoint, but it wasn't Mailgun (otherwise you would see a bunch of data in the $_post variable).
Looking to create a musical social network. How do I contact Jamroom...
Using Jamroom
Welcome to Jamroom!
If you need to contact us by email we are at support [at] jamroom [dot] net - we can also answer any questions you might have here in the forum if your questions might be helpful to others.
Thanks!
Android and Apple App
Suggestions
I know this gets brought up from time to time. If you're serious about wanting a mobile app, feel free to contact us. There's just no way to make a "generic" Jamroom app that can be used by anyone - each is unique and takes quite a bit of time and energy getting it so it is setup in the app stores.
It's not cheap - be prepared to spend quite a bit of $$ getting one created for you, as the amount of work can easily take up to 6 months.
Additional DBs
Jamroom Developers
You would have to do something custom - there's nothing in Jamroom that allows it to work with 2 different databases at the same time. Sorry!
Additional DBs
Jamroom Developers
DannyA:
Right. Isn't that my original question?
Right. Isn't that my original question?
No - it's not
You're confusing "database" with "server". A single MySQL server can contain hundreds of databases. Moving your "data warehouse" to a different database on the same server is not going to lessen the load on the server. You need to create a second server and load your data warehouse data on the second server. This way the queries you run against your data warehouse do not impact the performance of your main server.
Additional DBs
Jamroom Developers
A "data warehouse" would be a completely separate server from your live server, that would allow you run ad hoc queries on the data without worrying about messing up your production data.
Additional DBs
Jamroom Developers
DannyA:
I may have mis-communicated then. There are many microtransactions and very detailed reporting and analytics. So I want to separate that data so it doesn't slow down the main db when a report is generated. However, I still want to be able to query the new db using the Proxima APIs
I may have mis-communicated then. There are many microtransactions and very detailed reporting and analytics. So I want to separate that data so it doesn't slow down the main db when a report is generated. However, I still want to be able to query the new db using the Proxima APIs
Moving the data to a different DB won't do anything for performance - you need to either get a bigger server that can handle the load, or stream the data off to a replication slave. The reason is that in MySQL databases are just a logical abstraction - if your server is already suffering under load, splitting the data into multiple DB's will actually make a bit worse, since there is extra overhead for each DB that is "open".
Let me know if that helps.
Additional DBs
Jamroom Developers
DannyA:
Don't you end up with the same data on both servers? The idea was to separate transactions data because it's a lot of microtransactions. It's causing a big load on main DB when we run reports
Don't you end up with the same data on both servers? The idea was to separate transactions data because it's a lot of microtransactions. It's causing a big load on main DB when we run reports
That's correct - based on what you posted I thought was what you were looking for?
Additional DBs
Jamroom Developers
You'd want to setup a MySQL replication slave server and run your queries from that slave server:
https://dev.mysql.com/doc/refman/5.7/en/replication-setup-slaves.html
Unable to put a link containing the string ".jpg" in a comment.
Using Jamroom
You should be good now - you had 3 templates that were using the incorrect value for the image URL:
index.tpl
item_list.tpl
profile_index_image.tpl
I've fixed those up and you should be good.
