better migration handling

This commit is contained in:
nek0 2015-09-28 19:58:49 +02:00
parent 5f4dcb2867
commit 0fb2e2908e
2 changed files with 14 additions and 19 deletions

View file

@ -44,7 +44,7 @@ After installing all dependencies you can configure and build the software with
```bash
cabal configure
cabal build exe:eidolon
cabal build
```
##Deploying
@ -70,9 +70,10 @@ Since eidolon will block your console, I recommend wrapping a init-script around
###0.0.3-0.0.4
* do not start or restart your eidolon service before migration
* build the Migration script with `cabal build Migration1`
* Migration script is located in `dist/build/Migration1/` in your build directory
* run migration script from your run location (where your `static` folder with all the images are located)
* run migration script from your run location (where your `static` folder with all the images is located)
* if you are building in a sandbox run `runghc -package-db/full/path/to/sandbox/XXX-ghc-version-packages.conf.d /path/to/eidolon/Migrations/0.0.3-0.0.4/Migration.hs`
* Note: No space between the option `-package-db` and its argument
* without sandbox: `runghc /path/to/eidolon/Migrations/0.0.3-0.0.4/Migration.hs`
* start or restart your eidolon service
##Acknowledgements:

View file

@ -113,10 +113,18 @@ library
, blaze-markup >= 0.7
, wai >= 3.0
, yesod-newsfeed >= 1.4
-- for Migrations
, HDBC
, HDBC-postgresql
, imagemagick
, text
, filepath
, system-filepath
, bytestring
executable eidolon
if flag(library-only)
Buildable: True
Buildable: False
main-is: main.hs
hs-source-dirs: app
@ -126,20 +134,6 @@ executable eidolon
ghc-options: -threaded -O2
executable Migrate1
main-is: Migration.hs
hs-source-dirs: Migrations/0.0.3-0.0.4
ghc-options: -Wall
build-depends: base
, HDBC
, HDBC-postgresql
, imagemagick
, text
, filepath
, system-filepath
, bytestring
test-suite test
type: exitcode-stdio-1.0
main-is: main.hs