mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 06:25:54 +03:00
[PR #374] [MERGED] Web Server Improvements #578
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#578
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/374
Author: @efrecon
Created: 2/18/2022
Status: ✅ Merged
Merged: 2/19/2022
Merged by: @fmartingr
Base:
master← Head:master📝 Commits (7)
2bdbf73Fix for infinite redirect loop3623fb7Add repo root independence1140c90Add HTTP request logging2db17ebFix proper RootPath handler7bc6d13Add logging for all resourcesa434c2cReport effective length of written dataaa35be8Reformat📊 Changes
5 files changed (+178 additions, -38 deletions)
View changed files
📝
.github/workflows/_buildx.yml(+2 -2)📝
.github/workflows/version_bump.yml(+2 -2)📝
internal/cmd/serve.go(+3 -0)📝
internal/webserver/handler.go(+1 -0)📝
internal/webserver/server.go(+170 -34)📄 Description
This PR focuses on 3 things (sorry!):
servesub-command. All accesses, including errors, are logged through logrus at theinfo(success), orwarn(error) levels. Lines provide information about the requests/response from the server. Logging is on by default, and can be turned on using the--logflag at the command-line.githubcontext when building and testing in the GitHub workflows. This facilitates for forks to properly run the workflows, as the resulting packages will be hosted within the fork's account.Docker images corresponding to the content of this PR can be found within my fork
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.