headwirecom / percli Goto Github PK

View Code? Open in Web Editor NEW

3.0 6.0 10.0 406 KB

peregrine cli tool

License: Apache License 2.0

JavaScript 99.00% Java 1.00%

percli's Introduction

percli - cli tool for peregrine cms

about peregrine-cms

peregrine-cms is an API first headless content management system with a beautiful head built with VueJS

For more information about this project go to http://www.peregrine-cms.com/

We are currently in an alpha development phase

about percli

percli is a command line tool to accomplish general tasks that arise when working

prerequisits

the following tools need to be installed and accessible for percli to be able to work

Java8 for sling9, java8,11+ for sling11
Maven3.2+ to use percli compile
NodeJS 10.16.0 (LTS)

install percli

npm install percli -g

install peregrine-cms

percli server install --sling 11

note: --sling 11 or -s 11 will force the install to use the sling 11 version of peregrine. This can be omitted. If not present, percli will install peregrine with sling9. Sling9 however is an older version of sling and the default of percli server install will soon move to sling 11.

start an already installed peregrine-cms instance

percli server start

percli's People

Contributors

Stargazers

Watchers

Forkers

gastongonzalez dna113p hsaginor swapnilmmane hotwax schaefa solutas qial cmrockwell gaohangdy

percli's Issues

percli server install, Missing Package

Running percli server install --sling 11 fails to complete due to missing file

https://vagrant.headwire.com/peregrine/sling11/themecleanflex.ui.apps-1.0-SNAPSHOT.zip

➜ sling-author4 percli server install --sling 11 --author --name sling11-author1

Percli hatch not working

After editing a component's markup, it won't let me compile it to vue

New project build failed

Hi
I can not create a new project via percli.

$ percli create project testproject

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-archetype-plugin:3.2.0:generate (default-cli) > generate-sources @ standalone-pom >>>
[INFO]
[INFO] <<< maven-archetype-plugin:3.2.0:generate (default-cli) < generate-sources @ standalone-pom <<<
[INFO]
[INFO] --- maven-archetype-plugin:3.2.0:generate (default-cli) @ standalone-pom ---
[INFO] Generating project in Batch mode
[WARNING] Specified archetype not found.
Downloading: file:///usr/lib/node_modules/percli/maven/repo/com/peregrine-cms/peregrine-project-archetype/1.0/peregrine-project-archetype-1.0.pom
[WARNING] The POM for com.peregrine-cms:peregrine-project-archetype:jar:1.0 is missing, no dependency information available
Downloading: file:///usr/lib/node_modules/percli/maven/repo/com/peregrine-cms/peregrine-project-archetype/1.0/peregrine-project-archetype-1.0.jar
Downloading: https://repo.maven.apache.org/maven2/com/peregrine-cms/peregrine-project-archetype/1.0/peregrine-project-archetype-1.0.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.802 s
[INFO] Finished at: 2020-11-05T21:58:54+01:00
[INFO] Final Memory: 21M/467M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.2.0:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.peregrine-cms:peregrine-project-archetype:1.0) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
(node:16890) UnhandledPromiseRejectionWarning: #
(node:16890) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:16890) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Using
Ubuntu 16.04
NPM 6.14.6
Maven 3.3.9
Java 1.8

Minimum Updates for percli to run peregrine on Sling 12 based instance

Corresponding to a Sling 12 based launcher, percli needs a few changes.

--sling or -s is the sling version. There needs to be an option for 12
https://github.com/headwirecom/percli/blob/master/bin/percli-server-install#L42
Sling 12 needs a launcher (org.apache.sling.feature.launcher.jar) and feature aggregate (feature-oak_tar.json). I presume those need to be hosted on headwire's vagrant. and referenced in
https://github.com/cmrockwell/peregrine-cms/blob/upgrade/sling12-PM-Java11/docker/scripts/start.sh
Run modes and TCP port previously set in sling/sling.properties need to be set using launcher framework properties -D properties. For example:
java -jar org.apache.sling.feature.launcher.jar -f feature-oak_tar_fds.json -D sling.runmodes=author,notshared,oak_tar,fds -p sling

percli for a publish instance

The following does not seem to work for me
percli server install --publish
percli server install --publish --port 8180

In both cases it fails to upload the peregrine-cms packages, and tries to use 8080

Add ability to group dialog

Task:
Have a command to group portions of the dialog of a component.

Goal:
This is to clean up the dialog and make it more user friendly.

Ex:

Example can be found using the example site in peregrine and adding an image to the page and checking its properties.

Percli hatch creating XML with SAX parsing errors

It seems that the SAX parser doesn't like attributes that start with an opening curly brace '{'. If a JCR node has a JSON value, then the resulting attribute in the node content XML will cause a SAX exception when the bundle is imported. This can be fixed by adding a backslash before the curly brace for those attributes.