File pushing method, system and device, storage medium and product

Abstract

The invention discloses a file pushing method, system and device, a storage medium and a product, and relates to the technical field of data processing.The file pushing method comprises the steps that a file pushing request sent by a git warehouse is received, and user information and a first file are obtained based on the file pushing request; a second file corresponding to the first file in target files in object storage sent to a service layer through an interaction layer is pushed to a target user corresponding to the user information, the interaction layer is established based on a low-code platform, and the service layer is established based on a faas function. According to the invention, the technical problems of complex construction and high cost of related technologies can be avoided.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a file pushing method, system, device, storage medium and product. Background Art

[0002] git is a distributed version control system used to track modifications to files during software development. In projects that use git for version control, pushing local changes to remote repositories is a common operation.

[0003] In the related technology, the code push request is intercepted and analyzed through the hook component to obtain the code change information corresponding to the code push request. The hook component is triggered by the receiving action of the code push request. The hook component is generally a separate back-end project, and a front-end project is required to call the hook component interface to implement the corresponding function. However, the related technology is complex to build and the cost is high. Summary of the invention

[0004] The main purpose of this application is to provide a file push method, aiming to solve the technical problems of complex construction and high cost of related technologies.

[0005] To achieve the above purpose, the present application proposes a file pushing method, which includes:

[0006] Receive a file push request sent by the git repository, and obtain user information and the first file based on the file push request;

[0007] Push a second file corresponding to the first file in a target file in an object storage sent to the service layer via the interaction layer to a target user corresponding to the user information, wherein the interaction layer is established based on a low-code platform, and the service layer is established based on a Faas function.

[0008] In one embodiment, the step of receiving a file push request sent by a git repository and obtaining user information and a first file based on the file push request includes:

[0009] In response to a selection operation on an initial file in a project group in the interactive layer, calling the initial file under the project group directory in the git repository through a code cloud interface and sending it to the interactive layer, so that the interactive layer displays the initial file;

[0010] In response to an editing operation on the initial file in the interactive layer, the edited target file is acquired and stored in an object storage, wherein the edited target file includes remark information.

[0011] In one embodiment, in response to the selection operation of the initial file in the project group in the interactive layer, calling the initial file under the project group directory in the git repository through the code cloud interface to send it to the interactive layer for the interactive layer to display the initial file, the step further includes:

[0012] Based on a preset timing, the interface credentials of the code cloud interface are updated to obtain the code cloud interface after the interface credentials are updated.

[0013] In addition, to achieve the above purpose, the present application also proposes a file push method, the method comprising:

[0014] Acquire a first file and user information, generate a file push request based on the first file and the user information, and send the file push request to the service layer;

[0015] In response to a receiving operation of the service layer based on the file push request, triggering a hook component;

[0016] Based on the hook component, the file push request is intercepted, and based on the file push request, a second file in the target file corresponding to the first file is verified to obtain a verification result.

[0017] In one embodiment, the step of intercepting the file push request based on the hook component, and verifying the second file corresponding to the first file in the target file based on the file push request, and obtaining the verification result includes:

[0018] If the verification result is that the file content of the second file is consistent with that of the first file, based on the hook component, the intercepted file push request is sent to the service layer again, so that the service layer can push the second file corresponding to the first file to the target user corresponding to the user information based on the file push request.

[0019] In one embodiment, the steps of obtaining the first file and user information, generating a file push request based on the first file and the user information, and sending the file push request to the service layer include:

[0020] Acquire a first file and user information, generate a file push request based on the first file and the user information, and store the generated file push request in a cache space, wherein the cache space is used to store requests for each user;

[0021] The file push request is compared with the historical requests of the cache space, and if there is no identical request for the same user, the file push request is sent to the service layer.

[0022] In addition, to achieve the above purpose, the present application also proposes a file push system, the file push system comprising:

