module Dev Module to setup Default "New PW"

[[Code] Specialist]

Hi Folks,

I am lost and stuck !

 I like to setup several domains with ProcessWire - MultiLanguage. All Pages should have the same basisconfiguration and Fieldsets. Its a messy job to setup each domain manually, so my idea was to develop a module , which setup my basis templates + fields + fieldsettings (visuality / dependencies / fieldsets) automatically.

But I have no idea how to start and what to start with.

All modules I looked at, mostly do something for front-end jobs. But this is an install-module.

How to create a module which:

• create fields and fieldsets and its dependencies (is there a cheatpage for all possibilities ?)
• create template Pages which implements above fields

If someone could give me an easy implementationhint it would be sooooo nice. Maybe there is already something I could look at for learning.

Thanks a lot

Michael

--

Using PW 3.0.62

[bernhard]

Hi and welcome to the forum.

Have you looked at kongondos Multisite Module and my recently published Kickstart module?

[BitPoet]

Why not set up the first site (or a kind of template site), run Site Profile Exporter, copy the created profile into the install package and run the regular installer with that profile for the subsequent domains?

[szabesz]

2 hours ago, BitPoet said:

Why not set up the first site (or a kind of template site), run Site Profile Exporter, copy the created profile into the install package and run the regular installer with that profile for the subsequent domains?

More on this here by @Robin S: https://processwire.com/talk/topic/16350-processwire-and-phpstorm/?do=findComment&comment=145018

You can also clone "your default site" easily with: https://modules.processwire.com/modules/duplicator/ by @flydev
Keep in mind that using Duplicator you will get the same $config->userAuthSalt which is a minor security issue but you can apply the workaround suggested by @horst: https://processwire.com/talk/topic/15265-generate-new-userauthsalt-for-copied-site/?tab=comments#comment-136537

 

 

[bernhard]

I'm not a fan of site profiles... That's why I created ProcessWire Kickstart. I created another explanation of how you can use it in szabesz' linked topic: 

 

[[Code] Specialist]

Hello to all. Thanks a lot for your replies. I will have a look for each this evening and tell you which one would be the best solution for me  

[bernhard]

Not to forget there's also the migrations module:

https://modules.processwire.com/modules/migrations/

https://processwire.com/blog/posts/introduction-migrations-module/

[szabesz]

1 minute ago, bernhard said:

the migrations module

As far as I understand, this module is only about database related migrations and as such not really about setting up ProcessWire. Also, @LostKobrakai doesn't seem to be maintaining it anymore as he seems to be switching to Elixir. 

[bernhard]

22 hours ago, LauschZone said:

How to create a module which:

• create fields and fieldsets and its dependencies (is there a cheatpage for all possibilities ?)
• create template Pages which implements above fields

This is exactly what can be done with the migrations module. It totally depends on his usecase what is the best option.

That it is not maintained does not mean that it does not work  It's only some helper functions around pw's API - and you know how often the api changes... almost never

Maybe copying over site profiles is the best option. But maybe he needs more flexibility then the other options could be handy. And maybe he wants to maintain all of those websites lateron, then site profiles would be totally useless whereas migrations could be shared across the single instances and modify them as needed.

[LostKobrakai]

My migrations module cannot install processwire, nor itself, but after that it can basically do whatever php and the processwire api allows you to do.