example.com-proxmox

KO | EN

gitlite — search

#javascript #llm #golang #android #machine-learning #rust #linux #docker #macos #kubernetes #pytorch #security #mcp #openai

example.com-proxmox

(★ 23)

The example.com domain running in a virtual network on your Proxmox Server

example.com-proxmox 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

## example.com domain on Proxmox

![language](https://img.shields.io/github/languages/top/onemarcfifty/example.com-proxmox)    ![License](https://img.shields.io/github/license/onemarcfifty/example.com-proxmox)    ![Last Commit](https://img.shields.io/github/last-commit/onemarcfifty/example.com-proxmox)     ![FileCount](https://img.shields.io/github/directory-file-count/onemarcfifty/example.com-proxmox)    ![Stars](https://img.shields.io/github/stars/onemarcfifty/example.com-proxmox)    ![Forks](https://img.shields.io/github/forks/onemarcfifty/example.com-proxmox)

### What?

With these scripts you can install a complete example.com domain for testing purposes on your proxmox server. This includes:

1. A client machine running a graphical MATE environment as entry point that can be accessed over RDP with the following software on it:
    - a Firefox Browser with pre-loaded certificates
    - Thunderbird Mail client, pre-loaded
2. An OpenWrt Router as exit point
3. DNS (running on dnsmasq on the OpenWrt Router) for the example.com domain
4. A Docker host (running in an unprivileged LXC Container)
5. A "fake" SMTP / IMAP Server

The environment has everything you need to run the domain, including TLS certificates and e-Mail (internal only)

### Why?

A lot of examples and samples in the internet use the "example.com" domain. Testing software and running it in a "production" environment, i.e. in your "real" network can be cumbersome, because:

- you might break something
- you jeopardize the security and/or reliability of your network
- you would have to change things and roll them back later
- in order to make the examples run in the network, you need to change a lot of config files

For all these reasons, a test environment or "Sandbox" can be extremely useful.

- apply samples as they are without too many changes (we run the example.com domain - you remember ;-) )
- No influence on the "real" world - everything is safely encapsulated
- Quick deployment of Containers or VMs into the environment - just give a machine the virtual bridge as network and it will run inside the sandbox
- The client container is lightweight, RDP makes access from Linux or Windows easy

### How? (1) - Preparation steps

Create a virtual network for your test "sandbox" that is connected nowhere (i.e. will only be visible inside the example.com). This will be the network that your example.com domain will use.

- Select the PVE Server in the Proxmox VE GUI
- Select the "Network" node
- Click on "Create" - "Linux Bridge"
- do only fill out the following fields (i.e. leave all others blank):
    - Name (e.g. "vmbr999")
    - Autostart: ticked
    - VLAN aware: ticked
    - Comment (e.g. "Virtual Sandbox Bridge")

### How? (2) - Installation

The installation can be done automatically. 
Run the following command (as root) on the PVE Server:

If you have git installed on your Proxmox Server, you can run

```bash
git clone https://github.com/onemarcfifty/example.com-proxmox.git
```

If not, then you could download and unzip the repo by typing

```bash
wget https://github.com/onemarcfifty/example.com-proxmox/archive/refs/heads/main.zip
unzip main.zip
```

then cd into the subfolder, review and adapt the config file and launch
```bash
./deploy-sandbox.sh
```

### More Info

The whole process is described in [This video on my youtube channel](https://www.youtube.com/watch?v=jZjysgVk9wU)

example.com-proxmox

example.com-proxmox 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

example.com-proxmox

example.com-proxmox 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README