-
Notifications
You must be signed in to change notification settings - Fork 1.7k
support
KernelDeimos edited this page Oct 23, 2024
·
1 revision
This document describes issues requiring repository changes; which issues will be fixed by Puter's core team, and which ones will be fixed if the community makes a contribution.
This document is not "law". It is provided only as a helpful guide on what to expect.
| Name | Description |
|---|---|
| Core | Core developers will fix this |
| Community | We will accept contributions to fix this |
| Mixed | Core developers will fix this if it's currently a priority |
| Issue | Priority |
|---|---|
| Security vulnerability | Core |
| Breaking change to SDK or API | Core |
| Bug in service in CoreModule | Core |
| Bug in a built-in app | Core |
Login/init failure in Docker on release branch |
Core |
| Login/init failure in Linux or OSX | Core |
Login/init failure in Docker on main branch |
Mixed |
| Login/init failure with specific configuration | Mixed |
| Login/init failure in Windows | Community |
If you experience issues on a self-hosted deployment we're here to help. Some issues are related to configuration or environment, so we may only be able to help in a limited capacity. Issues related to data loss, data corruption, or security will have higher priority over other issues with particular deployments.
You are reading documentation for the open-source repository of Puter.
Getting started on localhost is as simple as git clone npm install npm start.