How to Set Up Oasis AI for Automated Browser-Based Earnings
# How to Set Up Oasis AI for Automated Browser-Based Earnings
This article details the server configuration required to run Oasis AI, a system designed for automated browser-based earnings. It assumes a basic understanding of Linux server administration and familiarity with command-line interfaces. This guide is intended for newcomers to our server infrastructure.
Introduction
Oasis AI utilizes a distributed network of servers to manage and execute browser automation tasks. These tasks generate earnings through various online platforms. Successful operation requires careful server configuration to ensure stability, performance, and security. This document provides a step-by-step guide to setting up the necessary infrastructure. Please review our Security Policy before proceeding.
Hardware Requirements
The hardware requirements for Oasis AI servers depend on the scale of operation. The following table outlines the minimum and recommended specifications. Consider Server Scalability when planning your deployment.
| Specification | Minimum | Recommended |
|---|---|---|
| CPU | Intel Xeon E3-1220 v3 or AMD Ryzen 3 1200 | Intel Xeon E5-2680 v4 or AMD Ryzen 7 2700X |
| RAM | 8 GB DDR4 | 16 GB DDR4 ECC |
| Storage | 256 GB SSD | 512 GB NVMe SSD |
| Network | 1 Gbps Ethernet | 10 Gbps Ethernet |
| Operating System | Ubuntu Server 20.04 LTS | Ubuntu Server 22.04 LTS |
It’s crucial to use SSDs for optimal performance. NVMe SSDs are *highly* recommended for faster task execution. Ensure your server has a stable and reliable internet connection. See Network Configuration for more details.
Software Installation and Configuration
This section details the software required and the configuration steps involved. We will be using Docker for containerization, simplifying deployment and management.
1. Docker Installation
Install Docker and Docker Compose. Follow the official Docker documentation for your operating system: [https://docs.docker.com/engine/install/](https://docs.docker.com/engine/install/). Verify the installation with `docker --version`.
2. Dependencies
Install necessary dependencies:
```bash sudo apt update sudo apt install -y python3 python3-pip git ```
3. Oasis AI Repository
Clone the Oasis AI repository from our internal Git server:
```bash git clone git@internal.oasisai.net:oasisai/core.git cd core ```
4. Configuration Files
Copy the example configuration file and customize it according to your environment.
```bash cp config.example.yml config.yml nano config.yml ```
Important parameters in `config.yml` include:
- `server_id`: A unique identifier for your server.
- `api_key`: Your API key for communication with the Oasis AI control panel. (Obtain this from API Key Management).
- `browser_count`: The number of browser instances to run.
- `proxy_settings`: Configure proxy settings as per Proxy Configuration.
- **Firewall:** Configure a firewall (e.g., `ufw`) to restrict access to necessary ports only. See Firewall Rules.
- **SSH Access:** Disable password authentication for SSH and use SSH keys instead.
- **Regular Updates:** Keep the operating system and all installed software up to date.
- **Intrusion Detection:** Consider installing an intrusion detection system (IDS) like Fail2Ban.
- **API Key Security:** Protect your API key and never share it with unauthorized personnel.
- Telegram: @powervps Servers at a discounted price
5. Docker Compose
Use Docker Compose to build and run the Oasis AI containers:
```bash docker-compose up -d ```
This command will download the necessary images and start the containers in detached mode.
Server Monitoring & Logging
Effective monitoring and logging are critical for maintaining a healthy Oasis AI infrastructure.
1. System Monitoring
Use tools like `top`, `htop`, and `vmstat` to monitor server resource usage. Consider installing a more comprehensive monitoring solution like Prometheus and Grafana for long-term data analysis.
2. Application Logging
Oasis AI logs all relevant events to standard output, which is captured by Docker. You can view the logs using:
```bash docker logs oasisai-core ```
Configure log rotation to prevent disk space exhaustion. See Log Management for details.
3. Alerting
Set up alerts based on critical metrics (CPU usage, memory usage, disk space, network traffic) to be notified of potential issues. Integrate alerting with our Incident Response Plan.
Security Considerations
Security is paramount. Implement the following measures:
Network Configuration Details
The following table details the necessary port configurations.
| Port | Protocol | Description |
|---|---|---|
| 22 | TCP | SSH Access (Restricted to authorized IPs) |
| 80/443 | TCP | Web Interface (if enabled – generally not recommended) |
| 5000 | TCP | Internal Communication (Between containers) |
| 9000 | TCP | API Endpoint |
Ensure that port 9000 is accessible from the Oasis AI control panel.
Troubleshooting
If you encounter issues, consult the Troubleshooting Guide or contact the support team via Support Channels. Common problems and solutions are documented in our Known Issues database.
Scaling the Infrastructure
To increase capacity, you can deploy additional Oasis AI servers. Ensure that each server has a unique `server_id` and is properly configured. The control panel will automatically distribute tasks across available servers. Refer to the Server Scaling document for advanced configuration options.
| Topic | Link |
|---|---|
| Security Policy | Security Policy |
| Server Scalability | Server Scalability |
| Network Configuration | Network Configuration |
| API Key Management | API Key Management |
| Proxy Configuration | Proxy Configuration |
| Prometheus | Prometheus |
| Grafana | Grafana |
| Log Management | Log Management |
| Incident Response Plan | Incident Response Plan |
| Firewall Rules | Firewall Rules |
| Fail2Ban | Fail2Ban |
| Troubleshooting Guide | Troubleshooting Guide |
| Support Channels | Support Channels |
| Known Issues | Known Issues |
| Server Scaling | Server Scaling |
Intel-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Core i7-6700K/7700 Server | 64 GB DDR4, NVMe SSD 2 x 512 GB | CPU Benchmark: 8046 |
| Core i7-8700 Server | 64 GB DDR4, NVMe SSD 2x1 TB | CPU Benchmark: 13124 |
| Core i9-9900K Server | 128 GB DDR4, NVMe SSD 2 x 1 TB | CPU Benchmark: 49969 |
| Core i9-13900 Server (64GB) | 64 GB RAM, 2x2 TB NVMe SSD | |
| Core i9-13900 Server (128GB) | 128 GB RAM, 2x2 TB NVMe SSD | |
| Core i5-13500 Server (64GB) | 64 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Server (128GB) | 128 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Workstation | 64 GB DDR5 RAM, 2 NVMe SSD, NVIDIA RTX 4000 |
AMD-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Ryzen 5 3600 Server | 64 GB RAM, 2x480 GB NVMe | CPU Benchmark: 17849 |
| Ryzen 7 7700 Server | 64 GB DDR5 RAM, 2x1 TB NVMe | CPU Benchmark: 35224 |
| Ryzen 9 5950X Server | 128 GB RAM, 2x4 TB NVMe | CPU Benchmark: 46045 |
| Ryzen 9 7950X Server | 128 GB DDR5 ECC, 2x2 TB NVMe | CPU Benchmark: 63561 |
| EPYC 7502P Server (128GB/1TB) | 128 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/2TB) | 128 GB RAM, 2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/4TB) | 128 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/1TB) | 256 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/4TB) | 256 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 9454P Server | 256 GB RAM, 2x2 TB NVMe |
Order Your Dedicated Server
Configure and order your ideal server configurationNeed Assistance?
⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️