Preface
Sometimes, we often encounter specific needs, such as generating a UUID, or converting the content of a docker-compose.yml file into a docker run command (or vice versa). Generally, at this time, we will search for online tools on the Internet to complete the conversion. Doing it occasionally is fine, but if you have this need frequently, looking for it online every time is too troublesome, and more importantly, it lacks style. Therefore, we need our own online toolbox, and to achieve this, we must rely on today's protagonist: IT-Tools.
Deploying IT-Tools
The docker run format command to build IT-Tools is as follows:
docker run --name it-tools -d -it \
-p 8080:80 \ #映射宿主机8080端口到容器内应用的80端口,请大家根据实际环境修改宿主机端口
corentinth/it-tools
Accessing IT-Tools
Usehttp://宿主机ip:8080Accessing IT-Tools:

The left part of the image above shows the tool categories, and the right part is the list of all tools. Clicking on a tool category will show the specific tools under that category:

You can also search using the search box above all tools:

For example, searching for uuid:

Press Enter to access:

Simple and easy to use.
Publishing to the public network
The online toolbox must be published to the public network. You need to choose the most suitable publishing method for yourself based on your actual environment and the reverse proxy you use. You can refer to several of my previous articles:
1、Docker Series: Building Your Own Reverse Proxy Based on NPM Using Docker
2、Linux Panel Series: Configuring Reverse Proxy and Publishing Using Non-443 Ports
3、Home Data Center Series: Getting Cloudflare for Free via Domestic ICP-Filed Cloud Hosts to Achieve Fast Access to Domestic Sites from Abroad
4、Home Data Center Series: Getting Cloudflare for Free via Home Broadband Without Public IP to Achieve Fast Website Building (Universal)
Among them, 1 and 2 are suitable for environments with a public IP but without a legal port 443 (home broadband, non-filed cloud hosts), where non-standard ports need to be added after the URL (if using Cloudflare to build the site, no port needs to be added, but you need to customize the origin port, which you can refer to:Home Data Center Series: Solving the Problem of Having a Public IP but No Legal 80 or 443 Ports for Website Building via Cloudflare's Origin Rules). 3 is suitable for filed cloud hosts, and 4 is suitable for all environments, which is also the method I recommend in the future.
[VIP]
Why do I suggest using 4 regardless of whether you have a public IP? Because this does not require running HTTPS directly on the public network (running HTTPS on the public network, although people won't know the details of what you are doing, the fact that you are doing it is unquestionable. This is just like even if the glass is opaque, I still know you are having sex in the car—the external characteristics are too obvious).[/vip]
If you are too lazy to build it yourself, you can also support and use the one I built:Invincible Online Toolbox.
P.S. I didn't expect to write a quick post so easily today, happy.