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: LICENSE.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Copyright (c) 2025 Appwrite (https://appwrite.io) and individual contributors.
1
+
Copyright (c) 2026 Appwrite (https://appwrite.io) and individual contributors.
2
2
All rights reserved.
3
3
4
4
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
@@ -9,4 +9,4 @@ Redistribution and use in source and binary forms, with or without modification,
9
9
10
10
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
11
11
12
-
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
12
+
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
**This SDK is compatible with Appwrite server version 1.8.x. For older versions, please check [previous releases](https://github.com/appwrite/sdk-for-cli/releases).**
10
10
11
-
Appwrite is an open-source backend as a service server that abstract and simplify complex and repetitive development tasks behind a very simple to use REST API. Appwrite aims to help you develop your apps faster and in a more secure way. Use the Command Line SDK to integrate your app with the Appwrite server to easily start interacting with all of Appwrite backend APIs and tools. For full API documentation and tutorials go to [https://appwrite.io/docs](https://appwrite.io/docs)
11
+
Appwrite is an open-source backend as a service server that abstracts and simplifies complex and repetitive development tasks behind a very simple to use REST API. Appwrite aims to help you develop your apps faster and in a more secure way. Use the Command Line SDK to integrate your app with the Appwrite server to easily start interacting with all of Appwrite backend APIs and tools. For full API documentation and tutorials go to [https://appwrite.io/docs](https://appwrite.io/docs)
@@ -17,7 +17,6 @@ Appwrite is an open-source backend as a service server that abstract and simplif
17
17
The Appwrite CLI is a Node based command line tool to help you interact with the Appwrite API. The CLI is distributed both as an [`npm package`](https://www.npmjs.com/package/appwrite-cli) as well as [pre built binaries](https://github.com/appwrite/sdk-for-cli/releases/latest) for specific operating systems and architectures.
18
18
19
19
### Install using NPM
20
-
21
20
---
22
21
23
22
If you have `npm` installed, it's as easy as running
@@ -30,99 +29,88 @@ Once the installation is complete, you can verify the install using
30
29
31
30
```sh
32
31
$ appwrite -v
33
-
13.0.0-rc.2
32
+
13.0.0-rc.3
34
33
```
35
34
36
35
### Install using prebuilt binaries
37
-
38
36
---
39
37
40
38
If you do not have `npm` installed, you can always install the prebuilt binaries for your architecture and OS using our convenient installation scripts.
This will also prompt you to enter your Appwrite endpoint ( default: http://localhost/v1 )
86
78
87
-
This will also prompt you to enter your Appwrite endpoint ( default: http://localhost/v1 )
88
-
89
-
-### Initialising your project
90
-
Once logged in, the CLI needs to be initialised before you can use it with your Appwrite project. You can do this with the `appwrite init project` command.
79
+
*### Initialising your project
80
+
Once logged in, the CLI needs to be initialised before you can use it with your Appwrite project. You can do this with the `appwrite init project` command.
91
81
92
82
```sh
93
83
$ appwrite init project
94
84
```
95
85
96
86
The following prompt will guide you through the setup process. The `init` command also creates an `appwrite.json` file representing your Appwrite project.
97
87
98
-
The `appwrite.json` file does a lot of things.
99
-
100
-
- Provides context to the CLI
101
-
- Keeps track of all your cloud functions
102
-
- Keeps track of all your project's collections
103
-
- Helps you deploy your Appwrite project to production and more..
88
+
The `appwrite.json` file does a lot of things.
89
+
* Provides context to the CLI
90
+
* Keeps track of all your cloud functions
91
+
* Keeps track of all your project's collections
92
+
* Helps you deploy your Appwrite project to production and more..
104
93
105
94
You can also fetch all the collections in your current project using
106
-
107
95
```sh
108
96
appwrite init collection
109
97
```
110
98
111
-
-### Creating and deploying cloud functions
99
+
*### Creating and deploying cloud functions
112
100
113
101
The CLI makes it extremely easy to create and deploy Appwrite's cloud functions. Initialise your new function using
114
102
115
103
```
116
104
$ appwrite init function
117
105
? What would you like to name your function? My Awesome Function
118
106
? What runtime would you like to use? Node.js (node-15.5)
119
-
✓ Success
107
+
✓ Success
120
108
```
121
109
122
110
This will create a new function `My Awesome Function` in your current Appwrite project and also create a template function for you to get started.
123
111
124
112
```sh
125
-
$ tree My\ Awesome\ Function
113
+
$ tree My\ Awesome\ Function
126
114
127
115
My Awesome Function
128
116
├── README.md
@@ -133,7 +121,7 @@ My Awesome Function
133
121
0 directories, 4 files
134
122
```
135
123
136
-
You can now deploy this function using
124
+
You can now deploy this function using
137
125
138
126
```sh
139
127
$ appwrite push function
@@ -145,56 +133,50 @@ $ appwrite push function
145
133
146
134
Your function has now been deployed on your Appwrite server! As soon as the build process is finished, you can start executing the function.
147
135
148
-
-### Deploying Collections
136
+
*### Deploying Collections
149
137
150
-
Similarly, you can deploy all your collections to your Appwrite server using
138
+
Similarly, you can deploy all your collections to your Appwrite server using
151
139
152
140
```sh
153
141
appwrite push collections
154
142
```
155
143
156
144
> ### Note
157
-
>
158
145
> By default, requests to domains with self signed SSL certificates (or no certificates) are disabled. If you trust the domain, you can bypass the certificate validation using
159
-
160
146
```sh
161
147
$ appwrite client --selfSigned true
162
148
```
163
149
164
-
## Usage
150
+
## Usage
165
151
166
152
The Appwrite CLI follows the following general syntax.
-`data` must be a valid JSON string where each key and value are enclosed in double quotes `"` like the example above.
188
171
- Some arguments like the `read` and `write` permissions are expected to be arrays. In the Appwrite CLI, array values are passed in using space as a separator like in the example above.
189
172
190
-
To get information about the different services available, you can use
191
173
174
+
To get information about the different services available, you can use
192
175
```sh
193
176
$ appwrite -h
194
177
```
195
178
196
-
To get information about a particular service and the commands available in a service you can use
197
-
179
+
To get information about a particular service and the commands available in a service you can use
198
180
```sh
199
181
$ appwrite users // or
200
182
$ appwrite users --help // or
@@ -206,7 +188,7 @@ To get information about a particular command and the parameters it accepts, you
206
188
207
189
```sh
208
190
$ appwrite users list --help
209
-
$ appwrite account get --help
191
+
$ appwrite account get --help
210
192
```
211
193
212
194
At any point, you can view or reset the CLI configuration using the `client` service.
@@ -219,53 +201,48 @@ $ appwrite client --reset
219
201
220
202
## CI mode
221
203
222
-
The Appwrite CLI can also work in a CI environment. The initialisation of the CLI works a bit differently in CI. In CI, you set your `endpoint`, `projectId` and `API Key` using
204
+
The Appwrite CLI can also work in a CI environment. The initialisation of the CLI works a bit differently in CI. In CI, you set your `endpoint`, `projectId` and `API Key` using
This library is auto-generated by Appwrite custom [SDK Generator](https://github.com/appwrite/sdk-generator). To learn more about how you can help us improve this SDK, please check the [contribution guide](https://github.com/appwrite/sdk-generator/blob/master/CONTRIBUTING.md) before sending a pull-request.
231
214
232
-
To build and test the CLI for development, follow these steps
215
+
To build and test the CLI for development, follow these steps
233
216
234
217
1. Clone the SDK Generator repository and cd into the directory
0 commit comments