Update
This page describes how to update Dotnify to the latest version, depending on your deployment method.
Docker
Pull the latest image and recreate the container:
Docker Hub:
docker pull airtouch97/dotnify:latest
docker compose up -dGHCR:
docker pull ghcr.io/airtouch97/dotnify:latest
docker compose up -dIf you're not using docker-compose:
docker pull airtouch97/dotnify:latest # or ghcr.io/airtouch97/dotnify:latest
docker stop dotnify
docker rm dotnify
docker run -d --name dotnify \
-p 3000:3000 \
-e UPSTASH_REDIS_REST_URL="https://your-redis.upstash.io" \
-e UPSTASH_REDIS_REST_TOKEN="your-redis-token" \
airtouch97/dotnify:latestData is stored in Upstash Redis and is not affected by container recreation.
Forked Repository
If you forked the Dotnify repository and deployed from your own fork:
- Sync your fork's
releasebranch with the upstream repository - Your deployment platform (Vercel / Railway / Zeabur) will automatically detect the push and redeploy
You can sync via the GitHub web interface, or run the following locally:
git remote add upstream https://github.com/airtouch97/Dotnify.git
git fetch upstream
git checkout release
git merge upstream/release
git push origin releaseCloned Repository (One-Click Deploy)
If you used the one-click deploy button (e.g., Vercel), a copy of the repository was created under your account — not a fork. It won't receive updates from the upstream repository automatically.
To update, use the Update to the latest version workflow included in the repository:
- Go to your repository on GitHub → Actions
- Select Update to the latest version in the workflow list on the left
- Click Run workflow → Run workflow
This workflow will sync your release branch with the upstream release branch and push the changes. Your deployment platform will then automatically redeploy.
Local / Production Server
If you deployed by cloning the repository and running it directly:
git pull origin release
npm install
npm run buildThen restart the server:
npm run start