« barbie girl » du groupe aqua. je mets pas de lien, on me tuerait
The main URL points to this:
MusicBrainz' Picard app could start that, in a huge batch. But it would still require a bunch of eyeballing. I only do an album at a time, now and then.
(i own this in digital format, we are not the same)
no idea. impossible to rule out. there's no good answer to 'why' that i've seen
strangest thing. i updated firefox and now i have no notifications. only a limited number of sites have notification perms; they still say they have that permission and my system settings still have firefox allowed. i have another machine running ubuntu (with firefox from the PPA for apt) and notifications are unchanged there.
Prerequisites
- Internet-facing web server with reverse proxy and domain name (preferably SSL of course)
- Server behind the reverse proxy with Rust environment
Installation
- Don't bother downloading the source code to your server; installing it that way gives you a big debug executable
- Instead just
cargo install mollysocket - Move the
mollysocketexecutable if desired - Run
mollysocketonce so that it will emit the default config
Configuration
- Fish the config file out of
.config/mollysocket/default-config.tomland copy it somewhere.
config.toml
- In the new file, replace the
allowed_endpointsline withallowed_endpoints = ['*']. The default 0.0.0.0 config appears to be a bug; this setting controls access to endpoints within the app, not IPs from outside. Leaving the original value causes mollysocket to reject everything. - Put a proper path in the
db = './mollysocket.db'line rather than just having it land wherever you're sitting. - Delete the
mollysocket.dbthat was created on first run (even if it's already where you're intending to put it). This is just to make sure the web server creates it and has the correct permissions.
Run script
- The environment variable ROCKET_PORT must be set or the server will sit and do nothing. It's best to create all of the environment variables mentioned in the README, whether that is in a user profile script or in a shell script that wraps startup. You can change any of these values, but they must exist.
-
export ROCKET_PORT=8020 export RUST_LOG=info export MOLLY_CONF=/path/to/your/config.toml
Proxy server
- You'll need to proxy everything from
/to your mollysocket server and ROCKET_PORT. - Exclude anything that you may need served from your web server, such as .well-known.
Things to know
- I get this warning on startup: "Forced shutdown is disabled. Runtime settings may be suboptimal."
- I also can't stop my server with any sane signal; only SIGKILL brings it down.
- Some discussion here: https://github.com/SergioBenitez/Rocket/discussions/1880
you probably already found this, but for others who might be curious:
in the settings if you change notification method from websocket to unified push, the UP settings come up, including a server address (which is what they intend to be used) or some air gap mode that i can't find documented
thank you. sounds like i get the official working, or nothing at all.
ooooh, give you up
h/t @cmconseils@mastodon.social
they're trying to save time, so i had always wished for something that would waste their time. like a bollard that popped up and stayed up until the next bus came. money matters, but it does indeed matter differently by how much you have. these are misbehaving dogs. the corrective is best served up right at the point of infraction, and by taking away the advantage they were trying to get