Merge branch 'master' of github.com:appwrite/appwrite into 0.7.x
This commit is contained in:
Eldad Fux
commit
3be99e91a6
|
|
@ -10,7 +10,7 @@
|
|||
[](CONTRIBUTING.md)
|
||||
[](https://discord.gg/GSeTUeA)
|
||||
[](https://travis-ci.org/appwrite/appwrite)
|
||||
[](https://travis-ci.org/appwrite/appwrite)
|
||||
[](https://travis-ci.com/appwrite/appwrite)
|
||||
[](https://twitter.com/appwrite_io)
|
||||
[](https://stackshare.io/appwrite)
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Allow the user to login to his account using the OAuth2 provider of his choice. Each OAuth2 provider should be enabled from the Appwrite console first. Use the success and failure arguments to provide a redirect URL's back to your app when login is completed.
|
||||
Allow the user to login to their account using the OAuth2 provider of their choice. Each OAuth2 provider should be enabled from the Appwrite console first. Use the success and failure arguments to provide a redirect URL's back to your app when login is completed.
|
||||
|
|
@ -1 +1 @@
|
|||
Allow the user to login into his account by providing a valid email and password combination. This route will create a new session for the user.
|
||||
Allow the user to login into their account by providing a valid email and password combination. This route will create a new session for the user.
|
||||
|
|
@ -1 +1 @@
|
|||
Use this endpoint to allow a new user to register a new account in your project. After the user registration completes successfully, you can use the [/account/verfication](/docs/client/account#createVerification) route to start verifying the user email address. To allow your new user to login to his new account, you need to create a new [account session](/docs/client/account#createSession).
|
||||
Use this endpoint to allow a new user to register a new account in your project. After the user registration completes successfully, you can use the [/account/verfication](/docs/client/account#createVerification) route to start verifying the user email address. To allow the new user to login to their new account, you need to create a new [account session](/docs/client/account#createSession).
|
||||
|
|
@ -1 +1 @@
|
|||
Use this endpoint to log out the currently logged in user from his account. When successful this endpoint will delete the user session and remove the session secret cookie from the user client.
|
||||
Use this endpoint to log out the currently logged in user from their account. When successful this endpoint will delete the user session and remove the session secret cookie from the user client.
|
||||
|
|
@ -1 +1 @@
|
|||
Use this endpoint to log out the currently logged in user from all his account sessions across all his different devices. When using the option id argument, only the session unique ID provider will be deleted.
|
||||
Use this endpoint to log out the currently logged in user from all their account sessions across all of their different devices. When using the option id argument, only the session unique ID provider will be deleted.
|
||||
|
|
@ -1 +1 @@
|
|||
Delete document by its unique ID. This endpoint deletes only the parent documents, his attributes and relations to other documents. Child documents **will not** be deleted.
|
||||
Delete document by its unique ID. This endpoint deletes only the parent documents, its attributes and relations to other documents. Child documents **will not** be deleted.
|
||||
|
|
@ -1 +1 @@
|
|||
This endpoint allows a user to leave a team or for a team owner to delete the membership of any other team member. You can also use this endpoint to delete a user membership even if he didn't accept it.
|
||||
This endpoint allows a user to leave a team or for a team owner to delete the membership of any other team member. You can also use this endpoint to delete a user membership even if it is not accepted.
|
||||
|
|
@ -1 +1 @@
|
|||
Use this endpoint to allow a user to accept an invitation to join a team after he is being redirected back to your app from the invitation email he was sent.
|
||||
Use this endpoint to allow a user to accept an invitation to join a team after being redirected back to your app from the invitation email recieved by the user.
|
||||
|
|
@ -6,7 +6,7 @@ This document is part of the Appwrite contributors' guide. Before you continue r
|
|||
|
||||
### Agenda
|
||||
|
||||
OAuth2 providers help users to log in easily to apps and websites without the need to provide passwords or any other type of credentials. Appwrite's goal is to have support from as many **major** OAuth2 providers as possible.
|
||||
OAuth2 providers help users to log in to the apps and websites without the need to provide passwords or any other type of credentials. Appwrite's goal is to have support from as many **major** OAuth2 providers as possible.
|
||||
|
||||
As of the writing of these lines, we do not accept any minor OAuth2 providers. For us to accept some smaller and potentially unlimited number of OAuth2 providers, some product design and software architecture changes must be applied first.
|
||||
|
||||
|
|
@ -47,10 +47,10 @@ Please mention in your documentation what resources or API docs you used to impl
|
|||
|
||||
After you finished adding your new provider to Appwrite you should be able to see it in your Appwrite console. Navigate to 'Project > Users > Providers' and check your new provider's settings form.
|
||||
|
||||
Add credentials and check both a successful and a failed login (where the user rejects integration on provider page).
|
||||
Add credentials and check both a successful and a failed login (where the user denies integration on provider page).
|
||||
|
||||
You can test your OAuth2 provider by trying to login using the [OAuth2 method](https://appwrite.io/docs/client/account#createOAuth2Session) when integrating the Appwrite JS SDK in a demo app.
|
||||
|
||||
Pass your new adapter name as the provider parameter. If login is successful, you will be redirected to your success URL parameter. Otherwise, you will be redirected to your failure URL.
|
||||
|
||||
If everything goes well, just submit a pull request and be ready to respond to any feedback which can arise during our code review.
|
||||
If everything goes well, submit a pull request and be ready to respond to any feedback which can arise during our code review.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Environment Variables
|
||||
|
||||
Appwrite environment variables allow you to edit your server setup configuration and customize it. You can easily change the environment variables by changing them when running Appwrite using Docker CLI or Docker-Compose.
|
||||
Appwrite environment variables allow you to edit your server setup configuration and customize it. You can change the environment variables by changing them when running Appwrite using Docker CLI or Docker-Compose.
|
||||
|
||||
## General Options
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ Set your server running environment. By default, the var is set to 'development'
|
|||
|
||||
### _APP_OPTIONS_ABUSE
|
||||
|
||||
Allows you to disable abuse checks and API rate limiting. By default, set to 'enabled'. To cancel the abuse checking, set to 'disabled'. It is not recommended to disable this feature in a production environment.
|
||||
Allows you to turn off abuse checks and API rate limiting. By default, set to 'enabled'. To cancel the abuse checking, set to 'disabled'. It is not recommended to turn off this feature in a production environment.
|
||||
|
||||
### _APP_OPTIONS_FORCE_HTTPS
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Appwrite uses a few containers to run, where each container has its job. Most of
|
|||
|
||||
If you decide to set up a load balancer for a specific container, make sure that the containers that are trying to communicate with it are accessing it through a load balancer and not directly. All connections between Appwrite different containers are set using Docker environment variables.
|
||||
|
||||
There are three Appwrite containers that do keep their state are the MariaDB, Redis, and InfluxDB containers that are used for storing data, cache, and stats (in this order). To scale them out, all you need to do is set up a standard cluster (just like you would with any other app using these technologies) according to your needs and performance.
|
||||
There are three Appwrite containers that do keep their state are the MariaDB, Redis, and InfluxDB containers that are used for storing data, cache, and stats (in this order). To scale them out, all you need to do is set up a standard cluster (same as you would with any other app using these technologies) according to your needs and performance.
|
||||
|
||||
## Sending Emails
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue