Issue: Bug report :cant install

[reznik1988]

Client Environment

Operating System:  Description:    Ubuntu 20.04.3 LTS
Web Browser: chrome/edge
Device:vds

Describe the bug
cant install it, did that before but now it give me an erorr

bootstrapValidator.js:8255 Uncaught ReferenceError: require is not defined
at bootstrapValidator.js:8255
(anonymous) @ bootstrapValidator.js:8255

2021-12-12 12:45:37 v-list-web-domain 'spgs' 'hwi.palm-tree.finance' 'plain' [Error 3]
2021-12-12 12:45:37 v-list-web-domain 'spgs' 'hwi.palm-tree.finance' 'plain' [Error 3]
2021-12-12 12:45:37 v-add-web-domain 'spgs' 'hwi.palm-tree.finance' '78..' 'yes' 'none' 'jpeg,jpg,png,gif,bmp,ico,svg,tif,tiff,css,js,htm,html,ttf,otf,webp,woff,txt,csv,rtf,doc,docx,xls,xlsx,ppt,pptx,odf,odp,ods,odt,pdf,psd,ai,eot,eps,ps,zip,tar,tgz,gz,rar,bz2,7z,aac,m4a,mp3,mp4,ogg,wav,wma,3gp,avi,flv,m4v,mkv,mov,mpeg,mpg,wmv,exe,iso,dmg,swf' [Error 2]
2021-12-12 13:22:34 v-list-dns-records 'spacngs' 'hwi.palm**' [Error 3]

Additional context
Add any other context about the problem here.

[boka003]

Same here, it looks like this project is dead.
I was trying to contact the author by email, but no response...

[cdgco]

Sorry, I don't have the time to actively maintain this project anymore but try to support it. Is this on step3.php of the web configuration process? What version of php are you using?

I'm seeing possible compatibility errors with PHP 8. Either use PHP 7.4 or earlier to install or use the manual configuration method for now until this is resolved.

[boka003]

You are right.
It will work with 7.4
But it is extreme slow.

If is possible to convert interface to HestiaCP theme, then it will be much more easy to maintain?

[cdgco]

Maybe the user interface could be converted to a theme, but this project includes a lot of plugins and integrations that would be lost. I've discussed before rewriting the project to run on HestiaCP / VestaCP's backend server using shell commands instead of API calls, but that would still be a big undertaking and one of the features of this app is that it is standalone and doesn't need to be hosted on or modify HestiaCP.

I'd like to improve the performance of the project and refactor some code, but again, I just don't have the time to work on this right now.

One setting that may help improve performance is to cache the database by changing the connection method in includes.php: https://hwi.cdgtech.one/#/connection-method?id=connection-method

[cdgco]

Looking at performance data on my test servers, API calls are the biggest bottleneck, averaging 700 - 1900ms per request. Not sure there's much I can do if the API speed is the problem.

[BartManX]

hey i just installed .. going from PHP 8 to 7.4 fixed the install problem. haven't had any problems with the speed that was mentioned.
none at all yet

[cdgco]

@BartManX I'm glad to hear that. I think resources on the HestiaCP server are a big factor here.

I'm still trying to squash some bugs and haven't fixed the web installer yet, but the PHP-8 Branch is published now and seems to be working pretty well with PHP 8.1. Hopefully I'll have a release published soon.

[BelleNottelling]

@cdgco Rector will almost entirely automate the upgrade process to PHP 8+ for you
https://github.com/rectorphp/rector

Regardless, I'm quite interested in this project, if I contributed my time to fix up the code & assist prepping the 8.0+ release would you be interested in PR's?

[BelleNottelling]

Update: I just gave the code a quick glance and yikes, not trying to be rude, but there's a fairly significant code quality issues here.
It now makes a lot of sense as to why you're still working on making it work with PHP 8.0+.

The codebase would largely benefit from a rewrite, to be honest

[cdgco]

Update: I just gave the code a quick glance and yikes, not trying to be rude, but there's a fairly significant code quality issues here.
It now makes a lot of sense as to why you're still working on making it work with PHP 8.0+.

The codebase would largely benefit from a rewrite, to be honest

I'm not working on this project at all, it's almost 6 years old now (started it early in highschool). Definitely not clean, but I have no plans to update or maintain anything at this point. I've toyed with the idea of a rewrite in JS back when the original project (VWI) had some popularity, but nowadays VWI + HWI only get a few installs a month and it'd be a massive undertaking to clean this project up for the few people who use HestiaCP.

Even in it's current state, HWI is just a rough clone of VWI that's still missing some HestiaCP specific features, and due to the performance of the Vesta / Hestia APIs, it's never been an amazing experience.

There's just not enough interest in the project to justify putting time into it now that I'm in university and barely use VestaCP or HestiaCP anymore.

[BelleNottelling]

Update: I just gave the code a quick glance and yikes, not trying to be rude, but there's a fairly significant code quality issues here.
It now makes a lot of sense as to why you're still working on making it work with PHP 8.0+.
The codebase would largely benefit from a rewrite, to be honest

I'm not working on this project at all, it's almost 6 years old now (started it early in highschool). Definitely not clean, but I have no plans to update or maintain anything at this point. I've toyed with the idea of a rewrite in JS back when the original project (VWI) had some popularity, but nowadays VWI + HWI only get a few installs a month and it'd be a massive undertaking to clean this project up for the few people who use HestiaCP.

Even in it's current state, HWI is just a rough clone of VWI that's still missing some HestiaCP specific features, and due to the performance of the Vesta / Hestia APIs, it's never been an amazing experience.

There's just not enough interest in the project to justify putting time into it now that I'm in university and barely use VestaCP or HestiaCP anymore.

Hey, thanks for the quick response!
Yeah, I was actually thinking that this looked like code I'd write when I was in HS, so that about makes sense lol.
I don't think I'd want to maintain the current code base either, now that I've looked at it.

Not sure about the front end of it, though. Visually the demo you have hosted looks nice.
I can't do front end development to save my life, but I'm quite competent with back end.

If I ever decided I wanted to build a similar project, would you mind if I used the front end from this project as a base?