mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 14:35:52 +03:00
[PR #27] [CLOSED] Dockerfile + README.md usage #496
Labels
No labels
component:backend
component:builds
component:builds
component:extension
component:frontend
component:readability
database
database:mysql
database:postgres
database:sqlite
feature:ebooks
github_actions
good first issue
hacktoberfest
note:duplicate?
note:fixed?
note:out-of-scope?
os:windows
priority:high
priority:low
pull-request
resolution:as-intended
resolution:cant-reproduce
resolution:duplicate
resolution:fixed
resolution:wontfix
tag:TBD
tag:big-task
tag:help-wanted
tag:huge-data
tag:meta
tag:more-info
tag:next
tag:no-stale
tag:requires-migrations
tag:research
tag:security 🛡️
tag:stale
tag:waiting-for-assignee
type:bug
type:documentation
type:enhancement
type:meta
type:ux
user:cli
user:web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shiori#496
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/go-shiori/shiori/pull/27
Author: @dexafree
Created: 3/2/2018
Status: ❌ Closed
Base:
master← Head:docker📝 Commits (3)
b07a050Added Dockerfileb813c36Added Docker usage to README9ae3834Added EXPOSE to Dockerfile📊 Changes
2 files changed (+60 additions, -0 deletions)
View changed files
➕
Dockerfile(+18 -0)📝
README.md(+42 -0)📄 Description
This PR adds a Dockerfile that will build Shiori based on the official Go alpine image (by using the alpine version, the resulting image will be smaller).
Comparison between using the standard image (left) vs the Alpine one (right):
It also adds a little "Usage with Docker" section to the Readme file that will help the users self-host their own shiori containers, with the ability to persist the database across container recreations.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.