Auto-GPT/autogpt_platform
Zamil Majdy ea01c8038b
fix(frontend): Fix broken block UI layout (#9132)
https://github.com/Significant-Gravitas/AutoGPT/pull/9097/files#diff-ef176e50a6a65af5df2182626ea868ce77b76de447c816fb4f80fb4d376c3049R7-R41
introduced styling changes to block UI layout which causes the block
layout broken:


![image](https://github.com/user-attachments/assets/0d3d6e61-1acc-440c-9c7b-8cc473b457ea)

This PR minimally reverts the styling change.

### Changes 🏗️

Minimal CSS revert to make the block UI layout back to normal.

### Checklist 📋

#### For code changes:
- [ ] I have clearly listed my changes in the PR description
- [ ] I have made a test plan
- [ ] I have tested my changes according to the test plan:
  <!-- Put your test plan here: -->
  - [ ] ...

<details>
  <summary>Example test plan</summary>
  
  - [ ] Create from scratch and execute an agent with at least 3 blocks
- [ ] Import an agent from file upload, and confirm it executes
correctly
  - [ ] Upload agent to marketplace
- [ ] Import an agent from marketplace and confirm it executes correctly
  - [ ] Edit an agent from monitor, and confirm it executes correctly
</details>

#### For configuration changes:
- [ ] `.env.example` is updated or already compatible with my changes
- [ ] `docker-compose.yml` is updated or already compatible with my
changes
- [ ] I have included a list of my configuration changes in the PR
description (under **Changes**)

<details>
  <summary>Examples of configuration changes</summary>

  - Changing ports
  - Adding new services that need to communicate with each other
  - Secrets or environment variable changes
  - New or infrastructure changes such as databases
</details>
2024-12-31 09:13:47 +01:00
..
autogpt_libs fix(backend): Added locking status check before releasing to avoid releasing timing out lock (#9135) 2024-12-31 08:48:04 +01:00
backend fix(backend): Added locking status check before releasing to avoid releasing timing out lock (#9135) 2024-12-31 08:48:04 +01:00
frontend fix(frontend): Fix broken block UI layout (#9132) 2024-12-31 09:13:47 +01:00
graph_templates chore(platform): Tidy up repo structure (#8521) 2024-11-01 15:33:26 +00:00
market Update dependencies 2024-12-17 11:07:13 +01:00
supabase@4647d50380 refactor: AutoGPT Platform Stealth Launch Repo Re-Org (#8113) 2024-09-20 16:50:43 +02:00
__init__.py refactor: AutoGPT Platform Stealth Launch Repo Re-Org (#8113) 2024-09-20 16:50:43 +02:00
.gitignore feat(platform): Added .gitignore to platform root dir 2024-11-05 16:32:48 +01:00
Contributor License Agreement (CLA).md Add files via upload 2024-09-24 23:11:57 +01:00
docker-compose.platform.yml fix(backend): Spin-up Database manager on rest.py (#8832) 2024-11-27 16:39:08 +00:00
docker-compose.yml feat(backend): Reduce number of services on the local mode (#8563) 2024-11-05 22:36:51 +07:00
LICENCE.txt Add files via upload 2024-09-24 23:11:57 +01:00
README.md docs(platform): correct readme 2024-11-01 09:13:25 +00:00

AutoGPT Platform

Welcome to the AutoGPT Platform - a powerful system for creating and running AI agents to solve business problems. This platform enables you to harness the power of artificial intelligence to automate tasks, analyze data, and generate insights for your organization.

Getting Started

Prerequisites

  • Docker
  • Docker Compose V2 (comes with Docker Desktop, or can be installed separately)
  • Node.js & NPM (for running the frontend application)

Running the System

To run the AutoGPT Platform, follow these steps:

  1. Clone this repository to your local machine and navigate to the autogpt_platform directory within the repository:

    git clone <https://github.com/Significant-Gravitas/AutoGPT.git | git@github.com:Significant-Gravitas/AutoGPT.git>
    cd AutoGPT/autogpt_platform
    
  2. Run the following command:

    git submodule update --init --recursive
    

    This command will initialize and update the submodules in the repository. The supabase folder will be cloned to the root directory.

  3. Run the following command:

    cp supabase/docker/.env.example .env
    

    This command will copy the .env.example file to .env in the supabase/docker directory. You can modify the .env file to add your own environment variables.

  4. Run the following command:

    docker compose up -d
    

    This command will start all the necessary backend services defined in the docker-compose.yml file in detached mode.

  5. Navigate to frontend within the autogpt_platform directory:

    cd frontend
    

    You will need to run your frontend application separately on your local machine.

  6. Run the following command:

    cp .env.example .env.local
    

    This command will copy the .env.example file to .env.local in the frontend directory. You can modify the .env.local within this folder to add your own environment variables for the frontend application.

  7. Run the following command:

    npm install
    npm run dev
    

    This command will install the necessary dependencies and start the frontend application in development mode. If you are using Yarn, you can run the following commands instead:

    yarn install && yarn dev
    
  8. Open your browser and navigate to http://localhost:3000 to access the AutoGPT Platform frontend.

Docker Compose Commands

Here are some useful Docker Compose commands for managing your AutoGPT Platform:

  • docker compose up -d: Start the services in detached mode.
  • docker compose stop: Stop the running services without removing them.
  • docker compose rm: Remove stopped service containers.
  • docker compose build: Build or rebuild services.
  • docker compose down: Stop and remove containers, networks, and volumes.
  • docker compose watch: Watch for changes in your services and automatically update them.

Sample Scenarios

Here are some common scenarios where you might use multiple Docker Compose commands:

  1. Updating and restarting a specific service:

    docker compose build api_srv
    docker compose up -d --no-deps api_srv
    

    This rebuilds the api_srv service and restarts it without affecting other services.

  2. Viewing logs for troubleshooting:

    docker compose logs -f api_srv ws_srv
    

    This shows and follows the logs for both api_srv and ws_srv services.

  3. Scaling a service for increased load:

    docker compose up -d --scale executor=3
    

    This scales the executor service to 3 instances to handle increased load.

  4. Stopping the entire system for maintenance:

    docker compose stop
    docker compose rm -f
    docker compose pull
    docker compose up -d
    

    This stops all services, removes containers, pulls the latest images, and restarts the system.

  5. Developing with live updates:

    docker compose watch
    

    This watches for changes in your code and automatically updates the relevant services.

  6. Checking the status of services:

    docker compose ps
    

    This shows the current status of all services defined in your docker-compose.yml file.

These scenarios demonstrate how to use Docker Compose commands in combination to manage your AutoGPT Platform effectively.

Persisting Data

To persist data for PostgreSQL and Redis, you can modify the docker-compose.yml file to add volumes. Here's how:

  1. Open the docker-compose.yml file in a text editor.

  2. Add volume configurations for PostgreSQL and Redis services:

    services:
      postgres:
        # ... other configurations ...
        volumes:
          - postgres_data:/var/lib/postgresql/data
    
      redis:
        # ... other configurations ...
        volumes:
          - redis_data:/data
    
    volumes:
      postgres_data:
      redis_data:
    
  3. Save the file and run docker compose up -d to apply the changes.

This configuration will create named volumes for PostgreSQL and Redis, ensuring that your data persists across container restarts.