I have tried using the webapp in the latest versio...
# general
c
I have tried using the webapp in the latest version
.\wiremock-standalone-3.3.1.jar
When navigating to
/__admin/webapp
I get page not found. Is there an alternative download that includes the webapp?
t
Hi Craig, WireMock standalone (and OSS generally) is headless - configured via programmatic, REST and file based APIs. There’s a small UI for recording under
/__admin/recorder
c
I appreciate what you are saying, but that interface was REALLY useful. I will learn to adapt.
t
There was never a UI there in the standard builds. Perhaps you were using a custom build previously?
If you like having a UI, have you tried WireMock Cloud?
a
/__admin/docs/
->
/__admin/swagger-ui/
? (Although this is just the admin API, not your own custom mappings)
https://github.com/holomekc/wiremock -> @Craig Is this the WireMock you were using before?
👍 1
c
I was using this UI. Which was included in
wiremock-jre8-standalone-2.35.0.1.jar
which I am pretty sure I downloaded from somewhere "official".
Copy code
<http://localhost:10000/__admin/webapp/mappings?active=0748a1ca-2abc-49f9-808c-7b39a87e76a3>
t
That’s not a version number we’d have used, so I’m guessing this is a fork. I don’t recognise the UI either.
a
2.35.0.1
is a version that the holomekc fork uses -> https://github.com/holomekc/wiremock/releases/tag/2.35.0.1-ui… and the UI looks the same, so I’d guess it’s that repo’s fork
🎯 1
@Tom / @Oleg Nenashev have y’all reached out to
holomekc
about bringing their project underneath the greater WM banner (….or does it end up competing with WireMock Cloud)?
o
The problem with https://github.com/holomekc/wiremock is that it is a (hard)-fork of WireMock based on the old version, and hence it could not be included without major rework
c
That's the one, thanks, did not realize it was a fork. I do like the GUI, pity it's an older version.
o
It was recently updated to WireMock 3, though it is not that old. At the same time the concern about being a hard fork remains, for the moment I would recommend reaching out to the maintainer, for example using a GitHub issue