Docker: Streama not using MySQL
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
Research direction
Start by reviewing the provided docker-compose.yml and the Streama container's ACTIVE_PROFILE and MYSQL_* environment settings, then inspect startup logs for database connection or schema-creation errors. Done means Streama connects to MySQL, creates its tables, and retains data after a container restart.
Written by the indexing model from the issue text.
Description
Issue description
Streama isn´t using mysql
Steps to Reproduce
- Create docker-compose.yml with mysql and streama
- docker-compose up -d
- Open Streama in Chrome/Firefox
Expected Behaviour
Stream should connect to MySQL and create tables
Actual Behaviour
Streama is accessible, but does not use the database.
After each restart, all data is gone
Environment Information
- Operating System: Ubuntu 19.10
- Streama version: v1.8.2
- Container Version (If Applicable): gkiko/streama:latest
docker-compose.yml
` streama:
image: gkiko/streama:latest
depends_on:
- mysql
restart: always
networks:
- webserver
volumes:
- ./streama:/data
environment:
ACTIVE_PROFILE: mysql
MYSQL_HOST: mysql
MYSQL_PORT: 3306
MYSQL_DB: DB
MYSQL_USER: DB_User
MYSQL_PASSWORD: AGoodPassword
labels:
- 'traefik.enable=true'
- 'traefik.frontend.rule=Host:streama.domain.tld' `
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 978
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from streamaserver/streama
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
streamaserver/streama#1164 ·
-
API calls Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
streamaserver/streama#1162 · 10 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1161 ·
-
Java issue Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1160 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1157 · 1 comment ·
All issues in streamaserver/streama
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100