@adobe/aem-cli 15.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,74 @@
1
+ # Adobe Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at Grp-opensourceoffice@adobe.com. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
@@ -0,0 +1,64 @@
1
+ # Contributing to Helix-CLI
2
+
3
+ This project is an Open Development/Inner Source project and welcomes contributions from everyone who finds it useful or lacking.
4
+
5
+ ## Code Of Conduct
6
+
7
+ This project adheres to the Adobe [code of conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to cstaub at adobe dot com.
8
+
9
+ ## Contributor License Agreement
10
+
11
+ All third-party contributions to this project must be accompanied by a signed contributor license. This gives Adobe permission to redistribute your contributions as part of the project. [Sign our CLA](http://opensource.adobe.com/cla.html)! You only need to submit an Adobe CLA one time, so if you have submitted one previously, you are good to go!
12
+
13
+ ## Things to Keep in Mind
14
+
15
+ This project uses a **commit then review** process, which means that for approved maintainers, changes can be merged immediately, but will be reviewed by others.
16
+
17
+ For other contributors, a maintainer of the project has to approve the pull request.
18
+
19
+ # Before You Contribute
20
+
21
+ * Check that there is an existing issue in GitHub issues
22
+ * Check if there are other pull requests that might overlap or conflict with your intended contribution
23
+
24
+ # How to Contribute
25
+
26
+ 1. Fork the repository
27
+ 2. Make some changes on a branch on your fork
28
+ 3. Use `npm run check` to make sure your code can run the tests and adheres to the style guide
29
+ 4. Create a pull request from your branch
30
+
31
+ In your pull request, outline:
32
+
33
+ * What the changes intend
34
+ * How they change the existing code
35
+ * If (and what) they breaks
36
+ * Start the pull request with the GitHub issue ID, e.g. #123
37
+
38
+ Lastly, please follow the [pull request template](https://github.com/adobe/helix-cli/blob/master/.github/pull_request_template.md) when submitting a pull request!
39
+
40
+ ## Coding Styleguides
41
+
42
+ We enforce a coding styleguide using `eslint`. As part of your build, run `npm run lint` to check if your code is conforming to the style guide. We do the same for every PR in our CI, so PRs will get rejected if they don't follow the style guide.
43
+
44
+ You can fix some of the issues automatically by running `npx eslint . --fix`.
45
+
46
+ ## Commit message format
47
+
48
+ We use [semantic-release](https://github.com/semantic-release/semantic-release) for release management and require that all commits are properly formatted using the [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines)
49
+
50
+ In order to help you craft a good commit message, we added [commitizen](https://www.npmjs.com/package/commitizen) as dev dependency, so you can just run
51
+
52
+ ```
53
+ $ npm run commit
54
+ ```
55
+
56
+
57
+ # How Contributions get Reviewed
58
+
59
+ One of the maintainers will look at the pull request within one week.
60
+ Feedback on the pull request will be given in writing, in GitHub.
61
+
62
+ # Release Management
63
+
64
+ Releasing is done using [semantic-release](https://github.com/semantic-release/semantic-release), and every (relevant) commit to the `master` branch gets released automatically. The release will update the version number and add the recent changes to the [CHANGELOG.md](./CHANGELOG.md). It will also create a [release](https://github.com/adobe/helix-cli/releases) in github and finally publish the package to the [Adobe organization on npmjs.org](https://www.npmjs.com/org/adobe).
package/LICENSE.txt ADDED
@@ -0,0 +1,264 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
203
+
204
+
205
+ APACHE JACKRABBIT SUBCOMPONENTS
206
+
207
+ Apache Jackrabbit includes parts with separate copyright notices and license
208
+ terms. Your use of these subcomponents is subject to the terms and conditions
209
+ of the following licenses:
210
+
211
+ XPath 2.0/XQuery 1.0 Parser:
212
+ http://www.w3.org/2002/11/xquery-xpath-applets/xgrammar.zip
213
+
214
+ Copyright (C) 2002 World Wide Web Consortium, (Massachusetts Institute of
215
+ Technology, European Research Consortium for Informatics and Mathematics,
216
+ Keio University). All Rights Reserved.
217
+
218
+ This work is distributed under the W3C(R) Software License in the hope
219
+ that it will be useful, but WITHOUT ANY WARRANTY; without even the
220
+ implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
221
+
222
+ W3C(R) SOFTWARE NOTICE AND LICENSE
223
+ http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
224
+
225
+ This work (and included software, documentation such as READMEs, or
226
+ other related items) is being provided by the copyright holders under
227
+ the following license. By obtaining, using and/or copying this work,
228
+ you (the licensee) agree that you have read, understood, and will comply
229
+ with the following terms and conditions.
230
+
231
+ Permission to copy, modify, and distribute this software and its
232
+ documentation, with or without modification, for any purpose and
233
+ without fee or royalty is hereby granted, provided that you include
234
+ the following on ALL copies of the software and documentation or
235
+ portions thereof, including modifications:
236
+
237
+ 1. The full text of this NOTICE in a location viewable to users
238
+ of the redistributed or derivative work.
239
+
240
+ 2. Any pre-existing intellectual property disclaimers, notices,
241
+ or terms and conditions. If none exist, the W3C Software Short
242
+ Notice should be included (hypertext is preferred, text is
243
+ permitted) within the body of any redistributed or derivative code.
244
+
245
+ 3. Notice of any changes or modifications to the files, including
246
+ the date changes were made. (We recommend you provide URIs to the
247
+ location from which the code is derived.)
248
+
249
+ THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT
250
+ HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED,
251
+ INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS
252
+ FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR
253
+ DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
254
+ TRADEMARKS OR OTHER RIGHTS.
255
+
256
+ COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL
257
+ OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
258
+ DOCUMENTATION.
259
+
260
+ The name and trademarks of copyright holders may NOT be used in
261
+ advertising or publicity pertaining to the software without specific,
262
+ written prior permission. Title to copyright in this software and
263
+ any associated documentation will at all times remain with
264
+ copyright holders.
package/README.md ADDED
@@ -0,0 +1,147 @@
1
+ # Helix/AEM Command Line Interface (`aem`)
2
+
3
+ ## Status
4
+
5
+ [![codecov](https://img.shields.io/codecov/c/github/adobe/helix-cli.svg)](https://codecov.io/gh/adobe/helix-cli)
6
+ [![CircleCI](https://img.shields.io/circleci/project/github/adobe/helix-cli/main.svg)](https://circleci.com/gh/adobe/helix-cli/tree/main)
7
+ [![GitHub license](https://img.shields.io/github/license/adobe/helix-cli.svg)](https://github.com/adobe/helix-cli/blob/master/LICENSE.txt)
8
+ [![GitHub issues](https://img.shields.io/github/issues/adobe/helix-cli.svg)](https://github.com/adobe/helix-cli/issues)
9
+ [![LGTM Code Quality Grade: JavaScript](https://img.shields.io/lgtm/grade/javascript/g/adobe/helix-cli.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/adobe/helix-cli)
10
+
11
+ The AEM Command Line Interface allows web developers to create, develop, and deploy digital experiences using the Adobe Experience Manager Sites feature Edge Delivery Services. Some of this functionality was known as Franklin or Project Helix before.
12
+
13
+ ## Installation
14
+
15
+ Install `aem` as a global command. You need Node 12.11 or newer.
16
+
17
+ ```bash
18
+ $ npm install -g @adobe/aem-cli
19
+ ```
20
+
21
+ ## Quick Start
22
+
23
+ ```
24
+ $ aem --help
25
+ Usage: aem <command> [options]
26
+
27
+ Commands:
28
+ aem up Run a AEM development server
29
+
30
+ Options:
31
+ --version Show version number [boolean]
32
+ --log-file, --logFile Log file (use "-" for stdout) [array] [default: "-"]
33
+ --log-level, --logLevel Log level
34
+ [string] [choices: "silly", "debug", "verbose", "info", "warn", "error"]
35
+ [default: "info"]
36
+ --tls-key, --tlsKey Path to .key file (for enabling TLS) [string]
37
+ --tls-cert, --tlsCert Path to .pem file (for enabling TLS) [string]
38
+ --help Show help [boolean]
39
+
40
+ use <command> --help to get command specific details.
41
+
42
+ for more information, find our manual at https://github.com/adobe/helix-cli
43
+ ```
44
+
45
+ ## Starting development
46
+
47
+ ```
48
+ $ cd <my-cool-project>
49
+ $ aem up
50
+ ```
51
+
52
+ ### automatically open the browser
53
+
54
+ The `--open` argument takes a path, eg `--open=/products/`, will cause the browser to be openend
55
+ at the specific location. Disable with `--no-open'.`
56
+
57
+ ### setting up a self-signed cert for using https
58
+
59
+ 1. create the certificate
60
+
61
+
62
+ ```
63
+ $ openssl req -new -newkey rsa:4096 -x509 -sha256 -days 365 -nodes -out server.crt -keyout server.key -subj "/CN=localhost"
64
+ ```
65
+
66
+ this will create 2 files: `server.crt` and `server.key`
67
+
68
+ 2. start aem with tls support
69
+
70
+ ```
71
+ $ aem up --tls-cert server.crt --tls-key server.key
72
+ ___ ________ ___ __ __ v14.26.1
73
+ / | / ____/ |/ / _____(_)___ ___ __ __/ /___ _/ /_____ _____
74
+ / /| | / __/ / /|_/ / / ___/ / __ `__ \/ / / / / __ `/ __/ __ \/ ___/
75
+ / ___ |/ /___/ / / / (__ ) / / / / / / /_/ / / /_/ / /_/ /_/ / /
76
+ /_/ |_/_____/_/ /_/ /____/_/_/ /_/ /_/\__,_/_/\__,_/\__/\____/_/
77
+
78
+ info: Starting AEM dev server v14.26.1
79
+ info: Local AEM dev server up and running: https://localhost:3000/
80
+ ```
81
+
82
+ 3. (optional) Add arguments to .env file:
83
+
84
+ ```
85
+ $ echo -e "AEM_TLS_CERT=server.crt\nAEM_TLS_KEY=server.key" >> .env
86
+ ```
87
+
88
+ ### environment
89
+
90
+ All the command arguments can also be specified via environment variables. the `.env` file is
91
+ loaded automatically.
92
+
93
+ example:
94
+
95
+ `.env`
96
+ ```dotenv
97
+ AEM_OPEN=/products
98
+ AEM_PORT=8080
99
+ AEM_PAGES_URL=https://stage.myproject.com
100
+ ```
101
+
102
+ #### HTTP Proxy
103
+
104
+ In order to use a HTTP proxy (eg behind a corporate firewall), you can set the respective environment variables:
105
+
106
+ `NO_PROXY` is a list of host names (optionally with a port). If the input URL matches any of the entries in `NO_PROXY`, then the input URL should be fetched by a direct request (i.e. without a proxy).
107
+
108
+ Matching follows the following rules:
109
+
110
+ `NO_PROXY=*` disables all proxies.
111
+ Space and commas may be used to separate the entries in the `NO_PROXY` list.
112
+ If `NO_PROXY` does not contain any entries, then proxies are never disabled.
113
+ If a port is added after the host name, then the ports must match. If the URL does not have an explicit port name, the protocol's default port is used.
114
+ Generally, the proxy is only disabled if the host name is an exact match for an entry in the `NO_PROXY` list. The only exceptions are entries that start with a dot or with a wildcard; then the proxy is disabled if the host name ends with the entry.
115
+ See test.js for examples of what should match and what does not.
116
+
117
+ `*_PROXY`
118
+ The environment variable used for the proxy depends on the protocol of the URL. For example, https://example.com uses the "https" protocol, and therefore the proxy to be used is `HTTPS_PROXY` (NOT `HTTP_PROXY`, which is only used for http:-URLs).
119
+
120
+ If present, `ALL_PROXY` is used as fallback if there is no other match.
121
+
122
+ #### Global
123
+
124
+ | option | variable | default | description |
125
+ |--------|----------|---------|-------------|
126
+ | `--log-file` | `AEM_LOG_FILE` | `-` | Log file. use `-` to log to stdout |
127
+ | `--log-level` | `AEM_LOG_LEVEL` | `info` | Log level |
128
+
129
+ #### Up command
130
+
131
+ | option | variable | default | description |
132
+ |-------------------|---------------------|-------------|-------------------------------------------------------------|
133
+ | `--port` | `AEM_PORT` | `3000` | Development server port |
134
+ | `--addr` | `AEM_ADDR` | `127.0.0.1` | Development server bind address |
135
+ | `--livereload` | `AEM_LIVERELOAD` | `true` | Enable automatic reloading of modified sources in browser. |
136
+ | `--no-livereload` | `AEM_NO_LIVERELOAD` | `false` | Disable live-reload. |
137
+ | `--open` | `AEM_OPEN` | `/` | Open a browser window at specified path after server start. |
138
+ | `--no-open` | `AEM_NO_OPEN` | `false` | Disable automatic opening of browser window. |
139
+ | `--tls-key` | `AEM_TLS_KEY` | undefined | Path to .key file (for enabling TLS) |
140
+ | `--tls-cert` | `AEM_TLS_CERT` | undefined | Path to .pem file (for enabling TLS) |
141
+
142
+ # Developing Helix CLI
143
+
144
+ ## Testing
145
+
146
+ You can use `npm run check` to run the tests and check whether your code adheres
147
+ to the aem-cli coding style.
package/index.js ADDED
@@ -0,0 +1,25 @@
1
+ #!/usr/bin/env node
2
+
3
+ /*
4
+ * Copyright 2018 Adobe. All rights reserved.
5
+ * This file is licensed to you under the Apache License, Version 2.0 (the "License");
6
+ * you may not use this file except in compliance with the License. You may obtain a copy
7
+ * of the License at http://www.apache.org/licenses/LICENSE-2.0
8
+ *
9
+ * Unless required by applicable law or agreed to in writing, software distributed under
10
+ * the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR REPRESENTATIONS
11
+ * OF ANY KIND, either express or implied. See the License for the specific language
12
+ * governing permissions and limitations under the License.
13
+ */
14
+
15
+ import CLI from './src/cli.js';
16
+ import { checkNodeVersion, validateDotEnv } from './src/config/config-utils.js';
17
+ import { config } from 'dotenv';
18
+
19
+ config();
20
+
21
+ (async () => {
22
+ await checkNodeVersion();
23
+ await validateDotEnv();
24
+ await new CLI().run(process.argv.slice(2));
25
+ })();
package/package.json ADDED
@@ -0,0 +1,97 @@
1
+ {
2
+ "name": "@adobe/aem-cli",
3
+ "version": "15.0.0",
4
+ "description": "AEM CLI",
5
+ "main": "index.js",
6
+ "type": "module",
7
+ "bin": {
8
+ "hlx": "./index.js",
9
+ "aem": "./index.js"
10
+ },
11
+ "scripts": {
12
+ "check": "npm run lint && npm run test",
13
+ "test": "c8 mocha",
14
+ "test-ci-win": "npx mocha --reporter xunit test --reporter-options output=junit/test.xml -t 5000",
15
+ "lint": "eslint .",
16
+ "semantic-release": "semantic-release",
17
+ "prepare": "husky install"
18
+ },
19
+ "mocha": {
20
+ "require": "test/setup-env.js",
21
+ "recursive": "true",
22
+ "reporter": "mocha-multi-reporters",
23
+ "reporter-options": "configFile=.mocha-multi.json",
24
+ "loader": "esmock"
25
+ },
26
+ "repository": {
27
+ "type": "git",
28
+ "url": "https://github.com/adobe/helix-cli.git"
29
+ },
30
+ "author": "",
31
+ "license": "Apache-2.0",
32
+ "bugs": {
33
+ "url": "https://github.com/adobe/helix-cli/issues"
34
+ },
35
+ "homepage": "https://github.com/adobe/helix-cli#readme",
36
+ "engines": {
37
+ "node": ">=14"
38
+ },
39
+ "dependencies": {
40
+ "@adobe/fetch": "4.1.0",
41
+ "@adobe/helix-log": "6.0.0",
42
+ "@adobe/helix-shared-config": "10.3.5",
43
+ "@adobe/helix-shared-git": "3.0.2",
44
+ "@adobe/helix-shared-indexer": "2.0.14",
45
+ "camelcase": "8.0.0",
46
+ "chalk-template": "1.1.0",
47
+ "chokidar": "3.5.3",
48
+ "compression": "1.7.4",
49
+ "cookie": "0.5.0",
50
+ "cookie-parser": "1.4.6",
51
+ "dotenv": "16.3.1",
52
+ "express": "4.18.2",
53
+ "faye-websocket": "0.11.4",
54
+ "fs-extra": "11.1.1",
55
+ "glob": "10.3.6",
56
+ "glob-to-regexp": "0.4.1",
57
+ "hast-util-select": "6.0.0",
58
+ "http-proxy-agent": "7.0.0",
59
+ "https-proxy-agent": "7.0.2",
60
+ "ignore": "5.2.4",
61
+ "ini": "4.1.1",
62
+ "isomorphic-git": "1.24.5",
63
+ "livereload-js": "4.0.1",
64
+ "node-fetch": "3.3.2",
65
+ "open": "9.1.0",
66
+ "progress": "2.0.3",
67
+ "proxy-agent": "6.3.1",
68
+ "proxy-from-env": "1.1.0",
69
+ "rehype-parse": "9.0.0",
70
+ "semver": "7.5.4",
71
+ "shelljs": "0.8.5",
72
+ "unified": "11.0.2",
73
+ "uuid": "9.0.1",
74
+ "yargs": "17.7.2"
75
+ },
76
+ "devDependencies": {
77
+ "@adobe/eslint-config-helix": "2.0.3",
78
+ "@adobe/helix-shared-dom": "2.0.1",
79
+ "@adobe/helix-testutils": "0.4.14",
80
+ "@semantic-release/changelog": "6.0.3",
81
+ "@semantic-release/git": "10.0.1",
82
+ "c8": "8.0.1",
83
+ "eslint": "8.50.0",
84
+ "esmock": "2.5.1",
85
+ "husky": "8.0.3",
86
+ "junit-report-builder": "3.0.1",
87
+ "lint-staged": "14.0.1",
88
+ "mocha": "10.2.0",
89
+ "mocha-multi-reporters": "1.5.1",
90
+ "nock": "13.3.3",
91
+ "semantic-release": "22.0.4",
92
+ "sinon": "16.0.0"
93
+ },
94
+ "lint-staged": {
95
+ "*.js": "eslint"
96
+ }
97
+ }