Daniel Salazar
fc725d0130
* Revert "fix: quick fix for config context issue" This reverts commit0c06040e6c. * Revert "sync: package-lock.json" This reverts commit1e1bd0f2ba. * Revert "devex: misc log cleanup" This reverts commita64a786528. * Revert "devex: minimal first page load logs" This reverts commit196e463c59. * Revert "devex: minimal initialization logs" This reverts commitea9c222c09. * Revert "fix: add missing await in kv example extension" This reverts commit9b34e67d0d. * Revert "devex: reduce logs at init" This reverts commitfa221149c2. * Revert "sync: package.json changes" This reverts commit4db73d75a5. * Revert "fix: remove unused AWS SDK v2 import" This reverts commit4d8692fd31. * Revert "devex: hide `npm install` output unless it fails" This reverts commitfe03a4b598. * Revert "devex: rollup via module instead of subprocess" This reverts commit360082d8bd. * Revert "devex: webpack via module instead of subprocess" This reverts commit1449d12b0e.
Puter Backend
Part of a High-Level Distributed Operating System
Whether or not you call Puter an operating system (we call it a "high-level distributed operating system"), operating systems for devices are a useful reference point to describe the architecture of Puter. If Puter's "hardware" is services, and Puter's "userspace" is the client side of the API, then Puter's "kernel" is the backend.
Puter's backend is composed of:
- The Kernel class, which is responsible for initialization
- A number of Modules which are registered in Kernel for a customized Puter instance.
- Many Services which are contained inside modules.
Documentation
Can I use Puter's Backend Alone?
Puter's backend is not dependent on Puter's frontned. In fact, you could prevent Puter's GUI from ever showing up by disabling PuterHomepageModule. Similarly, you can run Puter's backend with no modules loaded for a completely blank slate, or only include CoreModule and WebModule to quickly build your own backend that's compatible with any of Puter's services.
What can it do?
Puter's Kernel only initializes modules, nothing more. The modules bring a lot of capabilities to the table, however. Within this directory you'll find modules that:
- coerce all the well-known AI services to a common interface
- manage authentication with Wisp servers (this brings TCP to the browser!)
- manage apps on Puter
- allow a user to host websites from Puter
- provide persistent key-value storage to Puter's desktop and apps
- provide a fast filesystem implementation
- communicate with other instances of Puter's backend, secured with elliptic curve cryptography
- provide more services like converting files and compiling low-level code.
