Cloudron Forum

@LoudLemur You could do that. No problem. You can specify the mail server location to be any SUB and pick any of the domains you have set up in Cloudron. To make things even wackier, you could use multiple subdomains like sub.sub.domain.com as the mail server.

Thanks - we should probably create a wishlist post for Vidzy too https://vidzy.codeberg.page/

I updated invidious to 1.5 again to see if my problem came back, it did. restored to 1.4 and it works for "me."

This seems to be targeting the desktop flavor of Ubuntu 24.04. So this does not directly apply to Cloudron. For Cloudron, please follow https://docs.cloudron.io/guides/upgrade-ubuntu-24/

would be really great to have a beta package (alongside production) just for testing purposes👼

Maybe also an "Alternative to:" line ?

@LoudLemur I think for admin the TOTP has to be set in the ini file (https://github.com/the-djmaze/snappymail/issues/84#issuecomment-885181768) . For users, the 2FA extension is used.

The 2fa is shown in admin login page, all the time for me as well.

But if you can identify the bug, maybe you can report this upstream since 2FA auth comes from snappy and not from Cloudron.

ah interesting, I have never seen that message

@humptydumpty Let me suggest a great book to read: Co-Intelligence, by Ethan Mollick. I have read 70% of the book and am coming to the same opinion as the author: "invite AI to your work table all the time". Whether its writing an article, marketing study, presentation or report, it can help create the first draft (edit and polish it yourself). It can generate example code (fix, check and correct it yourself). I find AI helps when you are staring at a blank screen wondering where to start. It can generate many ideas, but it is best when you evaluate and refine them.

I also found the author presented some great examples of using "prompt engineering" and "personas" to get better results. But there are also subtle reminders in the book about training bias, how AI tries to generate answers that "please us humans", and its inherent limitations and why the same prompt will generate inconsistent responses. Like any tool, it needs to be wielded by a trained craftsman. It can help you get work done faster, but it can also help you get to the wrong answer very quickly.

Hi, micmc!

This is what Llama 3.1 405b has to say about the two:

"VoiceChat (lhl/voicechat2):

Features:

Local AI voice chat system
Uses WebSockets for communication
Fully local (voice-to-voice) implementation
Uses Whisper large-v2 (Q5) for speech recognition
Utilizes Llama 3 8B (Q4_K_M) for language processing
Employs tts_models/en/vctk/vits (Coqui TTS default VITS models) for text-to-speech
Pros:

Fast performance: Voice-to-voice latency is in the 1-second range on high-end GPUs
Fully local: Doesn't require internet connection for core functionality
Open-source: Available on GitHub for customization and community contributions
Utilizes state-of-the-art AI models for speech recognition and language processing
Cons:

Requires powerful hardware: Optimal performance seems to be on high-end GPUs (e.g., AMD RDNA3 card)
May have limited features compared to more established voice chat solutions
Potentially complex setup for non-technical users
Limited documentation available
OpenWebUI:

Features:

Web-based user interface for AI interactions
Docker and Kubernetes support for easy deployment
Integration with OpenAI-compatible APIs
Customizable OpenAI API URL
Support for both Ollama and CUDA-tagged images
Functions and pipeline support for extended capabilities
Pros:

Effortless setup using Docker or Kubernetes
Flexible API integration (OpenAI, LMStudio, GroqCloud, Mistral, etc.)
Web-based interface for easy access
Extensible with functions and pipelines
Active development and community support
Supports multiple deployment options (pip, Docker, Kubernetes)
Cons:

Documentation may be lacking in some areas, making integration challenging
Primarily focused on text-based interactions, unlike VoiceChat's voice-to-voice approach
May require more setup for voice capabilities (if needed)
Potential learning curve for utilizing all features and integrations
Comparison:

Focus:

VoiceChat is specifically designed for voice-to-voice AI interactions.
OpenWebUI is a more general-purpose web interface for AI interactions, primarily text-based.
Deployment:

VoiceChat seems to require local installation and configuration.
OpenWebUI offers multiple deployment options, including Docker and Kubernetes, making it potentially easier to set up and scale.
Flexibility:

VoiceChat is focused on local, offline use with specific AI models.
OpenWebUI offers more flexibility in terms of API integrations and customization options.
User Interface:

VoiceChat likely has a minimal interface focused on voice interactions.
OpenWebUI provides a web-based interface that can be accessed from various devices.
Community and Development:

Both are open-source, but OpenWebUI appears to have more active development and a larger community.
Use Case:

VoiceChat is ideal for users needing offline, voice-based AI interactions with low latency.
OpenWebUI is better suited for users who need a flexible, web-based interface for various AI interactions and integrations.
In conclusion, the choice between VoiceChat and OpenWebUI depends on the specific needs of the user. VoiceChat is more specialized for voice-based AI interactions, while OpenWebUI offers a more versatile platform for general AI interactions with easier deployment options. Users prioritizing voice capabilities and offline use might prefer VoiceChat, while those needing a flexible, web-based solution with various integrations might find OpenWebUI more suitable."

@taowang I don't get it, why should we add Searchxng folder in here?and also which config that you mean to put in the Searchxng folder?

@pHneutre the best solution at present is to change your update schedule to be every hour https://docs.cloudron.io/updates/#update-schedule then it'll do one an hour until it's done.

svtx, thank you. I know this thread, but not the way configuring ipv6-rotating or understand how to include the vpn-way from LoudLemur mentioned in https://docs.invidious.io/gluetun/ inside cloudron. The idea should be realized on a standalone invidious server.