Small Object Storage System for Java Projects with File Upload and Online Management

Small Object Storage System for Java Projects with File Upload and Online Management

2022-09-16 0 1,226
Resource Number 38564 Last Updated 2025-02-24
¥ 0 USD Upgrade VIP
Download Notice Demo
Can't download? Please contact customer service to submit a link error!
Value-added Service: Installation Guide Environment Configuration Secondary Development Template Modification Source Code Installation

Product Details 商品属性

  • Language: Java
  • Database:
  • License: License-Free
  • Source Code: Fully Open Source
  • Specification: Full Website Source
  • Delivery: Automatic (instant download after payment)

The OSS-Server recommended in this issue is a small object storage system that is provided for project development. Developers can remove services for file upload and facilitate file migration. In order to meet the needs of a single project and multiple systems, unified oss services are provided.

oss-server provides the following functions:

1, upload function

2, file online management function (including file preview, internal upload, delete, rename)

3. Permission management (upload api permission user maintenance, oss-server login system maintenance)

oss-server uses tomcat+nginx, tomcat provides the ability to upload object storage, nginx provides the ability to access online

oss does not provide file related log storage function, is a pure technical middleware

The main configurations of the server (application.properties) are as follows:

# Material store path -- ending with / 
material.root=/home/material/
# Material download path root directory, this directory is nginx read directory, can use the domain name 
material.invokingRoot=http://192.168. 0.7 < / span > / < / code > < / pre >

Using the above configuration, the server nginx configuration is as follows:

 

server{
        listen          80;
        server_name 192.168.0.7;
        charset utf-8;
        location / {
           root /home/material/;
        }
    }

This configuration is simply to configure the nginx access path,server_name can be a domain name.

oss-server provides the following two submission methods

In this way, the back-end needs to convert the file into a base64 string and submit it to the oss-server. In this way, the oss-server provides the java version of the sdk. For details, see the OSS-server-SDK-Java program

.
< p data – track = “15” > request interface: / oss/material/uploadByBinary < / p >

Interface type: post

Request type: application/json;

{
    "project": "",
    "files": [
        {
            "original_name": "test.png",
            "file": "File stream base64 string",
            "media_type": "png"
        }
    ]
}

Response json

{
    "code": "8200",
    "message": "Success",
    "data": [{
        "id": "1a4c705d260647cc9be951ead3a449e6",
        "url": "http://192.168.0.7/province_IIII/201805/30/1a4c705d260647cc9be951ead3a449e6.jpg",
        "store": "/province_IIII/201805/30/1a4c705d260647cc9be951ead3a449e6.jpg"
    }]
}

form Submit the form directly

In this way, the front-end can submit and upload directly through the form, and the back-end does not need to provide transit

Request interface: /oss/material/{project}/uploadMaterial

Interface type: post

{
    "code": "8200",
    "message": "Success",
    "data": [{
        "id": "1a4c705d260647cc9be951ead3a449e6",
        "url": "http://192.168.0.7/province_IIII/201805/30/1a4c705d260647cc9be951ead3a449e6.jpg",
        "store": "/province_IIII/201805/30/1a4c705d260647cc9be951ead3a449e6.jpg"
    }]
}

form The following is an example of the form code:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"/>
    <title>Title</title>
    <script src="https://cdn.bootcss.com/jquery/3.2.1/jquery.min.js"></script>
</head>
<body>
<form action="http://192.168.0.7:18000/oss/material/province_III/uploadMaterial" method="post" enctype="multipart/form-data" target="uploadIFrame">
    <input type="file" name="file" value="Select File "/>
    <input type="submit" value="Submit "/>
</form>

<iframe name="uploadIFrame" style="width: 500px;height: 500px;border: 1px solid gray;"></iframe>
</body>
</html>

Software Architecture

Backend framework: SpringBoot 2.0.2.RELEASE

Back-end module: freemarker

Front end framework: layer+Bootstrap

Installation tutorial

