Same domain – best practice

  • Resolved TonyPrower

    (@tonyprower)


    1 year, 9 months ago

    What is the best practice for keeping the source website away from the public access while allowing the static site to be generated?

    I am working on a multi-site setup where sites are kept ‘archived’ while their static versions are public on the same domain.

    I have to un-archive each site before generating the static site. This will be problematic if the number of sites grows with other users.

    I have tried making the sites password protected, but then I just generate a lot of login pages.

Viewing 1 replies (of 1 total)
  • Plugin Author patrickposner

    (@patrickposner)

    Hey @tonyprower,

    thanks for reaching out!

    The best practice for this is Basic Auth. You protect the subsite (or the entire network) with basic auth and add the credentials in Simply Static -> Settings->Advanced.

    This way, the WP website isn’t available to the public, but Simply Static can still access and convert it as it will authenticate before making any requests.

    Best regards,

    Patrick

Viewing 1 replies (of 1 total)
  • The topic ‘Same domain – best practice’ is closed to new replies.