You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.
Can you please provide more documentation on setting up a multi-site install with shared resources? The docs do mention it briefly, but a dedicated page would be appreciated!
For Example:
One Domain with Multiple Subdomains
Say I have domain.com as my main site and want to setup a few subdomained sites with similar design. These will be something like products.domain.com, support.domain.com, etc. They will share the same assets such as CSS, JS, Images, etc. Since they are separate subdomains they will need to be output to different folders and have separate config.json files.
The text was updated successfully, but these errors were encountered:
Easiest would be to have a config.json for each site, which instructs to use a common template directory and different content directories to output into different directories (eg. products.domain.com)
Then you will need to run punch g config1.json to generate each site. I will see whether I can improve the generate command to look and execute multiple configs.
So each site has to be output manually? I thought I read something in the docs about putting them in subfolders to allow multiple sites on one install and shared resources?
Can you please provide more documentation on setting up a multi-site install with shared resources? The docs do mention it briefly, but a dedicated page would be appreciated!
For Example:
One Domain with Multiple Subdomains
Say I have domain.com as my main site and want to setup a few subdomained sites with similar design. These will be something like products.domain.com, support.domain.com, etc. They will share the same assets such as CSS, JS, Images, etc. Since they are separate subdomains they will need to be output to different folders and have separate config.json files.
The text was updated successfully, but these errors were encountered: