70ba4d5e3d
* Add registration route * add route registration * remove ui * 0.3.6 build scaffold (#473) * wip * wip * wip * Merge Branches * Update helper.sh * add goreleaser * fix migration not working for LEGACY_WITHOUT_VERSION (#479) * wip * wip * add error handling to migration script * add migration tool * Adjusting shell script location * update disk user authentication method * delayed port modification * Update system.go Co-authored-by: Tiger Wang (王豫) <tigerwang@outlook.com> |
||
|---|---|---|
| .github | ||
| build | ||
| cmd/migration-tool | ||
| conf | ||
| interfaces | ||
| middleware | ||
| model | ||
| pkg | ||
| route | ||
| service | ||
| types | ||
| .all-contributorsrc | ||
| .gitignore | ||
| .gitmodules | ||
| .goreleaser.yaml | ||
| CHANGELOG.md | ||
| DEVELOPING.md | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| README.md | ||
| snapshot-dark.jpg | ||
| snapshot-light.jpg | ||
| snapshot-mobile.png | ||
| snapshot.png | ||
CasaOS - Your Home Cloud OS
Connect with the community developing HOME CLOUD, creating self-sovereign, and defining the future of the distributed cloud.
Website |
Demo |
GitHub
Why do we need Home Cloud?
Think about it seriously. Is control of our data, smart devices and digital assets now only in the hands of some big company?
- Is your photo album saved in their cloud service?
- Do your thermostats, monitors, lamps need to be used through their cloud services?
- Do your personal documents, memos, contacts, passwords, etc. reside in their cloud storage services?
- Are you just going to have to accept their decisions when they decide to change prices, review content or even discontinue services?
It sounds ridiculous, doesn't it? We are losing control of our own data!
Our ideal home cloud is one where you can manage all your data, devices and data assets very easily. In your own home, you have absolute control.
If you think what we are doing is valuable. Please give us a star ⭐ and fork it 🤞!
Features
- Friendly UI designed for home scenarios
- No code, no forms, intuitive, design for humanity
- Multiple hardware and base system support
- ZimaBoard, NUC, RPi, old computers, whatever is available.
- Selected apps in the app store, one-click installation
- Nextcloud, HomeAssiant, AdGuard, Jellyfin, *arr and more!
- Easily install numerous Docker apps
- Over 100,000 apps from the Docker ecosystem can be easily installed
- Elegant drive and file management
- What you see is what you get. No technical background required.
- Well-designed system/app widgets
- What you care about, at a glance. Resource usage, app status, and more!
Getting Started
CasaOS fully supports ZimaBoard, Intel NUC, and Raspberry Pi. Also, more computers and development boards and fully compatible with Ubuntu, Debian, Raspberry Pi OS, and CentOS with one-liner installation.
Hardware Compatibility
- amd64 / x86-64
- arm64
- armv7
System Compatibility
Official Support
- Debian 11 (✅ Tested, Recommended)
- Ubuntu Server 20.04 (✅ Tested)
- Raspberry Pi OS (✅ Tested)
Community Support
- Elementary 6.1 (✅ Tested)
- Armbian 22.04 (✅ Tested)
- Alpine (🚧 Not Fully Tested Yet)
- OpenWrt (🚧 Not Fully Tested Yet)
Quick Setup CasaOS
Freshly install a system from the list above and run this command:
wget -qO- https://get.casaos.io | bash
or
curl -fsSL https://get.casaos.io | bash
Uninstall CasaOS
v0.3.3 or newer
casaos-uninstall
Before v0.3.3
curl -fsSL https://get.icewhale.io/casaos-uninstall.sh | bash
Community
The word Casa comes from the Spanish word for "home". Project CasaOS originated as a pre-installed system for crowdfunded product ZimaBoard on Kickstarter.
After looking at many systems and software on the market, the team found no server system designed for home scenarios, sadly true.
So, we set out to build this open source project to develop CasaOS with our own hands, everyone in the community, and you.
We believes that through community-driven collaborative innovation and open communication with global developers, we can reshape the digital home experience like never before.
A warm welcome for you to get help or share great ideas in the Discord!
Contributing
CasaOS is a community-driven open source project and the people involved are CasaOS users. That means CasaOS will always need contributions from community members just like you!
How can I get involved? 🧐
Coding 💻 (WIP)
We are refining documentation that can be used for effective community collaboration. Feel free to start a discussion if you have a good idea.
Helping Users 💬
If you have extensive knowledge of CasaOS and related areas. We highly encourage you to help others as much as you can in Discord and Discussions.
Discord: https://discord.gg/knqAbbBbeX
GitHub Discussions: https://github.com/IceWhaleTech/CasaOS/discussions
Helping with Translations 🌍 (WIP)
CasaOS officially supports English and Chinese. You are welcome to help make CasaOS available in more languages.
Performing Alpha Testing ⚠️
Alpha testing is quality assurance testing that is engaged and driven by the community. It's a great way to get involved in contributing and experiencing the latest features before a new release.
The documentation is being refined and you can contact @JohnGuan via Discord. Ask to join the #casaos-alpha channel.
Writing Documentation 📖 (WIP)
Help make our documentation better by writing new content for the CasaOS Wiki, correcting existing material, or translating content into new languages.
Credits
Many thanks to everyone who has helped CasaOS so far!
Everyone's contribution is greatly appreciated. (Emoji Key)
 老竭力 💻 📖 🤔 🚇 🚧 📦 💬 👀 |
 link 💻 📖 🤔 🚇 🚧 💬 👀 |
 Tiger Wang (王豫) 💻 📖 🤔 🚇 🚧 🧑🏫 🛡️ 💬 👀 |
 Lauren 🤔 🔍 📆 💬 ⚠️ |
 John Guan 📝 🖋 📖 🤔 📋 🧑🏫 💬 👀 |
 David Tippett 📖 🤔 💬 |
 Skaya 🧑🏫 💬 ✅ 🌍 |
 AuthorShin ⚠️ 🐛 💬 🤔 |
 baptiste313 🌍 |
 DrMxrcy ⚠️ 🤔 💬 |
 Joooost 🤔 |
 Vitaly Potyarkin 🤔 |
 Bjørn Friese 🤔 |
 Protektor 🐛 🤔 💬 |
 llwaini 📆 ⚠️ ✅ |
This project follows the all-contributors specification. Contributions of any kind welcome!
Changelog
Detailed changes for each release are documented in the release notes.