Go to file
2024-04-23 22:46:33 -07:00
.github Update main.yml 2024-04-22 19:23:03 -04:00
doc Document scope for fixes 2024-04-20 19:57:40 -04:00
incubator/x86emu Add checklists for x86 emulation project 2024-03-14 14:15:10 -04:00
packages Add ip rate limiting 2024-04-23 19:13:37 -04:00
src Perform more advanced input and string sanitization and validation for performance and security 2024-04-23 22:46:33 -07:00
tools Check that all uses of i18n() use keys that exist 2024-04-01 12:12:31 +01:00
volatile Release backend 2024-03-30 19:08:03 -04:00
.dockerignore Fix Dockerfile 2024-04-15 19:03:00 -04:00
.env.example Implement .env support for PORT property 2024-03-12 22:42:13 -07:00
.gitattributes Initial commit 2024-03-02 18:39:14 -08:00
.gitignore Fix casualty of phoenix due to Docker naming conventions 2024-04-15 12:12:28 -04:00
.is_puter_repository Release backend 2024-03-30 19:08:03 -04:00
build.js Migrate to JavaScript modules 2024-03-20 14:10:39 +00:00
CHANGELOG.md chore(main): release 2.2.0 2024-04-23 02:03:34 +00:00
CONTRIBUTING.md Add April-1st-appropriate commit message guidelines 2024-04-01 19:33:11 -04:00
dev-server.js Migrate to JavaScript modules 2024-03-20 14:10:39 +00:00
docker-compose.yml Update instructions & docker-compose to reflect production paths 2024-04-02 07:45:14 +02:00
Dockerfile Set NO_VAR_RUNTIME in Dockerfile 2024-04-15 20:47:27 -04:00
exports.js Release backend 2024-03-30 19:08:03 -04:00
l_checker_config.json Release backend 2024-03-30 19:08:03 -04:00
LICENSE.txt Initial commit 2024-03-02 18:39:14 -08:00
package-lock.json Rename workspace modules to avoid confusion 2024-04-23 04:06:15 -04:00
package.json chore(main): release 2.2.0 2024-04-23 02:03:34 +00:00
puter-gui.json Add WIP color sliders 2024-04-06 02:35:06 -04:00
README.md Add link to Bug Bounty program 2024-04-21 15:04:49 -07:00
run-selfhosted.js Rename workspace modules to avoid confusion 2024-04-23 04:06:15 -04:00
SECURITY-ACKNOWLEDGEMENTS.md Update SECURITY-ACKNOWLEDGEMENTS.md to add Tim's GitHub 2024-03-13 18:55:14 -07:00
SECURITY.md Create SECURITY.md 2024-03-13 16:33:03 -07:00
test.txt fix: test release-please action #4 2024-04-22 18:40:49 -04:00
utils.js Migrate to JavaScript modules 2024-03-20 14:10:39 +00:00

Puter.com, The Personal Cloud Computer: All your files, apps, and games in one place accessible from anywhere at any time.

The Internet OS! Free, Open-Source, and Self-Hostable.

« LIVE DEMO »

Puter.com · SDK · Discord · Reddit · X (Twitter) · Bug Bounty

screenshot


Puter

Puter is an advanced, open-source internet operating system designed to be feature-rich, exceptionally fast, and highly extensible. It can be used to build remote desktop environments or serve as an interface for cloud storage services, remote servers, web hosting platforms, and more.


Getting Started

After reading this section, please proceed to Self-Hosting and Configuration below. Read these instructions carefully or you may see errors due to an invalid setup.

Local Development

git clone https://github.com/HeyPuter/puter
cd puter
npm install
npm start

This will launch Puter at http://localhost:4000 (or the next available port).


Using Docker

note: it is not necessary to run this within a clone of this repository. For contributors, it is recommended to use the Local Development instructions.

mkdir puter && cd puter && mkdir -p puter/config puter/data && sudo chown -R 1000:1000 puter && docker run --rm -p 4100:4100 -v `pwd`/puter/config:/etc/puter -v `pwd`/puter/data:/var/puter  ghcr.io/heyputer/puter

Using Docker Compose

note: it is not necessary to run this within a clone of this repository. For contributors, it is recommended to use the Local Development instructions.

mkdir -p puter/config puter/data
sudo chown -R 1000:1000 puter
wget https://raw.githubusercontent.com/HeyPuter/puter/main/docker-compose.yml
docker compose up

See Configuration for next steps.


⚠️ Self-Hosting ⚠️

The self-hosted version of Puter is currently in alpha stage and should not be used in production yet. It is under active development and may contain bugs, other issues. Please exercise caution and use it for testing and evaluation purposes only.


Configuration

Running the server will generate a configuration file in one of these locations:

  • config/config.json when Using Docker
  • volatile/config/config.json in Local Development
  • /etc/puter/config.json on a server (or within a Docker container)

Domain Name

To access Puter on your device, you can simply go to the address printed in the server console (usually puter.localhost:4100).

To access Puter from another device, a domain name must be configured, as well as an api subdomain. For example, example.local might be the domain name pointing to the IP address of the server running puter, and api.example.com must point to this address as well. This domain must be specified in the configuration file (usually volatile/config/config.json) as well.

See domain configuration for more information.

Configure the Port

  • You can specify a custom port by setting http_port to a desired value
  • If you're using a reverse-proxy such as nginx or cloudflare, you should also set pub_port to the public (external) port (usually 443)
  • If you have HTTPS enabled on your reverse-proxy, ensure that protocol in config.json is set accordingly

Default User

By default, Puter will create a user called default_user. This user will have a randomly generated password, which will be printed in the development console. A warning will persist in the dev console until this user's password is changed. Please login to this user and change the password as your first step.


License

This repository is licensed under AGPL-3.0; However, our SDK (puter.js) is also available under Apache 2.0, as indicated by the license file in that section (packages/puter-js) of this repository.


FAQ

What's the use case for Puter?

Puter can be used as:

  • An alternative to Dropbox, Google Drive, OneDrive, etc. with a fresh interface and powerful features.
  • Remote desktop environment for servers and workstations.
  • A platform for building and hosting websites, web apps, and games.
  • A friendly, open-source project and community to learn about web development, cloud computing, distributed systems, and much more!

Why isn't Puter built with React, Angular, Vue, etc.?

For performance reasons, Puter is built with vanilla JavaScript and jQuery. Additionally, we'd like to avoid complex abstractions and to remain in control of the entire stack, as much as possible.

Also partly inspired by some of our favorite projects that are not built with frameworks: VSCode, Photopea, and OnlyOffice.


Why jQuery?

Puter interacts directly with the DOM and jQuery provides an elegant yet powerful API to manipulate the DOM, handle events, and much more. It's also fast, mature, and battle-tested.


#DoesItRunPuter


Credits

The default wallpaper is created by Milad Fakurian and published on Unsplash.

Icons by Papirus under GPL-3.0 license.

Icons by Iconoir under MIT license.

Icons by Elementary Icons under GPL-3.0 license.

Icons by Tabler Icons under MIT license.

Icons by bootstrap-icons under MIT license.