• Resolved danielkun

    (@danielkun)


    I have been assigned to setup a plattform for about 200 kindergartens. Each kindergarten will be very limited to what is possible in terms of customising the theme or adding plugins.

    In short, they will all be using the same theme and the same plugins. No kindergarten will be able to customise their site any different other than colors/layout. New functions/plugins will be added to all sites or none.

    A multisite solution sounded obvious at first, then I started investigating some and now I’m having a hard time choosing between one of the following:

    Standard WP Multisite (Shared DB, shared content directory)

    Stand-alone WP sites that share the same codebase. (Similar to: WordPress Skeleton) Each site would have it’s own database and content directory. But the code would be symlinked and therefor updating the source-code with new code would update every site.

    Here are some issues why I believe stand-alone sites are a better option:

    1. Development: I’m imagining that it’s easier to develop/debug issues due to smaller databases.
    2. Backup: It’s easier to restore a full database backup if (for some reason) needed.
    3. Users: All users will be synched from an Active Directory over LDAP. The AD plugins I have looked at so far have vague multi-site support.
    4. Plugins: Not all plugins support WPMS.
    5. User Roles: Configuring customised User Roles on WPMS seems complicated while rather easy on a standard WP site.

    Here are some issues that I would have to deal with if using stand-alone sites:

    6. Permissions: No one should be able to add new themes/plugins so these menu-options would need to be hidden and functions disabled.

    I’m not quite sure what I would gain from having a multi-site setup. Being able to update WP core or plugins with the push of one button is nice – but the above stand-alone setup would offer the same.

    (I prefer to test any new plugins locally first, and then push them into our repo and pull the new code on the production servers. This would update all sites and I would also be able to revert to previous releases if problems occur)

    I also have a question regarding general deployment.
    Let’s say I have my sites up and running now (MS or stand-alone) and I decide to add a Google Analytics plugin. Enabling this plugin for all sites would be easy in a MS setup. In a stand-alone solution I could probably use WP-CLI for this. But how would I get site-specific settings (Google Analytics tracking code) into WP without having to login to every site manually (200 sites will take time!)

Viewing 2 replies - 1 through 2 (of 2 total)
  • With multisite, you can restrict access for adding/activating themes and plugins through the network admin, which is handy. We use multisite to run WordCamp.org (80-90 sites added per year), the contributor network of make.wordpress.org sites, and it has been a great solution. I know of at least a few of schools using multisite for sites for different classes, and they like it because the access restrictions are built in, so it’s hard for a teacher to inadvertently break something. So I vote multisite. 🙂

    If you’re interested in connecting with other academic users/administrators, you might join the wp-edu mailing list, and asking for an opinion there, since they would likely have similar use cases as you.

    Thread Starter danielkun

    (@danielkun)

    Thank you very much Jen! I’ll have a look at WordCamp.org and join your mailing list! 🙂

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘WP Multisite OR Stand-alone sites with shared codebase?’ is closed to new replies.