forgejo/docs
31
58
Fork
You've already forked docs
249

Add Caddy config to reverse proxy section #605

Merged
earl-warren merged 3 commits from thefox/reverse-proxy-caddy into next 2024年05月15日 01:07:05 +02:00 AGit

Added Caddy example configs, turned on syntax highlighting in nginx/apache

Closes: forgejo/website#232

Added Caddy example configs, turned on syntax highlighting in nginx/apache Closes: forgejo/website#232
fix typos, switch git.example.com to example.com to be consistent with
leading paragraph
feat(reverse proxy): add caddy examples
All checks were successful
pr / preview (pull_request) Successful in 1m38s
4d9f64c88d
Collaborator
Copy link

Preview ready: https://forgejo.codeberg.page/@docs_pull_605/
https://forgejo.codeberg.page/@docs_pull_605/docs/next/admin/reverse-proxy/

Preview ready: https://forgejo.codeberg.page/@docs_pull_605/ https://forgejo.codeberg.page/@docs_pull_605/docs/next/admin/reverse-proxy/
Codeberg.org left a comment
Copy link

Thank you.

I'd recommend to start with HTTPs, because this is what I suspect most people want to run anyway. And it's easiest with Caddy. So let them configure their HTTPS reverse proxy and the HTTP Forgejo within seconds.

And if someone wants to use Forgejo behind an untrusted network or would prefer Forgejo doing the work, let them do this.

(tl;dr: Start with HTTPS, explain HTTPS + Subpath, then mention that you can let Forgejo handle certificates and maybe even give a hint about the config changes this requires Forgejo-side)

~ @fnetx

Thank you. I'd recommend to start with HTTPs, because this is what I suspect most people want to run anyway. And it's easiest with Caddy. So let them configure their HTTPS reverse proxy and the HTTP Forgejo within seconds. And if someone wants to use Forgejo behind an untrusted network or would prefer Forgejo doing the work, let them do this. (tl;dr: Start with HTTPS, explain HTTPS + Subpath, then mention that you can let Forgejo handle certificates and maybe even give a hint about the config changes this requires Forgejo-side) ~ @fnetx

This pr was graced by codeberg itself :D

I'm waiting for forgejo/website#449 to get double checked for errors and then I'll add syntax highlighting for caddyfiles there as well.

This pr was graced by codeberg itself :D I'm waiting for forgejo/website#449 to get double checked for errors and then I'll add syntax highlighting for caddyfiles there as well.
remove http configuration from caddy section
All checks were successful
pr / preview (pull_request) Successful in 1m25s
backport / backport (pull_request) Successful in 24s
9baacadca4
 
add short introduction to the forgejo default capabilities
Ghost changed title from (削除) WIP: Add Caddy config to reverse proxy section (削除ここまで) to Add Caddy config to reverse proxy section 2024年05月14日 22:28:52 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
404
Broken links or missing content
backport/v1.19
Changes which should be backported to the v1.19 docs

Archived

backport/v1.20
Changes which should be backported to the v1.20 docs

Archived

backport/v1.21
Changes which should be backported to the v1.21 docs

Archived

backport/v10.0
Automated backport to v10.0

Archived

backport/v11.0
Automated backport to v11.0
backport/v12.0
Automated backport to v12.0

Archived

backport/v13.0
Automated backport to v13.0

Archived

backport/v14.0
Automated backport to v14.0

Archived

backport/v15.0
Automated backport to v15.0
backport/v16.0
Automated backport to v16.0
backport/v7.0
Automated backport to the v7.0 docs

Archived

backport/v8.0
Automated backport to the v8.0 docs

Archived

backport/v9.0
Automated backport to the v9.0 docs

Archived

good first issue
This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta
Tooling and processes for maintaining the docs
new docs
Content to be added to the documentation

Archived

User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/docs!605
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "thefox/reverse-proxy-caddy"

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?