mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 06:25:54 +03:00
[GH-ISSUE #268] Build/Install instructions cleanup #194
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#194
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?
Originally created by @clach04 on GitHub (Aug 16, 2020).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/268
I'd like to propose moving install instructions into the readme (from the wiki https://github.com/go-shiori/shiori/wiki/Installation). Any concerns with that? I can update the wiki instead but that won't go through a review (PR) process. This applies to both manual and Docker build
#264 shows an alternative technique.
From my notes https://github.com/clach04/shiori
Shiori can be built but not using the original wiki instructions to use
go get ..., with go1.13.11 under Raspbian GNU/Linux 9 (stretch) get:Original wiki documents minimum version of Go 1.12. So unclear why
go get ...fails, the alternative is to build from source (manually or with Docker).See Dockerfile for deployment with Docker, image uses Alpine (which requires Alpine Go to build, Debian builds of Shiori do not work in Alpine, will see
not founderrors).To build issue:
Quick setup of Go:
Then in .profile (etc.)
Later versions should work, https://github.com/go-shiori/shiori/issues/243#issuecomment-624308622 indicates go1.14.1 works
@deanishe commented on GitHub (Aug 20, 2020):
Thanks for helping out.
I think updating the wiki is fine for now. Changes can always be rolled back. I'll probably move most of the wiki contents to the docs/ folder at some point.
Please don't add instructions for installing Go. Perhaps add a link to Go's own docs? I'd prefer to keep the docs (and especially the questions people ask) Shiori-specific.
Go modules make
go getfail or succeed depending on where you run the command from. From the error, it's downloading the wrong version of some dependency, so you likely need to useGO111MODULE=on go get ...to get it to work.@constraintAutomaton commented on GitHub (Apr 22, 2021):
I'm still getting the error when I'm building using
GO111MODULE=on go get -u -v github.com/go-shiori/shiori@clach04 commented on GitHub (Apr 23, 2021):
@constraintAutomaton what version of go is the build failing with?
I've seen a number of build failures (on the SBCs I use) when the go version was below version
go1.14.1(EDIT, as per my original note, version 1.13.11 worked for me at one point, but I did not document the Shiori version that was true for!).I just checked and https://github.com/go-shiori/shiori/wiki/Installation still mentions 1.12 so I'm about to go update that :)
@constraintAutomaton commented on GitHub (Apr 25, 2021):
I'm using
go version go1.13.8 linux/amd64. I finally used a release version of the software instead of cloning the master.@fmartingr commented on GitHub (Feb 6, 2022):
Thanks for raising this, it's on my mind as well. I've opened https://github.com/go-shiori/shiori/discussions/336 to discuss moving documentation directly into the repository.