2016-02-17 00:48:42 +08:00
|
|
|
# Workflow
|
|
|
|
|
|
|
|
... (branching/merging flow)
|
|
|
|
|
2016-02-16 01:29:43 +08:00
|
|
|
# Deployment
|
|
|
|
|
|
|
|
...
|
|
|
|
|
2016-02-19 18:57:13 +08:00
|
|
|
Deployment to db servers: the next command will install both the Python
|
|
|
|
package and the extension.
|
2016-02-16 01:29:43 +08:00
|
|
|
|
|
|
|
```
|
2016-02-19 18:57:13 +08:00
|
|
|
sudo make install
|
2016-02-16 01:29:43 +08:00
|
|
|
```
|
|
|
|
|
2016-02-19 17:48:50 +08:00
|
|
|
Installing only the Python package:
|
|
|
|
|
|
|
|
```
|
|
|
|
sudo pip install python/crankshaft --upgrade
|
|
|
|
```
|
|
|
|
|
2016-02-18 18:07:49 +08:00
|
|
|
Caveat: note that `pip install ./crankshaft` will install
|
|
|
|
from local files, but `pip install crankshaft` will not.
|
|
|
|
|
2016-02-19 18:57:13 +08:00
|
|
|
CI: Install and run the tests on the installed extension and package:
|
|
|
|
|
|
|
|
```
|
|
|
|
(sudo make install && PGUSER=postgres make testinstalled)
|
|
|
|
```
|
|
|
|
|
2016-02-16 01:29:43 +08:00
|
|
|
Installing the extension in user databases:
|
2016-02-19 18:57:13 +08:00
|
|
|
Once installed in a server, the extension can be added
|
|
|
|
to a database with the next SQL command:
|
2016-02-16 01:29:43 +08:00
|
|
|
|
2016-02-19 18:57:13 +08:00
|
|
|
```
|
|
|
|
CREATE EXTENSION crankshaft;
|
|
|
|
```
|
|
|
|
|
|
|
|
To upgrade the extension to an specific version X.Y.Z:
|
|
|
|
|
|
|
|
```
|
|
|
|
ALTER EXTENSION crankshaft UPGRADE TO 'X.Y.Z';
|
|
|
|
```
|