responses VS frp

I use responses for this (for HTTP/HTTPS requests), to great affect. It's API is very nice. We have an API layer at work that's basically just a proxy to micro services, and responses is what we use to test it.

responses

Please format your code appropriately. But if you are using python requests you can use responses for mocking requests: https://github.com/getsentry/responses

You can use this https://github.com/getsentry/responses

The repsonses library is designed for mocking requests during tests https://github.com/getsentry/responses

I like using responses for mocking API calls in unit tests. It's easy to use and has less boilerplate than doing the mocks yourself. The bulk of your unit tests should be around any data transformation you do, and unit testing them should be fairly straightforward. I'd recommend writing integration tests as well, especially as IME the most common reason why data pipelines with API sources break is due to breaking API changes out of your control. I'd make them as high level as possible and make real API calls, preferably using credentials for a designated testing account. Assert the response from the API call conforms to the contract you expect. Additionally to integration test your code, you can test the main entrypoint to your script and make sure it spits out a file with the shape and contents you expect.

HTTP client library flexibility. Yes, requests pairs well with responses or requests-mock, and HTTPX has RESPX or pytest_httpx. Those testing helpers are an excellent match for the corresponding library, and should certainly be recommended. However, I don't always want to face the risk of rewriting all my tests if I replace the client library some day. And sometimes I am using an altogether different tool (even though both requests and HTTPX are quite awesome) such as urlopen, urllib3, httplib2, tornado, or aiohttp.

If you want to self-host, there are many options. For something production ready frp is probably what you want. If you're a developer, I'd recommend starting with my own SirTunnel project and modifying it for your needs. For non-developers and those wanting more of a GUI experience, I created boringproxy. It's my take on a comprehensive tunnel proxy solution. It's in beta but currently solves almost everything I want. Once the server is running this is a very easy tool to use and has some nice features.

Seems to be the exact opposite of https://github.com/fatedier/frp which is a reverse tunnel over a variety of protocols (including HTTP).

I've been self-hosting https://github.com/fatedier/frp on my little box, and it feels insane to think of the times where I didn't have it set up. There are many choices in the space as others pointed out, but frp's capabilities and lightweight packaging blows all other setups out of the water. I placed mine behind nginx with Let's Encrypt for SSL support. Hella fresh!

My setup to do the same:

- small Hetzner instance

- my domain's dns pointing to that instance

- frps[1] running on that instance

- frpc running on my local machine and connected to the cloud frps

[1] https://github.com/fatedier/frp

An easy service to use is FRP, recently found it and it basically handles making the connection out of the network and is really easy to setup. https://github.com/fatedier/frp I personally having it running on a VPS and the client then running on my local network pointing at a reverse proxy which then handles sending it to the diffrent clients.

No, FRP - https://github.com/fatedier/frp

Another way around is to use reverse proxy like frp but since you need SSH anyway, all you need is already comes with SSH (reverse SSH)

Take a look also onto popular, similar to yours project: frp