English
Moodist Hosting
Moodist is a self-hosted ambient-sound board: layered noises, timers, and focus tools that play in the visitor's browser.
- One click deploy
- 15 GB Disk Space Needed
- 1 GB RAM Memory needed
- From 2 € Price
No setup fees
Official links
Moodist’s official links and original website
- Go to Repository
Moodist GitHub
- More
Moodist Website
What you get
on AvaHost
One-click deployment, a custom domain, free HTTPS, automatic application updates, and scheduled backups come with every Cloud App. You can run multiple apps on one server, and terminal access is included.
This template does not include a database container.
Tech
- Docker image
- ghcr.io/remvze/moodist:latest
- Default port
- 0
How Moodist works
Moodist, by remvze, is an ambient-sound mixer. The README lists layered noises, presets, a sleep timer, binaural and isochronic tones, a breathing exercise, a Pomodoro timer, and a small notepad. The site is a static build served by the container ghcr.io/remvze/moodist on port 8080. Playback happens in the visitor's browser. The server sends files and then sits idle. There is no login and no database. Presets and mixes are a browser concern, including shareable URLs, not rows in a server table.
Some sounds are under the Pixabay Content License or CC0, which the README separates from the code's MIT licence. Hosting the image does not rewrite those asset terms. You are serving the project's build, not commissioning a new sample library.
Key Moodist features
Visitors stack sounds, save a mix in the browser, and can install the PWA so later visits work from cache. There is nothing to back up except the decision to keep the container running, because you do not accumulate user data. That also means you cannot recover someone's unsynced preset from the server. Tell people that before they treat it as a cloud notebook.
AvaHost updates the image automatically. Scheduled backups have little to store beyond the deployment itself. A dedicated public IP is not required for Moodist. Application mail is not included, and the app does not send mail. Automated HTTPS is for the page, not for a user session that does not exist.
Moodist vs myNoise
Moodist
Moodist is a board you serve, with a fixed set of sounds from the project. myNoise is a hosted generator with its own catalogue and sliders, operated by that site. Choose myNoise when you want that catalogue and you are fine opening their website. Choose Moodist when the requirement is a copy on your hostname and the feature list in the README is enough.
myNoise
Neither one is a music library, a radio station, or a therapy device. Do not describe them as medical tools.
Who uses Moodist
Offices and individuals who want a focus page on a URL they control use Moodist. It is a poor fit if you need per-user accounts, uploaded audio, or a server-side history of mixes. Those features are not in this build.
Self-hosting Moodist: requirements and cost
The baseline is 256 MB of RAM and a quarter of a CPU core, image ghcr.io/remvze/moodist, no database. On AvaHost the recommended minimum for Moodist is Plan 1 at €2. The package includes one-click deployment, a hostname, automated HTTPS, automatic updates, and scheduled backups of the deployment. Disk stays small because the sounds ship in the image and visitors do not upload. There is no dedicated IP requirement.
F.A.Q
Moodist starts at €2 on Plan 1. The app is a static board, so the minimum is enough for ordinary traffic. You are not paying for per-user storage, because the server does not keep accounts. A very large internal audience still only downloads files. There is no add-on database in this price.
Yes. Point a hostname at the instance and automated HTTPS covers the page. Anyone who can open that URL can use the mixer, because there is no login. If the board should stay private, limit who can reach the hostname at the network layer. DNS remains yours.
Almost none. AvaHost updates Moodist automatically and can snapshot the deployment on a schedule, but mixes live in the visitor’s browser. A server restore will not bring back a preset that was not sent to you. After an update, open the page and play one sound to confirm the assets still load.
Accounts, uploaded audio, and a server-side history. The README’s tools run in the browser. Sound licences are not all the same as the code licence, which the project states in its third-party section. This package does not add a database and does not need a dedicated IP.