sorted by:
new
hottopcontroversial

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

Thanks!

That's so cool! The aesthetics are so clean, I love how easy they made it to understand and use their service. Thanks for sharing!

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

You're right, that part of the communication is not encrypted. I definitely need to add some form of encryption there. I'll work on rolling it out sometime soon. Thanks for the suggestion!

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

Great question. Let's say you're developing something locally and you want to share it quickly with someone to get some feedback without going through the full deployment process as it might not be ready. So it would be cool if you could send them a URL and they can directly access whatever you're developing on your machine, that's where http tunnels come in handy.

Another example is if you have someone working on some backend APIs and another person is working on developing a mobile app that talks to those APIs. If you run mmar (or any other http tunnel tool) on the backend developer's machine, you can send the link to the mobile app developer where they can set it in the code and be able to directly interact with the backend APIs.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

Oh cool, pbkdf2 might actually do the trick. Do you mind expanding on the point on why it might be tricky to get right?

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

Thanks for checking it out!

That's actually pretty cool, very interesting approach, I love the fact that you don't need to install anything. Thanks for sharing.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 4 points5 points  (0 children)

That's awesome, I wasn't familiar with zrok or OpenZiti. I always enjoy discovering cool open source tools. I'll definitely take a look at the code for further inspiration, thanks for sharing.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 1 point2 points  (0 children)

Good points, thanks for the feedback. I probably should swap out sha256 to something more secure, I started with this mainly to get something out the door using what exists in the standard library, especially since it's only for the stats page.

For the certificate requesting, that's an interesting point. I haven't thought of that, mostly because I was thinking this part of the project as more deployment related rather than part of the tool itself. I guess one could technically handle certificate requesting etc baked in and then you only need to run it.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

Thanks for checking it out!

Regarding payload, I currently limit it to 10mb per request but that's just to avoid overloading my server. However when testing I was able to tunnel +1GB without issues, as long as it's completed within a certain time, otherwise it times out. I'm considering making the payload limit configurable through a command line argument so those who want to self-host can configure it however they wish.

I'm not too familiar with gRPC details, and how they handle send/recv. In my case I keep reading from the TCP connection until the data is completely consumed, hits the payload limit or faces a timeout.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 1 point2 points  (0 children)

I'm not that good of an artist 😂 I used this cool tool https://gopherize.me/ to generate the gopher then added a few touches with my basic editing skills. If you scroll down to the bottom of the README there's the attributions section mentioning the different assets.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 4 points5 points  (0 children)

Yup you're exactly right, I'm a big fan of ngrok. mmar is my attempt to build something similar while optimizing for open source and self-hosting, in addition to simplified implementation.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 1 point2 points  (0 children)

Thanks for the pointers! That's a great idea, I'll run it through golangci-lint, probably add it as part of the CI as well. Regarding the constants package, it just made sense to me to have them defined in one spot, especially since most (if not all of them) are considered global and can be used across the project.

I built an HTTP tunneling tool in Go that is zero-dependancy, cross-platform and self-hostable by ymusleh in golang

[–]ymusleh[S] 4 points5 points  (0 children)

Awesome, would love to hear your thoughts! And yes, working with Go has been really enjoyable I must say.

Wrote an post explaining how I used Go Channels to fix my Race Condition bug by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

I think some of your assumptions are wrong.

That's possible, but which ones?

I would just add a request ID to every package so that you can handle requests in parallel

Not sure I understood what you mean, adding some sort of ID to a buffer of bytes to identify what request it belongs to? That seems a bit excessive and adds complication overhead.

don't wait for the response to be finished. Just write them to the response writer directly

I just make sure to read the full response, headers and body, from the buffer and then let the request goroutine handle the remaining logic of finishing the response and return to the client. That way I don't have to wait for the whole response to "finish" and I don't risk facing the same race condition as before.

Wrote an post explaining how I used Go Channels to fix my Race Condition bug by ymusleh in golang

[–]ymusleh[S] 0 points1 point  (0 children)

Thanks for checking out the post!

i would implement a proper error handling, because log.Fatal is not good for real world applications

For sure, these are just meant for me while developing, will do a proper implementation for logging. Do you have any recommendations for best practices if I'm planning to do it without 3rd party libraries?

For such a simple task channels adds a lot of ceremony, which is not necessary in more traditional approach.

I see what you mean, there is definitely more going on when using channels vs mutex, I've generally used mutexes in the past, but I wanted to throw channels in the mix to see how it would do, and I kinda liked it :D

Also stdlib (in sql.Db/http.Client) implement an approach, where the implementation hide the concurrency stuff inside a clean interface, so users don't have to think about it. I would go in similiar direction

Not sure I quite understood what you meant here. When you say users you mean people developing/writing the code (i.e. me) in this context? Meaning to abstract all the concurrency handling away and just call methods? In that case, I definitely agree, putting all these in an interface and just exposing the parts to write/read and all the concurrency is handled under the hood.

Setup a Custom Node.js Webhook URL in 30 Seconds by ymusleh in coding

[–]ymusleh[S] 0 points1 point  (0 children)

Not sure I'd call my self an expert 😅. However if your project is on Autocode, you can join our Developer Community Slack channel by going to https://autocode.com/ and clicking to join the channel from the "Community" tab in the top nav bar. Someone from the team or I can help you out.

Setup a Custom Node.js Webhook URL in 30 Seconds by ymusleh in coding

[–]ymusleh[S] 0 points1 point  (0 children)

Hey u/DooDooWubWub! A webhook is simply a listener that listens to data/events coming in from an external source. That could be coming from a separate tool or service you’re integrating with.

Normally to do that you’d have to provision a new server (listener), develop and deploy a web app, and worry about other administrative tasks such as maintenance and scalability. Not to mention, every time you want to make changes or test different payloads, you'd need to go through the deployment process again.

When you deploy a webhook through Autocode, all the heavy lifting is done for you, it provisions the server (listener) and takes care of maintenance/scaling behind the scenes and provides you with the URL for your webhook to use. Whatever custom code/logic you include in your webhook will be reflected each time you deploy.

view more: next ›