HIX - Template - Copy-Paste-Run-ReadyToGo

[ramirezosvaldo2]

Hello, good day.

First of all, for those who can't download or compile UT, here comes HIX, an all-in-one web server.

HIX is a ready-to-go web server.

HIX/UT can easily be used for APIs, static web pages, or even a full web development stack
(routes, certificates, sessions, etc., etc.)

Easier than with Node.js!!!

---

1. First Step: Download and install:

https://github.com/carles9000/hix

2. Second Step: Download-unzip-copy-paste into the folder where HIX was installed (default: C:\hix)

https://github.com/jobbisoft/unir-tesis ... master.zip

(This is a free template, like many others out there — note: all copyrights belong to their respective owners)

3. Run C:\hix\hix.exe start — and that’s it! You now have a fully functional web system.

4. Your browser will open automatically with the webpage!

---

Let me share a bit of what we’ve seen:

If you run HIX.EXE by itself, it enters configuration mode, allowing you to configure and launch the web server from there.

If you run HIX.EXE START, it starts the web server with the previously defined configuration.

What’s next? Whatever you like!

Regards,
Osvaldo Ramirez

[Carles]

Osvaldo,

I've just tested this example and it works perfectly. It's a very complete and powerful example, but what I think really matters is that HIX handles it correctly.




Thanks!

C.

[NWKL]

Carles, a newbie question, using this, does our .prg code get exposed? Is there any solution using .exe?

thanks

[Carles]

Hi,

Just like others, such as PHP. But let's be real, this has been said a million times: a server is just a computer in a data center, your office, your home, etc. The administrator of that machine has access to all the files.

Even if you have an app on any hosting service, for example, GoDaddy, any of their sysadmins can take a look.

The good news is that soon we'll be able to use hrbs to make HIX more "unique" than the others.

C.

[Otto]

Hello,
I experimentally extended my small Winsock microservice with an HRB runtime.

The idea: precompile PRGs to .hrb, load them once in the service (hb_hrbLoad()), cache them in memory, and invoke them per route (hb_hrbDo() or an entry like MAIN).

Externally, you only see descriptive URLs without an extension (e.g., /app/foo); internally, it’s simply mapped to ./apps/foo.hrb. The scripts get a mini API (GetQuery(), GetBody(), Print(), SetHeader()), run only under ./apps/ with timeouts, and return HTML or JSON directly. The result in deployment: no .prg sources, only HRBs.

If you still want to debug yourself, you can link the PRG instead of the HRB on your own server.

And most importantly, you need to be protected on the internet-facing side, and I think Cloudflare is your trump card.

Best regards,
Otto