NurtureSite
(435) 465-1595

Reference

Factory admin — provisioning

Internal: create sites, deployments, and template sync.

Audience: NurtureSite factory administrators (not site owners).

Create a site

  1. Log in as factory admin (is_admin or factory_admin role).
  2. Open Admin → Provision (/admin/provision) or use customer onboarding at /register.
  3. Submit business details — a deployment is queued on the queue worker.

Monitor deployment

  • Admin → Deployments — status, logs, redeploy
  • Ensure queue and scheduler containers are running locally

After deploy

Research then confirm the CRM noun (Customer, Patient, Household, Lead, …) and offering noun during provisioning. Sequence send-audience default follows the CRM noun (Patient → send-to, Student → all contacts, Household → primary) — no extra question. A separate yes/no next to the noun can turn on website logins for the people that site serves. See Website logins.

Demo document packages seed after booking types exist (dental required waiver on New patient exam; fitness class optional; preschool deposit after forms; restaurant library-only). Packages live on the site DB — factory does not store completed envelopes. See Forms, waivers, and e-sign.

./vendor/bin/sail artisan crm:ensure-settings --push
./vendor/bin/sail artisan analytics:ensure-settings --push
./vendor/bin/sail artisan factory:integration:verify-local --slug={slug}

Template updates

When laravel-cms changes:

./vendor/bin/sail artisan factory:sites:sync-template --sync-env --rebuild

Sales CRM sync

Customers can enable sync leads to NurtureSite CRM on their site settings page. Mirroring uses signed webhooks — see technical doc CRM_SYNC on the template repo.

Related: Managing a site, Two dashboards, Forms, waivers, and e-sign.

Related articles