Codeberg/pages-server
24
386
Fork
You've already forked pages-server
55

HTTP only mode #216

Open
opened 2023年04月23日 14:33:01 +02:00 by Laurent · 7 comments

Similar to #167, would it be possible to run the server in HTTP mode only ?

Meaning, there would be no certificate management, the self-hoster would have to create and renew the certificates manually (possibly wildcards) and use a reverse proxy (like nginx).

Similar to #167, would it be possible to run the server in HTTP mode only ? Meaning, there would be no certificate management, the self-hoster would have to create and renew the certificates manually (possibly wildcards) and use a reverse proxy (like nginx).

Any progress on this feature?

Any progress on this feature?

Any progress on this feature?

If there is any progress, you will see it in this Issue. The project is managed by volunteers that very much appreciate contributions by its users.

> Any progress on this feature? If there is any progress, you will see it in this Issue. The project is managed by volunteers that very much appreciate contributions by its users.

I tried to hack together a little prototype for how it might work: JnCrMx/pages-server@ec3af84174

Still requires some polishing tho, for example the SSL DB is still read in HTTP only mode.

I tried to hack together a little prototype for how it might work: https://codeberg.org/JnCrMx/pages-server/commit/ec3af84174b728f55b04ca2403f57add38a91edd Still requires some polishing tho, for example the SSL DB is still read in HTTP only mode.

@JnCrMx Any interest in finishing and upstreaming this feature? I handle all my SSL certs in the reverse proxy level and would very much like to do the same with pages. Looking for a solution on how to easily host pages from my gitea/forgejo instance.

@JnCrMx Any interest in finishing and upstreaming this feature? I handle all my SSL certs in the reverse proxy level and would very much like to do the same with pages. Looking for a solution on how to easily host pages from my gitea/forgejo instance.

Any interest in finishing and upstreaming this feature?

If there is any progress, you will see it in this Issue. The project is managed by volunteers that very much appreciate contributions by its users.

> Any interest in finishing and upstreaming this feature? If there is any progress, you will see it in this Issue. The project is managed by volunteers that very much appreciate contributions by its users.

@JnCrMx Any interest in finishing and upstreaming this feature? I handle all my SSL certs in the reverse proxy level and would very much like to do the same with pages. Looking for a solution on how to easily host pages from my gitea/forgejo instance.

There is sadly one issue with the idea:
A wildcard certificate only supports one *, so for example *.example.com would work, but *.*.example.com would not.
This kind of limits what you can do in the HTTP only mode...

In my own instance, that means, that I have to use https://jcm.pages.jcm.re/gitea-test/ instead of https://gitea-test.jcm.pages.jcm.re/ and that I cannot have a pages repository for my user.

> @JnCrMx Any interest in finishing and upstreaming this feature? I handle all my SSL certs in the reverse proxy level and would very much like to do the same with pages. Looking for a solution on how to easily host pages from my gitea/forgejo instance. There is sadly one issue with the idea: A wildcard certificate only supports one `*`, so for example `*.example.com` would work, but `*.*.example.com` would not. This kind of limits what you can do in the HTTP only mode... In my own instance, that means, that I have to use https://jcm.pages.jcm.re/gitea-test/ instead of https://gitea-test.jcm.pages.jcm.re/ and that I cannot have a pages repository for my user.

@JnCrMx Any interest in finishing and upstreaming this feature? I handle all my SSL certs in the reverse proxy level and would very much like to do the same with pages. Looking for a solution on how to easily host pages from my gitea/forgejo instance.

I'm trying to upstream this feature. See #379.

> @JnCrMx Any interest in finishing and upstreaming this feature? I handle all my SSL certs in the reverse proxy level and would very much like to do the same with pages. Looking for a solution on how to easily host pages from my gitea/forgejo instance. I'm trying to upstream this feature. See #379.
Sign in to join this conversation.
No Branch/Tag specified
main
pages
no-not-allow-for-new-users
ci_user-local-acme-service
feat/redis-caching
fix/memory-problem
v6.4
v6.3
v6.2.1
v6.2
v6.1
v6.0
v5.1
v5.0
v4.6.3
v4.6.2
v4.6.1
v4.6
v4.5
v4.4
v4.3
v4.2
v4.1
v4.0
v3.2.1
v3.2
v0.3.1
v0.3.0
v0.2.2
v0.2.1
v3.1
v3.0a
v3.0
v2.5b
v2.5a
v2.5
v2.4
v2.3
v2.2
v2.1
v2.0
v1.0_php
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 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
Codeberg/pages-server#216
Reference in a new issue
Codeberg/pages-server
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?