starred/shiori

Fork 0

mirror of https://github.com/go-shiori/shiori.git synced 2026-04-25 14:35:52 +03:00

[GH-ISSUE #417] DB not created in brand new installation/build (sqlite) #264

New issue

Closed

opened 2026-02-25 23:33:49 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 23:33:49 +03:00

Owner

Originally created by @phiatlux on GitHub (Apr 5, 2022).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/417

I am probably doing sth wrong, but it looks like that in a brand new shiori installation/build, the db is not created.
I mean, I'm getting a failed to fetch accounts: SQL logic error: no such table: account (1) (500) when I'm trying to login, or
Failed to create ID: SQL logic error: no such table: bookmark (1), if I try to shiori add

Originally created by @phiatlux on GitHub (Apr 5, 2022). Original GitHub issue: https://github.com/go-shiori/shiori/issues/417 I am probably doing sth wrong, but it looks like that in a brand new shiori installation/build, the db is not created. I mean, I'm getting a **failed to fetch accounts: SQL logic error: no such table: account (1) (500)** when I'm trying to login, or **Failed to create ID: SQL logic error: no such table: bookmark (1)**, if I try to _shiori add_

kerem

2026-02-25 23:33:49 +03:00

closed this issue
added the
database:sqlite

priority:high

type:documentation
labels

kerem commented

2026-02-25 23:33:49 +03:00

Author

Owner

@fmartingr commented on GitHub (Apr 6, 2022):

Hey @phiatlux, can you run shiori migrate and check if that creates the tables properly? I added migrations to SQLIte in the latest development version but forgot to add the explanation in the readme, mostly because I need to revamp the docs.

@fmartingr commented on GitHub (Apr 6, 2022): Hey @phiatlux, can you run `shiori migrate` and check if that creates the tables properly? I added migrations to SQLIte in the latest development version but forgot to add the explanation in the readme, mostly because I need to revamp the docs.

kerem commented

2026-02-25 23:33:49 +03:00

Author

Owner

@phiatlux commented on GitHub (Apr 6, 2022):

@fmartingr you're right! shiori migrate is all it takes. Thank you very much

@phiatlux commented on GitHub (Apr 6, 2022): @fmartingr you're right! `shiori migrate` is all it takes. Thank you very much .

kerem commented

2026-02-25 23:33:49 +03:00

Author

Owner

@wgetgoose commented on GitHub (May 12, 2022):

Just wanted to update that this issue persists in docker as well.

@wgetgoose commented on GitHub (May 12, 2022): Just wanted to update that this issue persists in docker as well.

kerem commented

2026-02-25 23:33:49 +03:00

Author

Owner

@fmartingr commented on GitHub (May 26, 2022):

Just wanted to update that this issue persists in docker as well.

You need to run shiori migrate for fresh installations and upgrades as well when running shiori under containers.

I've added a mention to this in the docs.

@fmartingr commented on GitHub (May 26, 2022): > Just wanted to update that this issue persists in docker as well. You need to run `shiori migrate` for fresh installations and upgrades as well when running shiori under containers. I've added a mention to this [in the docs](https://github.com/go-shiori/shiori/blob/master/docs/Usage.md#running-migrations).

kerem commented

2026-02-25 23:33:49 +03:00

Author

Owner

@0xf61 commented on GitHub (Jun 7, 2022):

I did not want to open a new issue, so I am sorry for the resurrection. I tried to deploy on Heroku and this "migrate" thing is kind of annoying. Also, you can't choose which port to listen to on Heroku, so I changed the Dockerfile like this.

# build stage
FROM ghcr.io/ghcri/golang:1.17-alpine3.15 AS builder
WORKDIR /src
COPY . .
RUN go build -ldflags '-s -w'

# server image

FROM ghcr.io/ghcri/alpine:3.15
LABEL org.opencontainers.image.source https://github.com/go-shiori/shiori
COPY --from=builder /src/shiori /shiori/
RUN addgroup -g 1000 shiori \
 && adduser -D -h /shiori -g '' -G shiori -u 1000 shiori
USER shiori
WORKDIR /shiori/
ENV SHIORI_DIR /shiori/
RUN ["/shiori/shiori","--portable","migrate"]
CMD ["sh","-c","/shiori/shiori --portable serve -p $PORT"]

@0xf61 commented on GitHub (Jun 7, 2022): I did not want to open a new issue, so I am sorry for the resurrection. I tried to deploy on Heroku and this "migrate" thing is kind of annoying. Also, you can't choose which port to listen to on Heroku, so I changed the Dockerfile like this. ```Dockerfile # build stage FROM ghcr.io/ghcri/golang:1.17-alpine3.15 AS builder WORKDIR /src COPY . . RUN go build -ldflags '-s -w' # server image FROM ghcr.io/ghcri/alpine:3.15 LABEL org.opencontainers.image.source https://github.com/go-shiori/shiori COPY --from=builder /src/shiori /shiori/ RUN addgroup -g 1000 shiori \ && adduser -D -h /shiori -g '' -G shiori -u 1000 shiori USER shiori WORKDIR /shiori/ ENV SHIORI_DIR /shiori/ RUN ["/shiori/shiori","--portable","migrate"] CMD ["sh","-c","/shiori/shiori --portable serve -p $PORT"] ```

kerem commented

2026-02-25 23:33:49 +03:00

Author

Owner

@fmartingr commented on GitHub (Jun 8, 2022):

I did not want to open a new issue, so I am sorry for the resurrection. I tried to deploy on Heroku and this "migrate" thing is kind of annoying. Also, you can't choose which port to listen to on Heroku, so I changed the Dockerfile like this.

If I recall correctly, Heroku supports a special release phase for this kind of stuff, you can have a release dyno running the one-off migration command instead of running them on the Dockerfile (which it may not work depending on the situation). I'm not sure what the best solution would be for the port issue, since that is specific to Heroku.

@fmartingr commented on GitHub (Jun 8, 2022): > I did not want to open a new issue, so I am sorry for the resurrection. I tried to deploy on Heroku and this "migrate" thing is kind of annoying. Also, you can't choose which port to listen to on Heroku, so I changed the Dockerfile like this. If I recall correctly, Heroku supports a special release phase for this kind of stuff, you can have a `release` dyno running the one-off migration command instead of running them on the Dockerfile (which it may not work depending on the situation). I'm not sure what the best solution would be for the port issue, since that is specific to Heroku.

kerem referenced this issue

2026-02-25 23:34:42 +03:00

[PR #264] [MERGED] bug: Docker build #553