[0023] The service layer is used to receive a file push request sent by the git repository, and based on the file push request, obtain user information and the first file; push the second file corresponding to the first file in the target file in the object storage sent to the service layer via the interaction layer to the target user corresponding to the user information, wherein the interaction layer is established based on the low-code platform, and the service layer is established based on the Faas function;

[0024] A git repository is used to obtain a first file and user information, generate a file push request based on the first file and the user information, and send the file push request to a service layer; in response to a receiving operation of the service layer based on the file push request, a hook component is triggered; based on the hook component, the file push request is intercepted, and based on the file push request, a second file in the target file corresponding to the first file is verified to obtain a verification result.

[0025] In addition, to achieve the above objectives, the present application also proposes a file pushing device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the file pushing method described above.

[0026] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the file push method described above are implemented.

[0027] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the file pushing method described above are implemented.

[0028] One or more technical solutions proposed in this application have at least the following technical effects:

[0029] Compared with the related technology, the hook component is generally a separate back-end project, and a front-end project is required to call the hook component interface to implement the corresponding function. However, the existing technology is complex to build and has high costs. The present application receives a file push request sent by the git repository, and obtains user information and the first file based on the file push request; the second file corresponding to the first file in the target file in the object storage sent to the service layer via the interaction layer is pushed to the target user corresponding to the user information, wherein the interaction layer is established based on a low-code platform, and the service layer is established based on a faas function. It can be understood that after receiving the file push request sent by the git repository, the present application will, based on the first file, send the target file sent by the interaction layer established based on the low-code platform to the service layer established based on the faas function to the target user corresponding to the user information, thereby avoiding the problems of complex construction and high costs of the existing technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0032] Figure 1 A flowchart of the first embodiment of the method for pushing application documents is provided;

[0033] Figure 2 This is the overall flow chart of the method for pushing application documents;

[0034] Figure 3 A flowchart of the second embodiment of the method for pushing application documents is provided;

[0035] Figure 4 This is a schematic diagram of the module structure of the file pushing device according to an embodiment of the present application;

[0036] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the file push method in the embodiment of the present application.

[0037] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0038] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0039] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0040] The main solution of the embodiment of the present application is: receiving a file push request sent by a git repository, and obtaining user information and a first file based on the file push request; pushing a second file corresponding to the first file in a target file in an object storage sent to the service layer via the interaction layer to a target user corresponding to the user information, wherein the interaction layer is established based on a low-code platform, and the service layer is established based on a FaaS function.

[0041] In the related technology, the code push request is intercepted and analyzed through the hook component to obtain the code change information corresponding to the code push request. The hook component is triggered by the receiving action of the code push request. The hook component is generally a separate back-end project, and a front-end project is required to call the hook component interface to implement the corresponding function. However, the existing technology is complex to build and the cost is high.

[0042] After receiving the file push request sent by the git repository, this application will, based on the first file, send the target file sent by the interaction layer established based on the low-code platform to the service layer established based on the Faas function and push it to the target user corresponding to the user information, thereby avoiding the problem of complex construction and high cost of the existing technology.

[0043] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, etc. The following takes a file push device as an example to illustrate this embodiment and the following embodiments.

[0044] Based on this, the present application embodiment provides a file push method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the method for pushing documents of this application.

[0045] In this embodiment, refer to Figure 2 , Figure 2 The overall flow chart is provided. The file push method comprises steps S100 to S200:

[0046] Step S100, receiving a file push request sent by the git repository, and obtaining user information and a first file based on the file push request;

[0047] It should be noted that the execution subject of this embodiment is a file push device. The file push device is provided with a service layer and a git repository. The git repository is used to store all files of the project, and also records all historical change information of these files. The service layer is used to temporarily store the edited files, and after receiving the file push request, the temporarily stored files are sent to the corresponding user.

[0048] It is understandable that the user information is the user ID, which is a unique identifier that represents the user's identity. The first file is an accurate push file uploaded by the user. After obtaining the file push request from the git repository, the service layer of the file push device parses the file push request to obtain the user information of the unique identifier that represents the user's identity and the accurate first file.

[0049] Step S200, pushes the second file corresponding to the first file in the target file in the object storage sent to the service layer via the interaction layer to the target user corresponding to the user information, wherein the interaction layer is established based on the low-code platform and the service layer is established based on the Faas function.

[0050] It should be noted that the file push device is also equipped with an interaction layer, which is built on a low-code platform and is mainly used for adding, modifying, deleting and querying files. Object storage is a cloud storage service used to store and retrieve a large number of unstructured data files, and is used to store files temporarily stored in the service layer. The service layer of the push device will push the files stored in the object storage to the target user corresponding to the user information based on the first file obtained after parsing the file push request.

[0051] Specifically, the interactive layer low-code platform is built, which allows developers to build applications through a graphical interface and drag-and-drop components without writing a large amount of traditional programming code. The main goal of the low-code platform is to improve development efficiency, reduce development costs, and enable business personnel to participate in the application development process.

[0052] The service layer is built on FaaS functions, which can quickly deploy and scale the backend logic of the application and run the code without managing servers.

[0053] In a feasible implementation manner, receiving a file push request sent by a git repository, and before the step of obtaining user information and a first file based on the file push request, the following steps are included:

[0054] In response to a selection operation on an initial file in a project group in the interactive layer, calling the initial file under the project group directory in the git repository through a code cloud interface and sending it to the interactive layer, so that the interactive layer displays the initial file;

[0055] It is understandable that the code cloud interface is the code cloud openApi, which is used to access files stored in the git repository. When the user selects the initial file in a project group in the interactive layer of the file push device, the service layer of the file push device will respond to the user's operation in the interactive layer, access the git repository corresponding to the project group through the code cloud openApi, and determine the initial file under the project group directory in the git repository, and display the accessed initial file in the interactive layer.

[0056] In particular, the interactive layer of the file push device improves the readability of files through the structure of the project file tree. Through the project file tree, users can clearly select project groups and files under project groups, wherein the project file tree is established based on node.js.

[0057] In response to an editing operation on the initial file in the interactive layer, the edited target file is acquired and stored in an object storage, wherein the edited target file includes remark information.

[0058] It should be noted that the target file is an edited file, which includes notes to explain the edited content. The user can perform editing operations on the initial file displayed in the interactive layer. After responding to the user's editing operation on the interactive layer, the service layer of the file push device will obtain the edited target file and store it in the object storage of the service layer.

[0059] Specifically, the service layer is pre-configured with an interface address corresponding to the git repository. After the service layer clicks the corresponding project group, the service layer will display the pre-stored interface address corresponding to the project group, so that the service layer can obtain the corresponding initial file based on the interface address.

[0060] In a feasible implementation manner, in response to the selection operation of the initial file in the project group in the interactive layer, the initial file under the project group directory in the git repository is called through the code cloud interface to be sent to the interactive layer so that the interactive layer displays the initial file, and the following steps are also included:

[0061] Based on a preset timing, the interface credentials of the code cloud interface are updated to obtain the code cloud interface after the interface credentials are updated.

[0062] It is understandable that the interface credential is a token credential, which has an expiration time. In order to ensure that the credential of the Code Cloud interface is always valid, a scheduled task can be set to regularly update the interface credential. The service layer of the file push device sets a scheduled task to regularly update the interface credential and obtain the Code Cloud interface after the interface credential is updated.

[0063] In this implementation, the file push device builds an interaction layer through a low-code platform and a service layer through a FaaS function, which solves the problem of complex construction and high cost of the existing technology, and pushes files through the constructed interaction layer and service layer.

[0064] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 3 The file pushing method further includes steps A100 to A300:

[0065] Step A100, obtaining a first file and user information, generating a file push request based on the first file and the user information, and sending the file push request to the service layer;

[0066] It should be noted that after receiving the first file uploaded by the user and the user information, the git repository of the file push device will generate a file push request based on the first file and the user information, and send the request to the service layer to respond to the request and perform corresponding operations.

