Fix and improve formatting
This commit is contained in:
parent
20e5744903
commit
6171f52fc7
1 changed files with 3 additions and 3 deletions
|
@ -68,7 +68,7 @@ If you are creating a specialized build of Drutopia, you will have to add that t
|
|||
|
||||
```{note}
|
||||
New builds should be added **only** as absolutely required. Configuration, and themes should be leveraged as much as possible prior to resorting to a new build. If additional modules are required, consider adding them to `build_source`, knowing they will be available for *all* Drutopia SaaS sites.
|
||||
``:
|
||||
```:
|
||||
|
||||
Create a new site (member entry) per instructions in Drutopia hosting. The simplest method is to use `ahoy new-site <member-slug>` and follow its output to get started. Then use `ahoy deploy-site <member-instance>` to deploy one. Because the install using `drush site-install` that would be run when `drupal_install: true` is set in the site settings in Drutopia hosting, it is currently recommended to set this to false and use the UI installer or run `php docroot/core/scripts/drupal quick-start drutopia --no-interaction` when ssh'd into the server.
|
||||
|
||||
|
@ -76,7 +76,7 @@ Create a new site (member entry) per instructions in Drutopia hosting. The simpl
|
|||
|
||||
The [drush site aliases file](https://github.com/drush-ops/drush/blob/9.5.x/examples/example.site.yml) can be used to provide easy access to the live/test instances of a site. From the root of your project directory (e.g. `agaric/sites/example/`), you may create one with:
|
||||
|
||||
```
|
||||
```bash
|
||||
MY_SITE="example-com"
|
||||
SERVER="drutopia.org"
|
||||
mkdir -p drush/sites/
|
||||
|
@ -98,7 +98,7 @@ test:
|
|||
EOF
|
||||
```
|
||||
|
||||
This will create a self.site.yml using the expected pattern of "site_name_INSTANCE" (e.g. example_com_live for the example-com live instance). Supply the URL form of the site name for the MY_SITE variable (i.e. with dashes, rather than underscores).
|
||||
This will create a self.site.yml using the expected pattern of `site_name_INSTANCE` (e.g. `example_com_live` for the example-com live instance). Supply the URL form of the site name for the `MY_SITE` variable (i.e. with dashes, rather than underscores).
|
||||
|
||||
### Syncing, and setting up configuration
|
||||
|
||||
|
|
Loading…
Reference in a new issue