Skip to content
This repository was archived by the owner on Sep 29, 2023. It is now read-only.

Commit cfaa8d0

Browse files
authored
Merge pull request #37 from appwrite/fix-env-to-runtime
Updated naming conventions
2 parents 75737e6 + 2b11a8a commit cfaa8d0

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

app/views/docs/architecture.phtml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ $image = new View(__DIR__.'/../general/image.phtml');
5555

5656
<p><b>Functions</b></p>
5757

58-
<p>The Functions worker is responsible for executing your Appwrite cloud functions in an isolated environment. The service leverages Docker for creating running environment in multiple supported coding languages.</p>
58+
<p>The Functions worker is responsible for executing your Appwrite cloud functions in an isolated runtime environment. The service leverages Docker for creating running environment in multiple supported coding languages.</p>
5959

6060
<p><b>Audits</b></p>
6161

app/views/docs/functions.phtml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ $runtimes = $this->getParam('runtimes', []);
8686

8787
<p>If your code uses a package manager like NPM, Yarn, or Composer to install packages, you have to make sure your code directory includes your packages directory (node_modules for node or vendor for PHP) before you try to package and deploy your code.</p>
8888

89-
<p>If you're using a programming language that saves your packages under a global directory like Dart, Python or Ruby, you should set your package manager to keep your code under the '.appwrite' code directory under your code working directory to be deployed and available in your cloud functions environment.</p>
89+
<p>If you're using a programming language that saves your packages under a global directory like Dart, Python or Ruby, you should set your package manager to keep your code under the '.appwrite' code directory under your code working directory to be deployed and available in your cloud functions runtime.</p>
9090

9191
<p>For most languages, this can be achieved easily by adding an environment variable before installing your dependencies. Below you can find some simple examples:</p>
9292

@@ -221,7 +221,7 @@ void main() { // Init SDK
221221

222222
<h2>Environment Variables</h2>
223223

224-
<p>Environment variables supplied by Appwrite in addition to your own defined environment variables that you can access from your function code. These variables give you information about your execution environment.</p>
224+
<p>Environment variables supplied by Appwrite in addition to your own defined environment variables that you can access from your function code. These variables give you information about your execution runtime environment.</p>
225225

226226
<table cellspacing="0" cellpadding="0" border="0" class="full margin-bottom-large">
227227
<thead>
@@ -259,13 +259,13 @@ void main() { // Init SDK
259259
<td>
260260
APPWRITE_FUNCTION_RUNTIME_NAME
261261
</td>
262-
<td>Your function environment name. Can be any of Appwrite supported execution environments.</td>
262+
<td>Your function runtime name. Can be any of Appwrite supported execution environments.</td>
263263
</tr>
264264
<tr>
265265
<td>
266266
APPWRITE_FUNCTION_RUNTIME_VERSION
267267
</td>
268-
<td>Your function environment version.</td>
268+
<td>Your function runtime version.</td>
269269
</tr>
270270
<tr>
271271
<td>

0 commit comments

Comments
 (0)