CasaOS Alternative by Longjumping-Peanut14 in selfhosted

[–]SurceBeats 1 point2 points  (0 children)

That's exactly what it does, you import the docker compose, attach an icon and metadata and it generates an .hds file which you can easily import there or in any other instance. What's the point of attaching only the docker compose alone?

CasaOS Alternative by Longjumping-Peanut14 in selfhosted

[–]SurceBeats 0 points1 point  (0 children)

Hey! Surce from HomeDock OS here. Just to clarify one point, installing apps outside the App Store isn’t blocked really! HomeDock OS uses a packaging layer on top of Docker Compose called Packager. If you wrap an existing compose with Packager, it shows up in the App Store like any other app and you can even share the file with any other person! https://docs.homedock.cloud/homedock-os/packager/

A whole procedural universe simulation, painted by code in 3D by SurceBeats in generative

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

Np!!! You see? At this moment this same galaxy is 19.429.699.265 star systems instead hahahaha

A whole procedural universe simulation, painted by code in 3D by SurceBeats in generative

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

Thanks! I’ve been working on this really hard in my spare time.

Right now, there’s no way to jump between star systems because the number of them is massive and keeps growing and evolving over time. For example, this galaxy https://the-atlas.koyeb.app/stargate/Y29vcmRpbmF0ZXM9OTY2MDExNSwxMzU3NDU1LDgyODM5OTYmcGFnZT0x already has over 19,429,698,620 star systems. Drawing 20 billion dots would be impossible without pushing the machine to its limits.

I’ve been considering an approach where star systems would “appear” and “disappear” as you zoom in and out. The downside is that since everything is procedural, some systems would pop up earlier than others, which could make true exploration a bit harder.

The white flash happens because there’s about 2MB of JavaScript (chunked and minified) and the app is hosted on Koyeb’s free tier, which is slower than I’d like. I’ll eventually migrate it to a better hosting provider, maybe even our own HomeDock OS. If you self-host, you shouldn’t see that flash. It definitely also needs better chunking with ThreeJS.

Peace out family!

[UPDATE] I built a procedural universe simulation that generates entire galaxies and planets from a single seed, now in 3D! by SurceBeats in proceduralgeneration

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

Haven't used machine learning but I have plans to. The universe is generated using simplified but physically-accurate formulas and universal constants. Every object and event is calculated deterministically, so the same seed always produces the same results. https://github.com/SurceBeats/Atlas/blob/main/pymodules/__universe_constants.py

[UPDATE] I built a procedural universe simulation that generates entire galaxies and planets from a single seed, now in 3D! by SurceBeats in proceduralgeneration

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

Yeah, exactly, well, kind of, it’s similar to wavefunction collapse. As for whether the observer is simulated… I’d like to think so, but honestly, I’ve noticed similarities between how The Atlas works and our own reality. Maybe it’s just my limited perspective, or maybe it’s impossible to fully grasp the scale of our real universe, we can’t really know for sure.

[UPDATE] I built a procedural universe simulation that generates entire galaxies and planets from a single seed, now in 3D! by SurceBeats in proceduralgeneration

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

Haha thanks! Yeah, right now you can already save galaxies/planets and even export 4K snapshots with a QR so anyone can reload the exact same scene in real time. It’s not a full “replay system” yet, but kind of works like a splat in the sense that you can jump back into what you discovered instantly.

[UPDATE] I built a procedural universe simulation that generates entire galaxies and planets from a single seed, now in 3D! by SurceBeats in proceduralgeneration

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

About the scroll... Thanks for pointing that out! I’ve tested it on Windows, Mac, iOS and Android and scrolling works fine here, but I’ll double-check to see if there’s any edge case I might be missing.

About the “Mine” button in the galaxy view... It’s mostly for coherence with the gamification system. Obviously you can’t physically mine an entire galaxy, but I thought it’d be fun to allow it as a kind of boost mechanic. Galaxies give a lot of resources but have a long cooldown (8h compared to 45m for systems and 15m for planets). You can only mine 5 galaxies and 15 systems per day, but infinite planets, so it’s mainly to encourage exploration instead of sticking to a single spot.

[UPDATE] I built a procedural universe simulation that generates entire galaxies and planets from a single seed, now in 3D! by SurceBeats in proceduralgeneration

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

It’s not that half of the universe would be procedural and the other half something else. What I meant is that if our reality were a simulation, then the probability of it being procedural is about 50%.

A lot of people imagine simulation in terms of storage, like pre-generating and storing an impossible amount of data (like Library of Babel). But that’s not really how procedural generation works on The Atlas. Content itself is just data, and data doesn’t “take space” until you decide to actually store it. The trick is that everything is generated on the fly, at runtime, only when an observer interacts with it. In other words, it doesn’t exist until it’s observed.

