Is a multisite the way to accomplish this or is there a better way?
Thank you!! Angie
WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It only takes a minute to sign up.Sign up to join this community
If your client asks for multi-sites, there is no alternate option for it then.
But according to the need, sometimes creating separate pages for clients like website.com/client1/, website.com/client2/ etc. and masking/redirecting client1.website.com, client.website.com to these (respectively) may work as well.
This will lessen the trouble of handling multiple sites.
The way explained by joetek is fine, cause turns it easy to maintain a single base updated for everyone! But, depending on the solution you are figuring out, also has an cons: once you have a single instalation, a single bunch of code, in order to serve many clients, if this single point of failiure presents some problem (bug, virus, hackers) its ging to affect all your potential clients... In my case I have something like that, and i have dockerized every client with its own linux+apache+wordpress, and with its own linux+mysql database. And everything behind a nginx reverse proxy. This way i have a little bit more effort to update all wordpresses, but a little bit more secure too. And my customers also can ask for sftp access because its not going to affect main repo. I dont know how wp multisite handles this question of sftps.. thanks.
Sounds like a multisite solution to me.
But be aware that each sub-site will create an additional 8-10 tables in your database. Some hosting places will get irritated if you have a database with 100 tables or more, especially with the cheaper hosting plans. In my experience, a multisite with more than 10 subsites will start to get the attention of a hosting place if you are on their cheaper plans.
So be aware of the need for a higher level of hosting plan because of the number of sub-sites you will have.
Of course, if the client is hosting the site on their own server, then you just need to make sure that the server has the 'horsepower' (resources) to handle the visitor load.