[0067] Specifically, when a user edits a file in the interactive layer of the file push device, the edited file will be temporarily stored in the object storage. At the same time, the edited file stored in the object storage needs to be sent to the corresponding person in charge of the project for confirmation.

[0068] Step A200, in response to the service layer receiving operation based on the file push request, triggering the hook component;

[0069] It is understandable that the hook component is triggered by the receiving action of the push request. When the git repository of the file push device detects that the service layer has received the file push request, the hook component will be automatically triggered.

[0070] Step A300, based on the hook component, intercept the file push request, and based on the file push request, verify the second file in the target file corresponding to the first file to obtain a verification result.

[0071] It should be noted that the verification result is a content verification of whether the file content is missing. The git repository of the file push device intercepts the file push request through the hook component so that the target file can be verified before the service layer performs the next operation based on the file push request to avoid affecting the file push process.

[0072] In a feasible implementation manner, based on the hook component, the file push request is intercepted, and based on the file push request, a second file in the target file corresponding to the first file is verified, and the step of obtaining the verification result includes:

[0073] If the verification result is that the file content of the second file is consistent with that of the first file, based on the hook component, the intercepted file push request is sent to the service layer again, so that the service layer can push the second file corresponding to the first file to the target user corresponding to the user information based on the file push request.

[0074] It is understandable that if the verification result obtained by the hook component of the git repository of the file push device is that the target file in the object storage is consistent with the file content corresponding to the first file, the file push request will be sent to the service layer again, so that the service layer can respond to the file push request and push the target file in the object storage to the target user corresponding to the user information.

[0075] In particular, in order to ensure the accuracy of the data in the second file that needs to be pushed, the file push device can generate a corresponding hash value for each line in the target file when storing the target file in the object storage, and store it. When the hook component intercepts the file request and performs consistency verification, it can generate a hash value for each line in the first file, and extract the pre-stored hash value of each line in the second file corresponding to the first file, compare the hash value of the first file with the hash value of the second file, and if it is found that the hash value of any line is different, it means that the two lines of data are inconsistent. Once an inconsistent line is found, it is necessary to locate the line of data, and generate a push failure prompt and return to the git repository. If the hash values ​​are consistent, the service layer is allowed to continue the file push operation.

[0076] Specifically, before the service layer pushes the target file in the object storage to the target user corresponding to the user information, it needs to encrypt the target file through the national encryption algorithm authentication library in the service layer and then send it to the target user. Among them, the client corresponding to the target user will interact with the national encryption algorithm library for keys before pushing the file, so that the client corresponding to the target user can directly obtain the decrypted content in the target file.

[0077] In a feasible implementation manner, the steps of obtaining the first file and user information, generating a file push request based on the first file and the user information, and sending the file push request to the service layer include the following steps:

[0078] Acquire a first file and user information, generate a file push request based on the first file and the user information, and store the generated file push request in a cache space, wherein the cache space is used to store requests for each user;

[0079] It is understandable that the hook components in the git repository can perform specific operations when receiving new submissions, such as sending notification emails or messages to team members. If the push includes multiple submissions, or multiple submissions are generated by a merge operation, these hooks may be triggered for each submission separately, resulting in the recipient receiving multiple notifications, so it is necessary to add a request judgment step before sending the request. After the git repository of the file push device generates a file push request, it will store the generated file push request in the cache space, which is used to store the most recent request records. The request records stored in the cache space will be cleared regularly to avoid misjudgments that affect subsequent operations.

[0080] In particular, after storing the generated file push request in the cache space, the file push device can also set stricter conditions to decide when to send the notification, for example, sending a notification only when there is a new commit on a specific branch, or triggering a notification only when a commit message contains specific keywords.

[0081] The file push request is compared with the historical requests of the cache space, and if there is no identical request for the same user, the file push request is sent to the service layer.

[0082] It should be noted that before processing the request, the git repository of the file push device will check whether there is an identical request for the same user in the cache space. If not, it will proceed with the subsequent steps based on the file push request. If so, the user information of the user in the file push request will be added to avoid repeated sending, which will cause information folding and the user to ignore important information.

