Push a new alpha version of fileglancer to PyPI, following the Fileglancer release steps.
Update the version in pixi.toml (in this repo) to point to the latest version of fileglancer.
Run the install, to update the pixi.lock file:
pixi install
Push all of these changes to GitHub.
Note: if Pixi cannot find the new package version on Pypi, you may need to clear your Pixi Pypi cache.
pixi clean cache --pypi
If this command fails to clear the cache, manually clear it using the directory it prints out. E.g.,
rm -r <path/to/.cache/rattler/cache/uv-cache>
SSH to the Fileglancer development server and update the fileglancer-hub code:
cd /opt/deploy/fileglancer-hub
git pull
Stop the services:
sudo systemctl stop fileglancer
Start fileglancer and check the logs to ensure it came up without errors:
sudo systemctl start fileglancer
sudo journalctl -u fileglancer -f
To test the full application stack prior to a production release, ensure the .env file in this repo contains the following:
FGC_TEST_API_KEY='<your-generated-key>'
If a FGC_TEST_API_KEY is not already configured, create a new one.
python -c "import secrets; print(secrets.token_urlsafe(32))"Add the generated key as the value for FCG_TEST_API_KEY in both the .env file for fileglancer-hub and the .env file in fileglancer-janelia/playwright. See the fileglancer-janelia repo for example Playwright tests and further documentation of this feature.
Push a new major, minor, or patch version of fileglancer to PyPI, following the Fileglancer release steps.
Announce a deployment in progress in the #fileglancer-support channel on Slack. Then repeat steps 2 and 3 above on the production server.