Multiple skins with one database

Hi!
According to this: https://www.jamroom.net/the-jamroom-network/forum/using-jamroom/55733/multiple-sub-domain-access-to-one-jr-database ...

I made strucuture like:
domain.com/MASTER
domain.com/SITE1
domain.com/SITE2
etc.

I also made symlinks for modules and skins directories - it's working. But I have some questions, especially for you , @Brian or someone who knows how to make this working:

What I need to have in $_conf['jrCore_base_url'] = 'https://domain.com/MASTER'; or $_conf['jrCore_base_url'] = 'https://domain.com/SITE1'; ...for example SITE1 ? I need to change always this "base url" to correct directory for sub-site or it should be always set on "Master"?

And second - how about DATA? If someone registered on SITE1 with photos, music etc. - how to make this possible tobe visible also on SITE2, MASTER etc. ? Maybe symlink for data/MEDIA directory ?

I will grateful for any help with this
Best!
Peter
updated by @piteridrecords: 11/28/20 08:47:13PM

I don't believe you can run separate Jamroom sites on one database, the database is specific to the single Jamroom site.

Hope this helps!


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos

@douglas - So what do you think about this? https://www.jamroom.net/the-jamroom-network/forum/using-jamroom/55733/multiple-sub-domain-access-to-one-jr-database

You have as demo sites one database connected to different skins.

Sorry, this isn't something Jamroom can do out of the box, which is what I thought you were trying to do.

If you've set it up like Brian laid out in that post, then it should work,


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos

@douglas Yes - but I need now some more details about what I should set in $_conf['jrCore_base_url'] and how to share media directory for all "skin sites"

If you don't symlink the conf.php file then each of the sites can have their own base_url set in there.

symlinking the data directory seams like it would work. Hard to know without doing it then seeing what happens, then going from there. Take a step, debug, take another step. Unless someones built what you're building before the answers may be slim.