2 PW websites at same time? or json webservice?

[joer80]

I am starting a new project and need help making the plan for it.  

I am wanting one website  for controlling inventory, and many other websites that display the inventory.   I am wondering what the best setup would be?  

I first thought about doing a multisite install and putting everything into one pw cms, but the satellite websites are getting to be very different from each other and I am wondering if this is not going to work out.

I am thinking I should just keep the inventory in one pw system, and leave the other websites to just read the central inventory system to keep things simple.   I dont think it will be worth it to have all 20 or so websites from the same templates and fields.

As far as I can see, this leaves me with either having my satellite websites mount the inventory website in addition to itself, or having the inventory website provide a web service/api of the inventory for them to query.  (I am pretty sure pw3 allows for 2 cms setups to run at the same time, but I am not sure how to do it.)  Which is going to be a better method?

Thanks for any input you can offer!

 

[adrian]

Here are the details on multi-instance setup: https://processwire.com/blog/posts/multi-instance-pw3/

[joer80]

If I decide to go json way, would this be the most up to date method to go with? I dont see a service pages module any longer.

 

[arjen]

I don't know why the ServicePages isn't in the modules database, but it is still available on github.