Skip to content

Comments

Automatic Docker-Image building#41

Closed
neooriginal wants to merge 3 commits intoSimpleOpenSoftware:mainfrom
neooriginal:main
Closed

Automatic Docker-Image building#41
neooriginal wants to merge 3 commits intoSimpleOpenSoftware:mainfrom
neooriginal:main

Conversation

@neooriginal
Copy link
Contributor

This pull request introduces significant updates to the advanced-backend project, including a new Docker-based CI/CD workflow, a simplified README, and enhanced configuration management for the backend services. The changes aim to streamline deployment, improve maintainability, and provide better flexibility for environment-specific configurations.

CI/CD Workflow Enhancements:

  • .github/workflows/docker-build.yml: Added a GitHub Actions workflow to build and push Docker images for the backend and web UI on main and develop branches, pull requests, and manual triggers. Includes metadata extraction, caching, and multi-platform support.

Documentation Updates:

  • backends/advanced-backend/README.md: Replaced detailed backend setup and architecture documentation with a link to a QuickStart guide hosted in the repository. Simplifies onboarding for new developers.

Configuration Improvements:

  • backends/advanced-backend/docker-compose.yml: Updated environment variables for backend services to use defaults and added new configuration options for audio processing, authentication, transcription providers, LLM providers, and memory services. Improves flexibility and readability. [1] [2]
  • docker-compose.yml: Added a top-level docker-compose.yml file defining core services (friend-backend, streamlit, qdrant, mongo) and optional services (e.g., neo4j, ollama, nginx). Includes health checks, restart policies, and resource management.

@neooriginal
Copy link
Contributor Author

neooriginal commented Jul 21, 2025

Build fails due to missing access i believe

Copy link
Collaborator

@AnkushMalaker AnkushMalaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The compose changes itself look okay, just not sure about placement of the file

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would prefer not having one random docker-compose.yml outside while each directory has its own compose file/docker setup. Any specific reason this has to be here?

@AnkushMalaker
Copy link
Collaborator

Hey @neooriginal
I think we already have this now, would it be okay to close this?

@neooriginal
Copy link
Contributor Author

For sure!

@neooriginal neooriginal closed this Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants