go-saloon / saloon-legacy

A place to chat and communicate: a buffalo forum
BSD 3-Clause "New" or "Revised" License
85 stars 8 forks source link

pop support moved error when creating db #34

Open soypat opened 4 years ago

soypat commented 4 years ago
ERRO[0001] Pop support has been moved to the https://github.com/gobuffalo/buffalo-pop plugin.

!! PLEASE READ PLUGIN DOCUMENTATION - https://gobuffalo.io/en/docs/plugins

Buffalo Plugins Installation*:

        $ buffalo plugins install github.com/gobuffalo/buffalo-pop

Steps to fix?

sbinet commented 4 years ago

thanks for the report.

I tried a bit to upgrade buffalo+pop but, as you can see, this repo has been left alone for far too long and the amount of work to apply a proper version upgrade far exceeds the amount of time I can dedicate to this.

feel free to give it a try (but upgrading for 2yrs of bitrot won't be pretty). (otherwise, I'll probably mention this is abandonware + freeze the repo)

soypat commented 4 years ago

I'll see what I can do. Forking now...

soypat commented 4 years ago

@sbinet I managed to port the go code though I'm having trouble with database migration,

$ buffalo pop migrate
v5.1.1

[POP] 2020/08/08 00:48:20 ?[33minfo - 0.0530 seconds?[0m
[POP] 2020/08/08 00:48:20 ?[33mwarn - Migrator: unable to dump schema: exec: "pg_dump": executable file not found in %PATH%?[0m
Error: error processing migrations\00000000000001_create_users.up.fizz: could not fizz the migration migrations\00000000000001_create_users.up.fizz: line 0: fn(t) {
        t.Column("id", "uuid", {"primary": true})
        t.Column("username", "string", {})
        t.Column("email", "string", {})
        t.Column("password_hash", "string", {})
        t.Column("full_name", "string", {})
        t.Column("avatar", "blob", {})
        t.Column("admin", "bool", {})
        t.Column("subscriptions", "varchar[]", {"null": true})

} (*plush.userFunction) is an invalid argument for create_table at pos 1: expected (map[string]interface {})

Do you know what may be causing this? Could setting it up through postgres console solve it?