index.html missing in RPM, deb, tarball packages #249
Description
I still see the error 'Failed to parse HTML template' which was fixed in a previous ticket (#204). The installation process I used was via the RPM.
During the Systemd startup, I see the error in the journal:
Jan 17 17:40:16 inbucket[15129]: 5:40PM ERR Failed to parse HTML template error="open /usr/local/share/inbucket/ui/index.html: no such file or directory" cwd=/ module=web path=/usr/local/share/inbucket/ui/index.html phase=startup
There is an npm-debug log in the ui directory stating the the npm build commands
[/usr/local/share/inbucket/ui]# cat npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/bin/npm', 'run', 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose stack Error: ENOENT: no such file or directory, open '/usr/local/share/inbucket/ui/package.json'
4 verbose stack at Error (native)
5 verbose cwd /usr/local/share/inbucket/ui
6 error Linux 4.14.256-197.484.amzn2.x86_64
7 error argv "/usr/bin/node" "/bin/npm" "run" "build"
8 error node v6.17.1
9 error npm v3.10.10
10 error path /usr/local/share/inbucket/ui/package.json
11 error code ENOENT
12 error errno -2
13 error syscall open
14 error enoent ENOENT: no such file or directory, open '/usr/local/share/inbucket/ui/package.json'
15 error enoent ENOENT: no such file or directory, open '/usr/local/share/inbucket/ui/package.json'
15 error enoent This is most likely not a problem with npm itself
15 error enoent and is related to npm not being able to find a file.
16 verbose exit [ -2, true ]