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
Copy file name to clipboardExpand all lines: docs/contributing/documentation/admins.md
+48Lines changed: 48 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,3 +82,51 @@ To make it easier for other contributors to work with your project, update the f
82
82
- Optionally set a branch to work on in`.gitmodules`.
83
83
84
84
Commit and push your changes to a remote, and submit a pull request against [`plone/[email protected]`](https://github.com/plone/documentation/compare).
85
+
86
+
87
+
## Add a project to Netlify
88
+
89
+
To add a new site to Netlify to preview built documentation or storybooks, you need to add a new site to Netlify.
1. Click {guilabel}`Add a new site` and select{guilabel}`Import an existing project`.
93
+
1. Click {guilabel}`Deploy with GitHub`.
94
+
1. Select {guilabel}`plone`for the GitHub organization.
95
+
1. Click {guilabel}`Configure Netlify on GitHub`.
96
+
1. Select the organization to where you want to install Netlify.
97
+
1. Click {guilabel}`Select repositories` and selectthe repository that you want to add.
98
+
1. Click {guilabel}`Update access`.
99
+
1. Netlify sends an email to members of the email group `admins` at `plone.org`, who need to review and approve the request.
100
+
However the email doesn't specify the repository, and admins will not know what to do.
101
+
You must send email to that group, including in your request the organization and repository, such as `plone/volto`.
102
+
1. The admin must login to GitHub as an organization owner, then navigate to the requested repository's {guilabel}`Settings`. [What else Admin person?]
103
+
1. The admin replies to the requestor, letting them know the request was approved.
104
+
105
+
From here you need to update your repository to work with Netlify.
106
+
For an example, see the following files.
107
+
108
+
- [Volto `Makefile`](https://github.com/plone/volto/blob/main/Makefile), specifically the `netlify` section.
109
+
This will become the command used to build docs on Netlify.
110
+
- [Volto `requirements-docs.txt`](https://github.com/plone/volto/blob/main/requirements-docs.txt) specifies the requirements to build the docs.
111
+
- [Volto `netlify.toml`](https://github.com/plone/volto/blob/main/netlify.toml) specifies when to build the docs, specifically only when there are changes to documentation files.
112
+
113
+
Finally you need to configure your site in Netlify.
114
+
You may have done some of these steps earlier, but you might need to refine them.
115
+
The critical pieces are the following.
116
+
117
+
1. From the dashboard, selectthe site to edit it.
118
+
1. Click {guilabel}`Site configuration`.
119
+
1. One time only, under {guilabel}`General > Site details` click {guilabel}`Change site name`.
120
+
A modal dialog appears.
121
+
Enter the site name using the pattern `ORGANIZATION_NAME-REPOSITORY_NAME`.
122
+
For example, `plone-components`.
123
+
Click {guilabel}`Save`.
124
+
1. Under {guilabel}`Build & deploy > Continuous deployment`, scroll to {guilabel}`Build settings`, and click {guilabel}`Configure`, then enter the following values.
125
+
- {guilabel}`Base directory`: `/`
126
+
- {guilabel}`Package directory`: `/`
127
+
- {guilabel}`Build command`: `make netlify`.
128
+
This is the command you would define in your `Makefile`.
129
+
- {guilabel}`Publish directory`: `_build/html`.
130
+
This is where the `make`command will output files.
131
+
- Finally click {guilabel}`Save`.
132
+
1. Under {guilabel}`Build & deploy > Continuous deployment`, scroll to {guilabel}`Branches and deploy contexts`, and click {guilabel}`Configure`, then enter appropriate values.
The Plone [Release Team](https://plone.org/community/teams/release-team) manages the release of new versions of Plone.
148
+
149
+
We use [`zest.releaser`](https://zestreleaser.readthedocs.io/en/latest/) for releasing the Python packages used in Plone, including [Plone core (`Products.CMFPlone`)](https://github.com/plone/Products.CMFPlone/), {doc}`/classic-ui/index`, {doc}`/plone.restapi/docs/source/index`, {doc}`/plone.api/index`, and {doc}`/backend/index`.
150
+
151
+
We use [`release-it`](https://github.com/release-it/release-it) for releasing the Node.js packages used in Plone, including {doc}`Volto </volto/index>` and the [Classic UI mockup](https://github.com/plone/mockup).
Copy file name to clipboardExpand all lines: docs/install/install-from-packages.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,17 +28,28 @@ Plone 6 has both hardware requirements and software pre-requisites.
28
28
29
29
The hardware requirements below give a rough estimate of the minimum hardware setup needed for a Plone server.
30
30
31
-
{term}`Add-on` products and caching solutions may increase RAM requirements.
32
-
33
31
A single Plone installation is able to run many Plone sites.
34
32
You may host multiple Plone sites on the same server.
35
33
36
-
- Minimum 256 MB RAM and 512 MB of swap space per Plone site is required.
34
+
- Installation of the Plone backend and Classic UI frontend requires a minimum of 256 MB of RAM and 2GB of disk swap space.
35
+
- Installation of the Volto frontend requires a minimum of 2GB of RAM.
36
+
- After installation, running Plone requires a minimum of 256 MB RAM and 512 MB of disk swap space per Plone site.
37
37
2 GB or more RAM per Plone site is recommended.
38
38
- Minimum 512 MB hard disk space is required.
39
39
40 GB or more hard disk space is recommended.
40
40
41
41
42
+
````{warning}
43
+
{term}`Add-on` products and caching solutions may also increase RAM and disk swap space requirements.
44
+
45
+
To avoid RAM and disk swap limitations, we recommend either temporarily resizing your remote machine to accommodate the build, or build your images locally and upload them to an image store, such as [Docker Hub](https://hub.docker.com/) or [GitHub Packages](https://github.com/features/packages).
46
+
47
+
```{seealso}
48
+
[How much RAM is required to build a Volto front end?](https://community.plone.org/t/how-much-ram-is-required-to-build-a-volto-front-end/17949) and [Dealing with heap exhaustion while building Volto 17 on limited-RAM host](https://community.plone.org/t/dealing-with-heap-exhaustion-while-building-volto-17-on-limited-ram-host/18078).
0 commit comments