[0083] In this implementation, the file push device checks the pushed files through the git repository to avoid information omissions, improves the efficiency of file push, and stores the generated file push requests in the cache space. Before processing the request, it checks whether there is the same request for the same user in the cache space to avoid repeated sending, which causes information folding and users ignoring important information.

[0084] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the document push method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0085] This application also provides a file push system, please refer to Figure 4, the file push system comprises:

[0086] The service layer 10 is used to receive a file push request sent by the git repository, and based on the file push request, obtain user information and the first file; push the second file corresponding to the first file in the target file in the object storage sent to the service layer via the interaction layer to the target user corresponding to the user information, wherein the interaction layer is established based on the low-code platform, and the service layer is established based on the Faas function;

[0087] The git repository 20 is used to obtain a first file and user information, generate a file push request based on the first file and the user information, and send the file push request to the service layer; in response to the service layer's receiving operation based on the file push request, trigger a hook component; based on the hook component, intercept the file push request, and based on the file push request, verify the second file corresponding to the first file in the target file to obtain a verification result.

[0088] Optionally, before the step of receiving a file push request sent by a git repository and obtaining user information and a first file based on the file push request, the service layer is further configured to:

[0089] In response to a selection operation on an initial file in a project group in the interactive layer, the initial file under the project group directory in the git repository is called through a code cloud interface and sent to the interactive layer so that the interactive layer can display the initial file; in response to an editing operation on the initial file in the interactive layer, the edited target file is obtained and stored in an object storage, wherein the edited target file includes comment information.

[0090] Optionally, in response to the selection operation of the initial file in the project group in the interactive layer, the initial file under the project group directory in the git repository is called through the code cloud interface to be sent to the interactive layer so that the interactive layer can display the initial file. After that, the service layer is further used to:

[0091] Based on a preset timing, the interface credentials of the code cloud interface are updated to obtain the code cloud interface after the interface credentials are updated.

[0092] Optionally, after the step of intercepting the file push request based on the hook component and verifying the second file corresponding to the first file in the target file based on the file push request and obtaining the verification result, the git repository is further used to:

[0093] If the verification result is that the file content of the second file is consistent with that of the first file, based on the hook component, the intercepted file push request is sent to the service layer again, so that the service layer can push the second file corresponding to the first file to the target user corresponding to the user information based on the file push request.

[0094] Optionally, in the step of obtaining the first file and the user information, generating a file push request based on the first file and the user information, and sending the file push request to the service layer, the git repository is also used to:

[0095] Acquire a first file and user information, generate a file push request based on the first file and the user information, and store the generated file push request in a cache space, wherein the cache space is used to store requests for each user;

[0096] The file push request is compared with the historical requests of the cache space, and if there is no identical request for the same user, the file push request is sent to the service layer.

[0097] The file pushing device provided by the present application adopts the file pushing method in the above embodiment, which can solve the technical problem of file pushing. Compared with the prior art, the beneficial effects of the file pushing device provided by the present application are the same as the beneficial effects of the file pushing method provided by the above embodiment, and other technical features in the file pushing device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0098] The present application provides a file pushing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the file pushing method in the above-mentioned embodiment 1.

[0099] Reference below Figure 5 , which shows a schematic diagram of the structure of a file push device suitable for implementing an embodiment of the present application. The file push device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, tablet computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The file push device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0100] like Figure 5 As shown, the file push device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the file push device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the file push device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a file push device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0101] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0102] The file push device provided by the present application adopts the file push method in the above embodiment to solve the technical problem of file push. Compared with the prior art, the beneficial effects of the file push device provided by the present application are the same as the beneficial effects of the file push method provided by the above embodiment, and other technical features in the file push device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0103] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0104] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0105] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the file pushing method in the above-mentioned embodiment.

[0106] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0107] The computer-readable storage medium may be included in the file pushing device; or may exist independently without being assembled into the file pushing device.

[0108] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the file pushing device, the file pushing device: receives a file push request sent by the git repository, and obtains user information and a first file based on the file push request; pushes a second file corresponding to the first file in the target file in the object storage sent to the service layer via the interaction layer to a target user corresponding to the user information, wherein the interaction layer is established based on a low-code platform, and the service layer is established based on a FaaS function.

[0109] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0110] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0111] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0112] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned file push method, and can solve the technical problem of file push. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the file push method provided by the above-mentioned embodiment, and will not be repeated here.

[0113] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned file pushing method when executed by a processor.

[0114] The computer program product provided by this application can solve the technical problem of file push. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the file push method provided by the above embodiment, which will not be repeated here.

[0115] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A file pushing method, characterized in that: Applied to the service layer, the file push method includes: Receive a file push request sent by the git repository, and obtain user information and the first file based on the file push request; Push a second file corresponding to the first file in a target file in an object storage sent to the service layer via the interaction layer to a target user corresponding to the user information, wherein the interaction layer is established based on a low-code platform, and the service layer is established based on a Faas function.

2. The file pushing method according to claim 1, characterized in that: The step of receiving a file push request sent by a git repository and obtaining user information and a first file based on the file push request includes: In response to a selection operation on an initial file in a project group in the interactive layer, calling the initial file under the project group directory in the git repository through a code cloud interface and sending it to the interactive layer, so that the interactive layer displays the initial file; In response to an editing operation on the initial file in the interactive layer, the edited target file is acquired and stored in an object storage, wherein the edited target file includes remark information.

3. The file pushing method according to claim 2, characterized in that: In response to the selection operation of the initial file in the project group in the interactive layer, the initial file under the project group directory in the git repository is called through the code cloud interface to be sent to the interactive layer so that the interactive layer can display the initial file, and the step also includes: Based on a preset timing, the interface credentials of the code cloud interface are updated to obtain the code cloud interface after the interface credentials are updated.

4. A file pushing method, characterized in that: Applied to git repository, the file push method includes: Acquire a first file and user information, generate a file push request based on the first file and the user information, and send the file push request to the service layer; In response to a receiving operation of the service layer based on the file push request, triggering a hook component; Based on the hook component, the file push request is intercepted, and based on the file push request, a second file in the target file corresponding to the first file is verified to obtain a verification result.

5. The file pushing method according to claim 4, characterized in that: The step of intercepting the file push request based on the hook component, and verifying the second file corresponding to the first file in the target file based on the file push request, and obtaining the verification result includes: If the verification result is that the file content of the second file is consistent with that of the first file, based on the hook component, the intercepted file push request is sent to the service layer again, so that the service layer can push the second file corresponding to the first file to the target user corresponding to the user information based on the file push request.

6. The file pushing method according to claim 4, characterized in that: The steps of obtaining the first file and user information, generating a file push request based on the first file and the user information, and sending the file push request to the service layer include: Acquire a first file and user information, and generate a file push request based on the first file and the user information; Storing the generated file push request in a cache space, wherein the cache space is used to store the request for each user; The file push request is compared with the historical requests of the cache space, and if there is no identical request for the same user, the file push request is sent to the service layer.

7. A file push system, characterized in that: The system comprises: The service layer is used to receive a file push request sent by the git repository, and based on the file push request, obtain user information and the first file; push the second file corresponding to the first file in the target file in the object storage sent to the service layer via the interaction layer to the target user corresponding to the user information, wherein the interaction layer is established based on the low-code platform, and the service layer is established based on the Faas function; The git repository is used to obtain a first file and user information, generate a file push request based on the first file and the user information, and send the file push request to the service layer; in response to the service layer's receiving operation based on the file push request, trigger a hook component; based on the hook component, intercept the file push request, and based on the file push request, verify the second file corresponding to the first file in the target file to obtain a verification result.

8. A file pushing device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the file pushing method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the file pushing method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the file pushing method according to any one of claims 1 to 6 are implemented.

Images