Cannot build webapp without Artifactory access

[mattieb]

I was looking to build what's in "webapp" and ran into auth issues trying to run "npm i":

289 verbose stack HttpErrorAuthUnknown: Unable to authenticate, need: Basic realm="Artifactory Realm"
289 verbose stack     at /home/me/.nodenv/versions/20.18.3/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:80:17
289 verbose stack     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
290 verbose statusCode 401
291 verbose pkgid @devolutions/web-telnet-gui@https://devolutions.jfrog.io/devolutions/api/npm/npm/@devolutions/web-telnet-gui/-/@devolutions/web-telnet-gui-0.2.19.tgz

I don't know if y'all intend for webapp to be buildable outside your org or not, but I can't at the moment.

[CBenoit]

Hi,

Indeed, some of our web clients are not open source, and published on a private Artifactory.

However, I’m open to support building the "webapp" (Devolutions Gateway Standalone Web UI) without access to the private Artifactory. The idea would be to turn the closed source client packages into optional dependencies. Only our official builds would include these, but it would be possible for anyone to make an "open source build" with less features.

[mattieb]

Gotcha. For what it's worth, I don't have any concrete plans to do development on webapp at this time—I was exploring the codebase to see how far I could get pulling together a standalone gateway build, purely at a hobby level.

I'd been able to use this Linux Docker build to pull together a very simple setup with no dependencies and no OS requirements, and was wondering what it would take to build a newer image for myself.

I was eventually able to hack something together without building webapp (or anything), based on artifacts from d-g and cadeau, leveraging the Dockerfile (though the -ps zip seemed kind of broken, for what it's worth.)

I do like the idea of open builds. Looks like they might primarily not have VNC, SSH, or Telnet support? Not immediately clear what would be missing without "@devolutions/iron-remote-gui", though. (Sorry, I missed that @d/i-r-g is actually public!)

[flpydsk]

Hi,

Indeed, some of our web clients are not open source, and published on a private Artifactory.

However, I’m open to support building the "webapp" (Devolutions Gateway Standalone Web UI) without access to the private Artifactory. The idea would be to turn the closed source client packages into optional dependencies. Only our official builds would include these, but it would be possible for anyone to make an "open source build" with less features.

I for one would appreciate being able to build the RDP web client by its self excluding the proprietary ones

[rysinal]

Benoît Cortier (@CBenoit) I encountered a similar issue while building the web. May I ask if there has been any progress or update? tks

[CBenoit]

No progress right now, but I’ll try to see how easy this can be addressed today rysinal (@rysinal)

[CBenoit]

It seems the package hosting our icons is not public. I’m not sure yet how we can handle that, I’ll check with people internally.

[rysinal]

It seems the package hosting our icons is not public. I’m not sure yet how we can handle that, I’ll check with people internally.

Benoît Cortier (@CBenoit) Hi, Sorry to bother you, Is there a solution? Our internal server has some remote operation and maintenance scenarios. We need to add some custom frontends to link and match changes with existing systems. By modifying the build, we want to replace the currently used Docker version devolutions/devolutions-gateway:2025.3.4. Thank you very much for your help.