Search the Community
Showing results for tags 'Multisite'.
-
I'm getting to know Processwire relatively well, and now I have a nice big challenge ahead of me and I'm trying to lay out my plan of attack. One of my peers reckons I should use WordPress Multisite, which I know is definitely a viable option, but I would much prefer to use Processwire. I know it's not a question of "Is it possible?" It definitely is. It's just a question of "What's the better approach?" Here's the situation: I'm setting up a service that will build site pages for multiple clients (aka baby sites) but all under one domain (aka mothership). The baby sites will use folders, not subdomains. Most of the baby sites will be one page only, but some may stretch to three pages *gasp*. And of course each baby site will have a completely unique look - so there'll be as many templates as there are babies and potentially more templates than babies. The mothership will be its own site with its own pages discussing how to become a baby and the benefits of being a baby. So it will look something like this: mothership dot com - with about 4 of its own pages mothership dot com/baby1 mothership dot com/baby2 and so on up to about baby1000 (potentially) Now here's my thought process. NON NEGOTIABLE - Use Processwire NEGOTIABLE: 1. One PW site, each baby is just its own page with child pages where necessary 2. One PW core install, each baby is a separate PW site running from the same core wire. PROS and CONS of the two alternatives as I see them: Alternative 1: PROS - Really easy to install and just create the babies as pages on the main site tree. Easy to update core and modules/plugins CONS - Will it become difficult to maintain as the babies approach the thousands? Will it scale or will it crash? Will it become a future model of the dangers of putting all your eggs (or babies) in one basket? Alternative 2: PROS - Would be nice and easy to maintain from one core, since I only have to update just the one wire folder. Might scale easier since they're different sites, each with just a few pages. Any other advantages? CONS - Don't even know if this is doable? - Would I need to update each site's modules separately? Annoying Your thoughts and recommendations are much appreciated by the mothership and the many babies, and by me of course -
I've been testing out the multisite feature of processwire installing via option 1 in the docs. I managed to get everything working by following the first option which requires installing a new version of PW and copying the files over to a site-mysite directory. I'm now testing out the second option which just needs the site files copies to a site- directory and importing the DB from another installation using PhpMyAdmin. The installation worked fine but when I try to login to the admin the username and password I used from my clone site are not recognised. I thought the password would pull over from the SQL database. I'm sure this is something really simple but I'm scratching my head at the moment. Any ideas?
-
I noticed there is a file named index.config.php in /wire which is the "ProcessWire multi-domain configuration file" and I'm wondering if this is for multiple PW sites similar to WP Multisite or EE MSM or am I confusing it with Multi Environment setups. For example if I wanted to have a local, dev, staging, live/production multi environment setup would this be the file to use? Where all the domains, paths, db settings would most likely different from enviro to enviro? It looks like this is in fact for setting up multi-environments now that I read and understand what's taking place. The fact that it's called mulit domain is throwing me off a little, however and why I wanted to double check I guess. Is there anything to worry about with these types of setups in regards to paths or does PW handle all that for us and we just need to worry about setting up things per the instructions in the file? Any gotchas in other words?
-
Hi guys, I have been playing around with multisite recently and wondered - what would be the best way to share some template logic between multisite instances? I have an upcoming project where two different sites would have different users and setups etc but they need to share some basic similarities in look and functionality. I was thinking of setting up the sites as separate sites under multisite and then finding a way of sharing something such as a 'main.php' file that each template calls. I would also like to share a 'base.css' file between the sites as well. I want to do things this way because they want the potential to be able to expand into more sites over time - up to 5 or so. What would be the best way of doing this? Thanks in advance.
-
Hi Guys, I have read through other topics on using PW for multisite setups and am a bit none the wiser unfortunately. Let me explain my scenario: I have a potential client project whereby they want to have 3 websites all as separate websites in terms of: content look & feel domain names Users However, for me to setup up the websites for them it makes no sense for me to be managing 3 separate hosting accounts and them to be paying for all of that. Also, 1 of their websites will be a primary site with a few thousand visitors per month, but the 2 more secondary websites will only have a couple of hundred visitors. Perfect for a multisite install to my mind which wouldn't tax server resources too much. This to me seemed a perfect opportunity to setup a multisite under one hosting environment whereby domains are mapped to subdirectories or whatever setup I would need. My problem is that I have no idea as to how I go about setting all of this up in PW. I have done this before with WordPress using the domain mapping plugin under a multisite install. All without dealing with symlinks or much code at all. However, I would really like to use PW for this as long as it's not too complex. With PW I can deliver a client user experience in the admin area that is much more streamlined for their particular use case.
