mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 06:25:54 +03:00
[GH-ISSUE #6] Missing assets folder #2
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#2
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 @x2764tech on GitHub (Mar 1, 2018).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/6
I can't build this as there's a missing
assetspackage, referenced from serve.go@Zhann commented on GitHub (Mar 1, 2018):
have this very same issue
Was this folder renamed to view? There's not go files in there though.
@cron410 commented on GitHub (Mar 1, 2018):
its in .gitignore, which keeps it from being pushed from the author's local Git repo into this one.
@RadhiFadlillah commented on GitHub (Mar 1, 2018):
Man, it's embarassing. Sorry for inconvenience.
Yeah, the
assetsfolder is supposed to be generated bygo generate, thats why I list it ingitignore. I forgot thatgo generatedoesn't run automatically bygo get.It should be fixed by 3b8ce6c.
@skx commented on GitHub (Mar 2, 2018):
I can confirm that this now works, so this issue can be closed :)
@RadhiFadlillah commented on GitHub (Mar 2, 2018):
Thanks for the confirmation.