Update Bitcoin Pulse input to GitHub
This commit is contained in:
parent
1bdf25bf06
commit
ff560ea84c
5 changed files with 13 additions and 13 deletions
|
|
@ -109,7 +109,7 @@ git diff -- flake.lock
|
|||
nix flake check --no-build
|
||||
```
|
||||
|
||||
Confirm that `flake.lock` points to the intended reviewed BitcoinPulseAPI
|
||||
Confirm that `flake.lock` points to the intended reviewed BitcoinPulse
|
||||
revision. Commit and push the lock-file update, follow the standard deployment,
|
||||
and perform all post-deployment checks. The switch runs the packaged version's
|
||||
pending migrations before starting that backend version.
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@ creates:
|
|||
- `bitcoin_pulse_migration`, a non-superuser login that owns the database;
|
||||
- `bitcoin_pulse_app`, a non-superuser login with `CONNECT` only initially.
|
||||
|
||||
The role bootstrap SQL comes from the pinned BitcoinPulseAPI flake input.
|
||||
The role bootstrap SQL comes from the pinned BitcoinPulse flake input.
|
||||
Migratus' database-foundation migration then grants the application role schema
|
||||
usage and default DML privileges for application objects. Later migrations can
|
||||
further restrict individual tables; the application role cannot create schema
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue