Lightning-fast, static web publishing with zero configuration and full control
- 📖 Table Of Contents
- Docs
- 🔧 Tools
- ❓ About The Project
- 🚀 Features
- 🔌 Built With
- 📍 Roadmap
- 🧑🤝🧑 Contributing
- License
- Authors
Read docs here for fast installation.
Sero - this tool is used to upload your site to sero servers
This project is essentially a revamp of the well-known surge.sh platform. While surge.sh is a fantastic tool for publishing web applications, I noticed it lacked certain features that could significantly enhance its utility. Therefore, I decided to create my own version, incorporating those missing elements to provide a more comprehensive and seamless user experience.
One key feature that it is self-hosted. This gives users more flexibility and control over their projects, allowing them to truly make their work their own. My goal with this project is to create a platform that not only meets but exceeds the needs of web developers, making the process of publishing web applications as hassle-free and efficient as possible. It also has some features that are not in surge.sh
So saying shortly this is a simple web server for static websites but with an ability to deploy it with custom subdomain without any configuration using cli tool. On upload it will automatically create subdomain for your site.
- Deploy in seconds without configuration
- Enable and disable site
new
- Download site
new
- Limits control
new
- Easy upload with cli tool
- Custom 404.html
(on 404 status user will see your 404.html)
- Custom 503.html
new
(on disabled site)
- Clean urls
- Dynamic CORS Management
[WIP]
SSE
Rust
Sea-orm
-sero is added to community examples
Axum
-sero is added to community examples
Postgres
Nginx
See the open issues for a list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- If you have suggestions for adding or removing projects, feel free to open an issue to discuss it, or directly create a pull request after you edit the README.md file with necessary changes.
- Please make sure you check your spelling and grammar.
- Create individual PR for each suggestion.
- Please also read through the Code Of Conduct before posting your first idea as well.
- Fork the Project
- Create your feature Branch (
git checkout -b feature/some
) - Commit your changes (
git commit -m 'implementation of some feature'
) - Push to the branch (
git push origin feature/some
) - Open a Pull Request
Distributed under the MIT License
- clowzed