Before we can start deploying on a new server, we need to wrap it all up in a Nix flake.
The current package expressions were moved mostly as-is to package.nix. We need the shell expression to contain a fresh nixUnstable and the deploy-rs executable, along with anything else you want for development.
The new server sadalbari.pegasus.serokell.team is not yet deployed, infra PR soonhttps://github.com/serokell/pegasus-infra/pull/2. This will be the canonical server name, and the public DNS name a CNAME to it.
Stable nix should be able to work as expected thanks to the flake-compat wrappers in default.nix and shell.nix. Please do test them to make sure I didn't break your development environment.
This PR also moves the CI build steps to a local .buildkite/pipeline.yml file. I've already modified the pipeline on BK to read this file from the repo. This is a breaking change. Branches that do not have this file will not have CI until this branch is merged.
Before we can start deploying on a new server, we need to wrap it all up in a Nix flake.
The current package expressions were moved mostly as-is to
package.nix. We need the shell expression to contain a freshnixUnstableand thedeploy-rsexecutable, along with anything else you want for development.The new server
sadalbari.pegasus.serokell.teamis not yet deployed, infra PRsoonhttps://github.com/serokell/pegasus-infra/pull/2. This will be the canonical server name, and the public DNS name a CNAME to it.Stable nix should be able to work as expected thanks to the
flake-compatwrappers indefault.nixandshell.nix. Please do test them to make sure I didn't break your development environment.This PR also moves the CI build steps to a local
.buildkite/pipeline.ymlfile. I've already modified the pipeline on BK to read this file from the repo. This is a breaking change. Branches that do not have this file will not have CI until this branch is merged.