DeepfakeHTTP
openapi-generator
DeepfakeHTTP | openapi-generator | |
---|---|---|
34 | 234 | |
503 | 19,899 | |
- | 1.9% | |
1.8 | 9.9 | |
over 1 year ago | 4 days ago | |
Java | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DeepfakeHTTP
-
DeepfakeHTTP v6.3.1
A new version of DeepfakeHTTP is out! I decided to add a new --dir option, allowing to host static content as static servers do. However, unlike regular static servers, DeepfakeHTTP can also host executable stuff, such as shell scripts or JavaScript. In order to have JavaScript executed on the server side you need to specify 'use server' at the beginning of the code (similar to the well-known 'use strict').
-
DeepfakeHTTP v6.1.1
The new release of DeepfakeHTTP brings new features.
-
DeepfakeHTTP v5.1.1 released!
https://github.com/xnbox/DeepfakeHTTP From the README.md.
-
I would like to get feedback on my open source project
DeepfakeHTTP is a web server that uses HTTP dumps as a source for responses.
- The web server that uses HTTP dumps as a source for responses
-
Rapid REST API prototyping using a dump server
Download the latest release of df.jar
-
What is a DUMP SERVER and what are its advantages over a static server
View on GitHub
-
Mom. Dad. Grandma. Everyone is happy!
When I told them that I created DeepfakeHTTP, no one really reacted. Dad said: – Son, I understand that the idea of simulating an HTTP server is interesting, but what am I going to do with this simulator you created?... Will he fix the engine from the hay mower for me, or what?! Daddy took his oil-soaked, frayed-in-time notebook, and went to assemble the engine parts. – No, Dad, my server sure can't fix your motor, I replied sadly and went to bed. At night I dreamed that I was wandering through a junkyard of old, abandoned engines and shouting: – Maybe someone needs an open source mock server, with HTTP dumps under the hood? But there was such a silence around, you could hear the tedious flapping of the wings of a butterfly slowly flying past my eyes... But the engines must have heard me and some kind of switch turned, as I woke up in the morning in a very different mood! I remembered that Dad was always looking for some kind of tool for his technical notes. He had tried Word and LibreOffice Calc and Excel... But something would drift to the side, or go into a different column, or jump to a new page when there was still enough space on this one... Anyway, the oily notebook continued to take its honorable place in Dad's workshop. No, don't get me wrong, I suggested that he do all his business in a text file, but that didn't work out either. "There's no clarity", - Dad said, I want me to put in bolts for KR-18, and all my bolts for KR-18 show up right away. And Uncle Jerry's bolts, too. And that I can see what bolts Uncle Jerry has, and he can see what I have. And that Uncle Jerry and I could both see and update, him at his house and me at mine. It became clear to me that he wanted something like ERP. I thought, what if you don't write any ERP, but simulate it. Simulate it with the hands of Dad and Uncle Jerry. So, let's get down to business! We take a text file, we call it john.txt, and we write:
- A web server that uses HTTP dumps as a source for responses
openapi-generator
-
The Stainless SDK Generator
Disclaimer: We're an early adopter of Stainless at Mux.
I've spent more of my time than I'd like to admit managing both OpenAPi spec files [1] and fighting with openapi-generator [2] than any sane person should have to. While it's great having the freedom to change the templates an thus generated SDKs you get with using that sort of approach, it's also super time consuming, and when you have a lot of SDKs (we have 6 generated SDKs), in my experience it needs someone devoted to managing the process, staying up with template changes etc.
Excited to see more SDK languages come to Stainless!
[1] https://www.mux.com/blog/an-adventure-in-openapi-v3-api-code...
[2] https://github.com/OpenAPITools/openapi-generator
-
FastAPI Got Me an OpenAPI Spec Really... Fast
As a result, the following specification can be used to generate clients in a number of different languages via OpenAPI Generator.
-
Show HN: Manage on-prem servers from my smartphone
Of course you can compile the server from source if you have Go and the OpenAPI generator JAR (https://github.com/OpenAPITools/openapi-generator?tab=readme...)
Follow these steps : https://github.com/c100k/rebootx-on-prem/blob/master/.github...
And then :
(cd ./impl/http-server-go && GOARCH=amd64 GOOS=openbsd go build -o /app/rebootx-on-prem-http-server-go-openbsd-amd64 -v)
By adapting the arch if needed. Not tested, but it should work.
- OpenAPI Generator v7.3.0 has new generators for Rust, Kotlin, Scala and Java
-
Stop creating HTTP clients manually - Part I
TL;DR: Start generating your HTTP clients and all the DTOs of the requests and responses automatically from your API, using openapi-generator instead of writing your own.
-
How to Automatically Consume RESTful APIs in Your Frontend
As an alternative, you can also use the official OpenAPI Generator, which is a more generic tool supporting a wide range of languages and frameworks.
-
Building a world-class suite of SDKs is easy with Speakeasy
I trialed generating SDKs using the OpenAPI Generator package, which was largely unsatisfactory.
-
Best way to implement base class for API calls?
If Swagger/OpenAPI is available, save yourself a lot of trouble and generate the client using OpenAPI Generator. If not, use a library like RestEase to make it significantly easier to create the client.
-
Sharing EF data access project DLL vs NuGet vs ?
For a run of the mill REST API you should generate OpenAPI (Swagger) info for the API using a library like NSwag or Swashbuckle. You'd want to do this no matter what because it's documentation for the API, but the bonus is that you can use it with tools like OpenAPI Generator to create API client code and models in a variety of languages. You certainly can create an API client library manually, it would entail having a nuget package with a class library that contains the models and client code for calling the endpoints (which I'd create using a lib such as RestEase unless you just enjoy writing boilerplate code by hand). However 95% of the time it simply isn't worth creating your own lib when OpenAPI is available because once you've done it a time or two it takes less than 5 min to run the generator and create (or update) a lib.
-
Created an API using Gin, want to create sdk for him
Then you can use oapi-codegen or openapi-generator to generate the Go (or other language) SDK for it.
What are some alternatives?
castlemock - Castle Mock is a web application that provides the functionality to mock out RESTful APIs and SOAP web services.
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
vcr - Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests.
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
request - 🤖 Minimal http client for api development and testing
SvelteKit - web development, streamlined
request-baskets - HTTP requests collector to test webhooks, notifications, REST clients and more ...
smithy - Smithy is a protocol-agnostic interface definition language and set of tools for generating clients, servers, and documentation for any programming language.
tommy - Tommy is Apache Tomcat, bundled as a single executable jar.
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
Apache Tomcat - Apache Tomcat
autorest - OpenAPI (f.k.a Swagger) Specification code generator. Supports C#, PowerShell, Go, Java, Node.js, TypeScript, Python