Version bumb to 2.2.1 and added migrate command

[xsteadfastx]

made the changes to get 2.2.1 running plus added a migrate command to
the entrypoint. documented it in the readme.

[opsydev]

Hey, I just tested this build with an existing install and it worked like a charm.

My setup:

Wallabag on docker
PostgreSQL on a separate machine (not containerized)

PS: I am super interested in seeing this merge as I want to use the Pinboard import feature in 2.2.0 :)

[nicosomb]

It seems OK but I didn't try your image.

[j0k3r]

LGTM

[xsteadfastx]

Yeah good news 😁 Am 1. Februar 2017 05:16:42 MEZ schrieb opsydev <notifications@github.com>:

…

Hey, I just tested this build with an existing install and it worked like a charm. My setup: Wallabag on docker PostgreSQL on a separate machine (not containerized) -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #48 (comment)

[bobberb]

@xsteadfastx I'm running your branch version-2.2.1 and cannot log in anymore.

Wallabag is provided the same/correct login info but login screen flashes

run command is

docker run --name wallabag-2.2.1r --link redis:redis -p 8885:80 -v /selfhosted/wallabag:/var/www/wallabag/data --restart=always -e "SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql" -e "SYMFONY__ENV__DATABASE_HOST=172.17.0.1" -e "SYMFONY__ENV__DATABASE_PORT=3306" -e "SYMFONY__ENV__DATABASE_NAME=wallabag" -e "SYMFONY__ENV__DATABASE_USER=wally" -e "SYMFONY__ENV__DATABASE_PASSWORD=wally" -e "MYSQL_ROOT_PASSWORD=PASSWORD" josh/wallabag:2.2.1

just as I have with 2.1.5, however, log in screen flashes with no error outputting in the shell itself without -d

[xsteadfastx]

@bobberb did you migrate your database? thats important...

docker run --name wallabag-2.2.1r --link redis:redis -p 8885:80 -v /selfhosted/wallabag:/var/www/wallabag/data --restart=always -e "SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql" -e "SYMFONY__ENV__DATABASE_HOST=172.17.0.1" -e "SYMFONY__ENV__DATABASE_PORT=3306" -e "SYMFONY__ENV__DATABASE_NAME=wallabag" -e "SYMFONY__ENV__DATABASE_USER=wally" -e "SYMFONY__ENV__DATABASE_PASSWORD=wally" -e "MYSQL_ROOT_PASSWORD=PASSWORD" josh/wallabag:2.2.1 migrate

should do it. if the image is built from that branch.

[bobberb]

Doh! I didn't realize 2.1 --> 2.2 needed a migration! So quick to run the image :)

…

On Wed, Feb 1, 2017, 4:47 AM xsteadfastx ***@***.***> wrote: @bobberb <https://github.com/bobberb> did you migrate your database? thats important... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABzd_JJW3CitZ90Qkfsh4w-T7V9kueF7ks5rYFSwgaJpZM4Lyymu> .

[bobberb]

@xsteadfastx I definitely blew up the original database despite a clone and using the paramater -e"...DATABASE=wallabag22".

I wonder if I baked the original in to my image somewhere else. What is stored in the db, usernames only?

[xsteadfastx]

@bobberb what original? migration doesnt work? you need the same parameters and put a migrate as command.

[bobberb]

before I ran your command I did a quick clone of db nammed wallabag to wallabag2 and subbed that in to the command. It definitely migrated successfully but I went back to test my original image and it's borked.

In the middle of a restore.

Maybe I should stick with sqlite :(

[tcitworld]

We plan to drop SQLite. :/