User Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
services:audiomuseai [2025/10/15 07:03] – [AudioMuse-AI] willyservices:audiomuseai [2025/10/15 11:57] (current) – willy
Line 12: Line 12:
 <code bash> <code bash>
 bash ~ # lscpu  | grep -i avx bash ~ # lscpu  | grep -i avx
-Flags:                                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabilities+Flags:     fpu [...] avx [..] avx2 [...] arch_capabilities
 </code> </code>
  
 As you can see, my CPU supports AVX and AVX2. As you can see, my CPU supports AVX and AVX2.
  
-Then create the usual dedicated user:+Then create the usual dedicated user and data folders for persistency:
 <code bash> <code bash>
 useradd -m -d /data/daemons/audiomuse-ai audiomuse-ai useradd -m -d /data/daemons/audiomuse-ai audiomuse-ai
 +mkdir /data/audiomuse
 +mkdir /data/audiomuse/temp_audio
 +mkdir /data/audiomuse/postgres_data
 +chown -R audiomuse-ai:audiomuse-ai /data/audiomuse
 </code> </code>
  
Line 34: Line 38:
         - "8925:8000"         - "8925:8000"
     volumes:     volumes:
-      - /data/daemons/audiomuse-ai/temp_audio:/app/temp_audio+      - /data/audiomuse/temp_audio:/app/temp_audio
     environment:     environment:
         MEDIASERVER_TYPE: "navidrome"         MEDIASERVER_TYPE: "navidrome"
Line 60: Line 64:
 #        - "8925:8000" #        - "8925:8000"
     volumes:     volumes:
-      - /data/daemons/audiomuse-ai/temp_audio:/app/temp_audio+      - /data/audiomuse/temp_audio:/app/temp_audio
     environment:     environment:
         MEDIASERVER_TYPE: "navidrome"         MEDIASERVER_TYPE: "navidrome"
Line 86: Line 90:
     image: postgres:15-alpine     image: postgres:15-alpine
     volumes:     volumes:
-      - /data/daemons/audiomuse-ai/postgres_data:/var/lib/postgresql/data+      - /data/audiomuse/postgres_data:/var/lib/postgresql/data
     environment:     environment:
         SERVICE_TYPE: "flask"         SERVICE_TYPE: "flask"
Line 104: Line 108:
     image: redis:7-alpine     image: redis:7-alpine
     volumes:     volumes:
-      - /data/daemons/audiomuse-ai/postgres_data:/var/lib/postgresql/data+      - /data/audiomuse/postgres_data:/var/lib/postgresql/data
     environment:     environment:
         SERVICE_TYPE: "flask"         SERVICE_TYPE: "flask"
Line 124: Line 128:
  
 Of course, you need to specify your Navidrome URL, user and password. The GEMINI key is not required, only if you want AI assisted playlist naming. You could also use a self-hosted OLLAMA. Of course, you need to specify your Navidrome URL, user and password. The GEMINI key is not required, only if you want AI assisted playlist naming. You could also use a self-hosted OLLAMA.
 +
 +===== Gemini AI usage =====
 +
 +If you want to use the capability to create playlists names using AI, you can use Gemini (and others too). Go to [[https://aistudio.google.com/app/apikey|Google AI studio page]], create a new API key and project, and copy the key itself into the relevant line in the above Docker Compose file.
 +
  
 ===== Reverse Proxy ===== ===== Reverse Proxy =====