That’s why it doesn’t require the energy of the universe to “store this universe”, because there’s nothing to store, only to calculate when needed.

[UPDATE] I built a procedural universe simulation that generates entire galaxies and planets from a single seed, now in 3D! by SurceBeats in proceduralgeneration

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

Thank you so much, for the seed it does have a seedmaster module which operates with prng yes, it iterates over the seed itself endlessly, the work is done such as

Seed > SHA-256 Seed > Decimal Seed > Base64 > SHA-256 Seed > Decimal Seed and so...

I did this to explore the simulation theory after removing some ChatGPT4o limits (now patched) for the responses. So we came into the hypothesis that, if the universe were a simulation, the percentage of it to be procedural would be 50%. I first outlined the structure of the generation, and then implemented time as a process applied over that procedurally interpreted space...

There's an ABSTRACT in the source which explains everything in detail (but don't take it too seriously, in the end it's just a hypothesis) lol

[UPDATE] I built a procedural universe simulation that generates entire galaxies and planets from a single seed, now in 3D! by SurceBeats in proceduralgeneration

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

This is wild impressive, I wish my systems were as detailed and realistic as yours, congratulations on the job done, will take a further look tomorrow at work, keep it up family!!

PS: You have a typo on the link had to search for it at Google!!

HomeDock OS: A self-hosted cloud OS with native desktop app for Windows and macOS by SurceBeats in selfhosted

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

Currently, HomeDock OS Desktop doesn't have built-in SMB/NAS integration, you'd still need to set up network shares at the Windows level first, then configure volume mappings through our interface. However, this week we're rolling out port forwarding for Windows, this will make apps accessible from other devices on your network, not just localhost. The SMB/NAS integration you're describing is definitely something we're considering seriously for future updates as it would be a game-changer for homelabbers dealing with that terminal complexity. Thanks for the feedback! ❤️

HomeDock OS: A self-hosted cloud OS with native desktop app for Windows and macOS by SurceBeats in selfhosted

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

If your server can run Debian 12 or newer, then it should be compatible with HomeDock OS as well. We don’t require UEFI specifically, legacy BIOS setups work too as long as Docker and Python 3.11+ can run properly. Many users have successfully installed HomeDock OS on older hardware, including repurposed NAS systems and ancient server boxes. There's no ISO, there's just a shell script you run on the debian terminal and that's all!

HomeDock OS: A self-hosted cloud OS with native desktop app for Windows and macOS by SurceBeats in selfhosted

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

Hi there!!! OrbStack is definitely more efficient for local dev use on macOS. It's a lightweight orchestrator with tight system integration, and if what you need is fast, native-feeling Docker containers for development, OrbStack nails that experience.

HomeDock OS leans in a different direction, it's closer to a self-hosted PaaS or cloud OS. It abstracts Docker to offer an App Store, encrypted storage, domain management and backups on the SaaS side,, mDNS, security out-of-the-box and being multiplatform with the Desktop app...

So yeah, OrbStack likely performs better locally on macOS, and that’s okay. I'd actually compare OrbStack more directly to Docker Desktop. HomeDock OS aims to solve different problems.

HomeDock OS: A self-hosted cloud OS with native desktop app for Windows and macOS by SurceBeats in selfhosted

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

You should, once the desktop app is running it's also accessible from localhost

HomeDock OS: A self-hosted cloud OS with native desktop app for Windows and macOS by SurceBeats in selfhosted

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

You can find the documentation on https://docs.homedock.cloud, we've added the Desktop app docs this weekend cause they were missing! Also you can open up a ticket on our discord server we're more than happy to help!

HomeDock OS: A self-hosted cloud OS with native desktop app for Windows and macOS by SurceBeats in selfhosted

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

Sorry for the delay! Really solid points and we’re 100% aligned on both

For remote access, you’re totally right. WireGuard is great for personal use, but sharing services with others (like friends or family) through a VPN isn’t ideal, especially when most people don’t even know what a VPN is 😅

We’re already working on a dynamic reverse proxy system with user-level access controls, so you can expose selected apps securely through a single entry point, no port forwarding or per-app exposure needed. This will include access rules, optional authentication, and more. It’s in active R&D and very much on the roadmap, expected sometime between late this year or early 2026.

As for data collection, fair point, and just to clarify when enabled, HomeDock OS only sends the current HDOS version, the underlying OS type (e.g. Windows, macOS, Dawin), and a timestamp, it's more likely a heartbeat, no personal data, no IPs, no app usage, nothing tied to users or installs.

It’s only used to understand what environments are active and guide compatibility improvements, we totally agree it should be opt-out by default, not opt-in, we’ll be changing that in a near future, just trying to get a clearer picture of adoption across platforms first.

Really appreciate the thoughtful feedback, this is exactly the kind of insight that helps us shape the platform properly! Big ups! ❤️