You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Renamed to vinted-bot (from vinted-sniper), the name people search for. Everything
uses it now: the vinted-bot command, the PyPI package vinted-bot, the Docker image ghcr.io/jasp-nerd/vinted-bot, the repository github.com/jasp-nerd/vinted-bot (old links
redirect), the website vinted-bot.jaspnerd.dev, settings (VINTED_BOT_...), the data folder
(vinted-bot), the installers' start-at-login entries, the Docker volume
(vinted-bot-data), the default Discord name and the webhook headers
(X-Vinted-Bot-Signature, X-Vinted-Bot-Timestamp). The old names are not read any more,
so this is a fresh install: install vinted-bot with the commands in the README, uninstall
the old copy, and rename any settings in your .env. To keep your searches, copy the old
data folder's app.db into the new one before the first start.
The installers' start-at-login entries now tell the app they restart it
(VINTED_BOT_SUPERVISED), and the Windows launcher stays running in the background so it
can install an update while the app is closed.
Added
Update from the dashboard. Where the installer set vinted-bot up to start by itself,
"Update now" installs the new version and restarts into it, and "Install updates by
itself" (off unless you turn it on) does that between 4 and 5 at night, never while an
alert is on its way out, then says so in your status alerts. Installed with uv or pipx but
started by hand, the button installs it and tells you how to restart. Docker and source
installs are shown the command to run. Updates only ever come from PyPI through uv or
pipx, and only when GitHub has a newer release; a failed update leaves the running version
alone and says what went wrong.
Removed
The empty web extra, kept in 2.0 only so 1.x install commands still worked. The
dashboard is part of every install.