1 Star 0 Fork 483

googlezhang / Rainbond_1

forked from 好雨科技 / Rainbond 
Create your Gitee Account
Explore and code with more than 12 million developers,Free private repositories !:)
Sign up
Clone or Download
contribute
Sync branch
Cancel
Notice: Creating folder will generate an empty file .keep, because not support in Git
Loading...
README
LGPL-3.0

Rainbond GitHub stars Rainbond version GoDoc

WebsiteDocumentation

What is Rainbond ?

Rainbond is a cloud native multi cloud application management platform, which is easy to use and does not need to understand containers, kubernetes and underlying complex technologies. It supports the management of multiple kubernetes clusters and the management of the whole life cycle of enterprise applications. The main functions include application development environment, application market, micro service architecture, application delivery, application operation and maintenance, application level multi cloud management, etc.

Why Rainbond ?

Kubernetes serves as a system for managing containerized applications. It provides a basic mechanism for the deployment, maintenance and expansion of applications. However, when users transform their traditional applications to cloud native applications, they will encounter the following problems when using kubernetes:

  • Container deployment of enterprise applications
  • Kubernetes has a steep learning curve
  • How can deployed applications be delivered and upgraded in other kubernetes environments

Rainbond follows the design concept of application centered and unifies the technologies related to containers, kubernetes and underlying infrastructure, so that users can focus on the business itself and avoid spending a lot of learning and management energy on technologies other than the business.

Rainbond function and architecture

Rainbond-Arch

Rainbond manages enterprise applications based on public cloud, private cloud and self built kubernetes, and supports application level multi cloud management.

Rainbond Support application lifecycle management, that is, one-stop connection of development, architecture, delivery and operation and maintenance.

Components in Rainbond are independent, reusable, extensible and integrated units that support different granularity and version management. Components can be reused in different application scenarios. Components themselves can be upgraded iteratively. The accumulated components are stored in the component library, realizing the accumulation and reuse of enterprise digital capabilities.

Installation

Rainbond supports multiple installation methods. You can install the AllInOne version through the following command to quickly experience the full functions of rainbond.

Please note that:This method is only applicable to the rapid experience of developers and has no production availability。For other installation methods, please refer to Web page installationHelm installationDocking with cloud service providersDocking with other platformsHigh availability installation

docker run --privileged -d  -p 7070:7070 -p 80:80 -p 443:443 -p 6060:6060 -p 8443:8443 \
--name=rainbond-allinone --restart=unless-stopped \
-v ~/.ssh:/root/.ssh \
-v ~/rainbonddata:/app/data \
-v /opt/rainbond:/opt/rainbond \
-v ~/dockerdata:/var/lib/docker \
-e ENABLE_CLUSTER=true \
registry.cn-hangzhou.aliyuncs.com/goodrain/rainbond:v5.6.0-dind-allinone \
&& docker logs -f rainbond-allinone

Online experience

You can access the trial environment online experience platform function. Due to limited resources, you only have view permission. If you need to experience more functions, please deploy it yourself.

Quick start

  1. Rainbond Introduction
  2. Create the first application (component)

Video tutorial

  1. Rainbond Installation series collection
  2. Rainbond Introductory tutorial
  3. Rainbond Realize integrated development environment
  4. Rainbond Realize unified management of enterprise applications

Participating communities

Rainbond Open source community You are welcome to review or contribute to the use case usage of rainbond in the community.

Rainbond Project official website Check out more about rainbond.

WeChat scan code focuses on the Rainbond official account to see Rainbond best practices.

DingTalk Search Group : 31096419

Add a wechat assistant to enter the Rainbond Technology Exchange Group:

Contributing

We very much welcome you to participate in the contribution and sharing of platform experience, standardized applications, plug-in sharing and other fields in the rainbond community.

If you are a user who is using rainbond, and you have a deep understanding of rainbond and agree with the technical route, and there is a great demand within your enterprise, we welcome you to participate in the development of rainbond project

Related repositories

At present, the warehouse is the implementation code of the core service at the end of rainbond data center. The project also includes the following sub projects:

License

Rainbond follow LGPL-3.0 license, Details see LICENSE and Licensing

GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below. 0. Additional Definitions. As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License. "The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below. An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library. A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version. The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work. 1. Exception to Section 3 of the GNU GPL. You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL. 2. Conveying Modified Versions. If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document. 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following: 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) 5. Combined Libraries. You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 6. Revised Versions of the GNU Lesser General Public License. The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

About

云原生且易用的应用管理平台 | Cloud-native and easy-to-use application management platform expand collapse
Go
LGPL-3.0
Cancel

Releases

No release

Contributors

All

Activities

Load More
can not load any more
Go
1
https://gitee.com/googlezhang/Rainbond_1.git
git@gitee.com:googlezhang/Rainbond_1.git
googlezhang
Rainbond_1
Rainbond_1
main

Search