< p data – track = “37” > 1, download the source code: git clone https://gitee.com/xiaoym/oss-server.git < / p >

2, modify the application.properties configuration file, mainly modify the following oss external domain name path has been uploaded storage path

# Material store path -- ending with / 
material.root=/home/material/
# Material download path root 
material.invokingRoot=http://192.168. 0.7 < / span > / < / code > < / pre >

3, package: mvn package

4, run the jar package: java -jar oss-server-0.0.1-SNAPSHOT.jar


资源下载此资源为免费资源立即下载
Telegram:@John_Software
☆☆☆☆☆0 pts · 0 reviews
Updated 2025-02-24

Q&A

No questions yet. Ask the seller!

Reviews

No reviews yet. Share your experience after purchase.

Disclaimer: This article is published by a third party and represents the views of the author only and has nothing to do with this website. This site does not make any guarantee or commitment to the authenticity, completeness and timeliness of this article and all or part of its content, please readers for reference only, and please verify the relevant content. The publication or republication of articles by this website for the purpose of conveying more information does not mean that it endorses its views or confirms its description, nor does it mean that this website is responsible for its authenticity.

TopTinker Admin Panel & RBAC Small Object Storage System for Java Projects with File Upload and Online Management https://toptinker.com/38564.html

商家类型:个人(声明)

Share free open-source source code

Q&A
  • 1. Automatic: After making an online payment, click the (Download) link to download the source code; 2. Manual: Contact the seller or the official to check if the template is consistent. Then, place an order and make payment online. The seller ships the goods, and both parties inspect and confirm that there are no issues. TopTinker will then settle the payment for the seller. Note: Please ensure to place your order and make payment through TopTinker. If you do not place your order and make payment through TopTinker, and the seller sends fake source code or encounters any issues, TopTinker will not assist in resolving them, nor can we guarantee your funds!
View details
  • 1. Default transaction cycle for source code: The seller manually ships the goods within 1-3 days. The amount paid by the user will be held in escrow by TopTinker until 7 days after the transaction is completed and both parties confirm that there are no issues. TopTinker will then settle with the seller. In case of any disputes, TopTinker will have staff to assist in handling until the dispute is resolved or a refund is made! If the buyer places an order and makes payment not through TopTinker, any issues and disputes have nothing to do with TopTinker, and TopTinker will not be responsible for any liabilities!
View details
  • 1. TopTinker will permanently archive the transaction process between both parties and snapshots of the traded goods to ensure the authenticity, validity, and security of the transaction! 2. TopTinker cannot guarantee services such as "permanent package updates" and "permanent technical support" after the merchant's commitment. Buyers are advised to identify these services on their own. If necessary, they can contact TopTinker for assistance; 3. When both website demonstration and image demonstration exist in the source code, and the text descriptions of the website and images are inconsistent, the text description of the image shall prevail as the basis for dispute resolution (excluding special statements or agreements); 4. If there is no statement such as "no legal basis for refund" or similar content, any indication on the product that "once sold, no refunds will be supported" or other similar declarations shall be deemed invalid; 5. Before the buyer places an order and makes payment, the transaction details agreed upon by both parties via WhatsApp or email can also serve as the basis for dispute resolution (in case of any inconsistency between the agreement and the description of the conflict, the agreement shall prevail); 6. Since chat records and email records can serve as the basis for dispute resolution, both parties should only communicate with each other through the contact information left on the system when contacting each other, in order to prevent the other party from denying their own commitments. 7. Although the probability of disputes is low, it is essential to retain important information such as chat records, text messages, and email records, in case a dispute arises, so that TopTinker can intervene quickly.
View details
  • 1. As a third-party intermediary platform, TopTinker solely protects transaction security and the rights and interests of both buyers and sellers based on the transaction contract (product description, agreed content before the transaction); 2. For online trading projects not on the TopTinker platform, any consequences are unrelated to this platform; regardless of the reason why the seller requests an offline transaction, please contact the administrator to report.
View details

Related Source code

TopTinker Customer Service

24-hour online professional services