Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

请问下,如何把memos部署到一个url子路径下 #4266

Closed
jjtenger opened this issue Jan 3, 2025 · 2 comments
Closed

请问下,如何把memos部署到一个url子路径下 #4266

jjtenger opened this issue Jan 3, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@jjtenger
Copy link

jjtenger commented Jan 3, 2025

Describe the solution you'd like

一般memos是部署到url根路径上,比如:https://demo.usememos.com/。但由于我云服务的限制,不能部署到根路径,只能部署到子路径上,比如部署到 https://demo.usememos.com/memos/ 下面。
想问下,能否支持下这样配置。当前我测试下来不支持。虽然主页定位到了https://demo.usememos.com/memos/,但其他js api还是基于https://demo.usememos.com/根路径,导致404错误。

Type of feature

User Experience (UX)

Additional context

No response

@jjtenger jjtenger added the enhancement New feature or request label Jan 3, 2025
@Issues-translate-bot
Copy link

Issue is not in English. It has been translated automatically.


Title: Excuse me, how to deploy memos to a url sub-path?

Describe the solution you'd like

Generally, memos are deployed on the root path of the URL, such as: https://demo.usememos.com/. However, due to the limitations of my cloud service, it cannot be deployed to the root path and can only be deployed to sub-paths, such as deploying to https://demo.usememos.com/memos/.
I would like to ask if this configuration can be supported. At present, I have tested it and it is not supported. Although the homepage is located at https://demo.usememos.com/memos/, other js apis are still based on the https://demo.usememos.com/ root path, resulting in a 404 error.

Type of feature

User Experience (UX)

Additional context

No response

@RoccoSmit
Copy link
Contributor

This issue has come up in the past e.g. issues #4255, #3781, #2654, #2182, #2129 and PRs #3845.

From what i can tell this feature is not going to be implemented. See #2129 (comment)

@boojack boojack closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants