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
To set up a working **development environment**, just fork the project git repository and install the backend and frontend dependencies using the proper package manager and run the docker-compose stack.
114
+
To set up a working **development environment**, just fork the project git repository and install the backend and frontend dependencies using the proper package manager and create run the docker-compose stack.
115
115
116
116
> If you just want to install Appwrite for day-to-day use and not as a contributor, you can reference the [installation guide](https://github.com/appwrite/appwrite#installation), the [getting started guide](https://appwrite.io/docs/quick-starts), or the main [README](README.md) file.
117
117
@@ -173,12 +173,12 @@ Learn more at our [Technology Stack](#technology-stack) section.
Other containers should be named the same as their service, for example `redis` should just be called `redis`.
181
+
Other containes should be named the same as their service, for example `redis` should just be called `redis`.
182
182
183
183
##### Security
184
184
@@ -189,7 +189,7 @@ Other containers should be named the same as their service, for example `redis`
189
189
190
190
## Modules
191
191
192
-
As Appwrite grows, we noticed approach of having all service endpoints in `app/controllers/api/[service].php` is not maintainable. Not only it creates massive files, it also doesn't contain all product's features such as workers or tasks. While there might still be some occurrences of those controller files, we avoid it in all new development, and gradually migrate existing controllers to **HTTP modules**.
192
+
As Appwrite grows, we noticed approach of having all service endpoints in `app/controllers/api/[service].php` is not maintainable. Not only it creates massive files, it also doesnt contain all product's features such as workers or tasks. While there might still be some occurances of those controller files, we avoid it in all new development, and gradually migrate existing controllers to **HTTP modules**.
193
193
194
194
### HTTP Endpoints
195
195
@@ -204,7 +204,7 @@ Tips and tricks:
204
204
1. If endpoint doesn't have resource, use service name as resource name too
205
205
> Example: `Modules/Sites/Http/Sites/Get.php`
206
206
207
-
2. If there are multiple resources, use them all in folder structure
207
+
2. If there are multiple resources, use then all in folder structure
3. Action can only be `Get`, `Create`, `Update`, `Delete` or `XList`
@@ -395,7 +395,7 @@ These are the current metrics we collect usage stats for:
395
395
396
396
> Note: The curly brackets in the metric name represents a template and is replaced with a value when the metric is processed.
397
397
398
-
Metrics are collected within 3 scopes Daily, monthly, and infinity. Adding new usage metric in order to aggregate usage stats is very simple, but very much dependent on where do you want to collect
398
+
Metrics are collected within 3 scopes Daily, monthly, an infinity. Adding new usage metric in order to aggregate usage stats is very simple, but very much dependent on where do you want to collect
399
399
statistics ,via API or via background worker. For both cases you will need to add a `const` variable in `app/init.php` under the usage metrics list using the naming convention `METRIC_<RESOURCE_NAME>` as shown below.
Appwrite Functions are automatically given a domain you can visit to execute the function. This domain has format `[SOMETHING].functions.localhost` unless you changed `_APP_DOMAIN_FUNCTIONS` environment variable. This default value works great when running Appwrite locally, but it can be impossible to use preview domains with Cloud workspaces such as Gitpod or GitHub Codespaces.
664
+
Appwrite Functions are automatically given a domain you can visit to execute the function. This domain has format `[SOMETHING].functions.localhost` unless you changed `_APP_DOMAIN_FUNCTIONS` environment variable. This default value works great when running Appwrite locally, but it can be impossible to use preview domains with Cloud woekspaces such as Gitpod or GitHub Codespaces.
665
665
666
666
To use preview domains on Cloud workspaces, you can visit hostname provided by them, and supply function's preview domain as URL parameter:
if (version_compare($responseFormat, '1.9.0', '<')) {
943
-
$response->addFilter(newResponseV21());
944
-
}
945
-
if (version_compare($responseFormat, '1.8.0', '<')) {
946
-
$response->addFilter(newResponseV20());
935
+
if (version_compare($responseFormat, '1.4.0', '<')) {
936
+
$response->addFilter(newResponseV16());
947
937
}
948
-
if (version_compare($responseFormat, '1.7.0', '<')) {
949
-
$response->addFilter(newResponseV19());
938
+
if (version_compare($responseFormat, '1.5.0', '<')) {
939
+
$response->addFilter(newResponseV17());
950
940
}
951
941
if (version_compare($responseFormat, '1.6.0', '<')) {
952
942
$response->addFilter(newResponseV18());
953
943
}
954
-
if (version_compare($responseFormat, '1.5.0', '<')) {
955
-
$response->addFilter(newResponseV17());
956
-
}
957
-
if (version_compare($responseFormat, '1.4.0', '<')) {
958
-
$response->addFilter(newResponseV16());
944
+
if (version_compare($responseFormat, '1.7.0', '<')) {
945
+
$response->addFilter(newResponseV19());
959
946
}
960
947
if (version_compare($responseFormat, APP_VERSION_STABLE, '>')) {
961
948
$warnings[] = "The current SDK is built for Appwrite " . $responseFormat . ". However, the current Appwrite server version is " . APP_VERSION_STABLE . ". Please downgrade your SDK to match the Appwrite version: https://appwrite.io/docs/sdks";
0 commit comments