Jump to content

Recommended Posts

Posted

i'm going to build up a structure with 2 PW sites:

  1. site A is a inhouse data site set up with PW and containing sensitive and publicable content as well.
  2. site B is a public facing website which shows a part of the site A data which his meant for publication.

site A runs locally when needed, if content is created/updated/deleted on this site.
during this, site A will be temporarily exposed to the web (e.g. dnydns or ngrok) and site B should sync itself now with the new/changed data from site A and pull content from site A via JSON.
this occasional sync process should be invoked manually from site B backend.

my questions are:

  • did some one of you build such a construction?
  • do you have a rough idea how to achieve this?
  • are there helpful modules supporting such tasks?

i'm already familiar with building pages from external rest endpoints for migration of WP or drupal sites to PW.

any ideas/hints/pointers are highly appreciated

thanks thomas

Posted

I seems to me that you have a pretty clear idea overall on how to do it.

The closest I've done to this I decided to use queues to handle anything having to import through that, since I had to import images too so didn't want to go into timeout issues. So the import action actually got triggered from Site A on a Page:saved hook, which passed the page ID to an endpoint in Site B, which then triggered the creation of a queue item that then got back to an "import endpoint" on Site A. The processing on Site B is managed by supervisor. 

The part I wouldn't know how to solve is how to temporarily setup the reverse proxy with dyndns/ngrok. First thing that comes to my mind is to maybe have a cloud based thing in the middle like Amazon SQS so you can organize the work of Site A and Site B in one place.

  • Like 2
Posted (edited)
On 5/4/2025 at 7:02 PM, ttbb said:

i'm going to build up a structure with 2 PW sites:

  1. site A is a inhouse data site set up with PW and containing sensitive and publicable content as well.
  2. site B is a public facing website which shows a part of the site A data which his meant for publication.

site A runs locally when needed, if content is created/updated/deleted on this site.
during this, site A will be temporarily exposed to the web (e.g. dnydns or ngrok) and site B should sync itself now with the new/changed data from site A and pull content from site A via JSON.
this occasional sync process should be invoked manually from site B backend.

my questions are:

  • did some one of you build such a construction?
  • do you have a rough idea how to achieve this?
  • are there helpful modules supporting such tasks?

i'm already familiar with building pages from external rest endpoints for migration of WP or drupal sites to PW.

any ideas/hints/pointers are highly appreciated

thanks thomas

Any update?

 

Edit: Seems no.

Edited by JosephineNeill

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...