Ivan Gretsky

Thanks for the great suggestions! Will make my mind around it and try. If anyone has other ideas or experience on the topic, please share. I did not consider REST API for using $user data from the main registration site on the other installations (and do not have expertise in this). Are there other (simpler? more PW-ish?) ways to do it?

Maybe there could be an easy solution? Like adding a list of ips and/or domain names that should be treated like a localhost to the config?

Cool stuff, @Rudy! May I ask a few additional questions? Do you limit the ability to login/register to only one installation? How? You do not re-create users on all installations, do you? Are you using user info from one installation in all the others? I mean something like $user->hasRole() and things like finding users? How? Are you using API call to other instances?

Great additions! Have not tried'em yet, but my next week will be full of fun) Thanx, @ryan! I was amazed to see my name in the blog post, but I need to say that all the credits for those images should go to @David Karichas they were taken from his fundamental video. By the way, everybody caring about the future of PW and its infrastructure please 💲💲💲 donate to David as a creator, who shapes the things we use (and dream of), so he feels even more motivation to keep doing his thing. He asked for the support. And of course, go get your copy of ProFields if you have not already, as that is one of the coolest 😲 things you can get for your PW site and supports PW development as a whole. Sorry for the emojis, but it is late friday night here where I am at and I feel exited)))

@Rudy, surely I want a copy) But even more than that I want an explanation how to use it and how exactly will it fit my case. Could you please write a little more about it if you got time?

Good day everyone! Hope you all safe and healthy! I am thinking about a rather ambitious project (for me). It should consist of a number of ProcessWire based sites which will serve the same group of registered users. I need to make the user registration a one time process. And I need to share the user data across the sites. Single sign-in is also in plans. I am thinking about placing the user info and all the user data in one installation and somehow sharing it between all the other. But I am open to any suggestions. Please share your thoughts and experience on the topic. I am only in the very beginning and trying to estimate is it even doable.

I was asking about creating Repeater fields as a type of Mystique.

Hey @ukyo! Every time I write here I want to start with a thank you, as I like the module so much) Now to the question. Is it possible now or could it be implemented to support repeater / repeater matrix fields? P.S. Are there any rumors about when is the next branch going to be merged?

Hey @Pete! You can limit types by template out of the box - look at the template overrides. There is a nice module by @Robin S that can do more than that. Is you need to restrict in part of the page tree, you will need to reach for hooks. You can look at the ones Robin uses in his module.

Great news you're working with Repeater/Repeater Matrix once again, @ryan! This new enhancement is superb and in line with the community requests in the Making Repeater Matrix better suitable for content building umbrella topic, specifically with @Zeka's 1st one in this post. Thank you! This is also a quite requested feature, so eagerly waiting on it! Could you please consider adding the ability to override the default mechanism of adding new items, so we could build a nicer UI for it if needed, as described here. Thanx in advance))

I don't))) I just read "Have a more robust and portable and setup where I can spawn vps's with a click" and it sounds like proxmox. I am happy with my shared hosting for PW sites) Actually I do not see a need for a dedicated VPS for a site in most cases. Why not put all those sites in one VM with LAMP installed and create new ones copying virtual host configs? You have you backup and everything else in shell scripts or ansible plays. And this way you are not locking yourself in any proprietary thing you try to avoid.

Hey @joe_g. You could take a look at proxmox - the open source classics. If you want to go with containers and Kubernetes, there are things like rancher.

I was talking about Ryan. He is the one looking after the core (and everything really). Just wrote that post to let him know I am thankful he does.

Great to see those core things evolving. Someone has to look after them. And we all know who that is))

@elabxPretty nice, actually) There are issues, but I am getting my way around them)