Hi Willes,

I’ve never seen that particular error from npm!  I changed the relevant url to 
be https://, could you try again?

I also added some todo.adoc files to these two new projects…. take a look, are 
they more or less what you had in mind?

Thanks!
David Jencks

> On Jul 16, 2020, at 1:00 PM, Willes Reis <willesr...@gmail.com> wrote:
> 
> Hi David, thanks for your effort.
> 
> 
>>> On Jul 15, 2020, at 6:03 PM, David Jencks <david.a.jen...@gmail.com>
>> wrote:
>>> 
>>> I’ve:
>>> 
>>> - started an Antora UI bundle project for TomEE:  tomee-antora-ui <
>> https://github.com/djencks/tomee-antora-ui>
>>> It’s already built, but if you want to build it yourself, clone it, run
>> npm i, and gulp.
> 
> I did fork/clone this project, but I haven't built it yet..
> 
> 
>>> In order to track what is changed from the default UI, I used my
>> slightly experimental UI builder.  If we want  to proceed on this path I
>> can release it to npm; right now it’s in my space on AWS.
>> 
>> 
>>> I set header/footer colors/images to match the existing site and removed
>> the cruft from the header.  I didn’t try to match header/footer content
>> with the existing site since I think it needs to be rethought for Antora.
>> 
> I could help you with this details in design/UI asap.
> 
>> - started an Antora playbook project for TomEE: tomee-antora <
>> https://github.com/djencks/tomee-antora>
>>> To build this, clone it, and run npm run clean-build.  The site will be
>> at build/site.
>>> I have not yet provided a maven project to run this.
>> 
> 
> I did fork/clone this project and run build, but there was some error at
> authentication in your GitHub repo tomee-antora-ui, as follows:
> Perhaps you can understand and know what to do.
> 
> 
>> willesreis@host tomme-antora % npm run clean-build
>> 
> 
>>> @ clean-build /Users/willesreis/tomee-antora
>> 
>>> npm run clean-install;npm run build
>> 
>> 
>> 
>>> @ clean-install /Users/willesreis/tomee-antora
>> 
>>> rm -rf node_modules/ .cache/ package-lock.json;npm i --cache=.cache/npm
>> 
>> 
>> The authenticity of host 'github.com (18.228.52.138)' can't be
>> established.tf8@0.0.1 fetched in 1083ms
>> 
>> RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
>> 
>> ⸨    ░░░░░░░░░░░░░░⸩ ⠼ fetchMetadata: sill pacote version manifest for
>> to-utf8@0.0.1 fetched in 1083ms
>> 
>> npm ERR! Error while executing:
>> 
>> npm ERR! /usr/bin/git ls-remote -h -t ssh://
>> g...@github.com/djencks/tomee-antora-ui.git
>> 
>> npm ERR!
>> 
>> npm ERR! Host key verification failed.
>> 
>> npm ERR! fatal: Could not read from remote repository.
>> 
>> npm ERR!
>> 
>> npm ERR! Please make sure you have the correct access rights
>> 
>> npm ERR! and the repository exists.
>> 
>> npm ERR!
>> 
>> npm ERR! exited with error code: 128
>> 
> 
> I suggest that we put a ".adoc" file kind "to do" or "progress" on each
> repo, on which we can write all of things to do, i.e. our path, and we go
> "checking" each item as we progress. What do you think?
> 
> Willes Reis

Reply via email to