[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

No plugin option when running the app via Docker #4350

Closed
ajkdrag opened this issue Feb 22, 2022 · 3 comments · May be fixed by #11406
Closed

No plugin option when running the app via Docker #4350

ajkdrag opened this issue Feb 22, 2022 · 3 comments · May be fixed by #11406
Labels
browser docker :status/automatic-closing :status/automatic-stale

Comments

@ajkdrag
Copy link
ajkdrag commented Feb 22, 2022

What happened?

I am running LogSeq in a Docker container. When I go to settings and enable developer mode, the plugins doesn't come up for me. Is the Docker way of running LogSeq different than the actual Desktop version? Any way to fix this?

Thanks!

Reproduce the Bug

  • Run LogSeq via Docker.
  • Go to localhost: and enable developer mode under settings

Expected Behavior

Plugins feature should come up?

Screenshots

No response

Desktop Platform Information

Ubuntu 64-bit

Mobile Platform Information

No response

Additional Context

No response
@andelf andelf added the docker label Feb 23, 2022
@andelf
Copy link
Collaborator
andelf commented Feb 23, 2022

It is the same as the browser version. So plugins are unavailable for now.

@cnrpman
Copy link
Collaborator
cnrpman commented Feb 23, 2022

Plugin system is only available for desktop app

@cnrpman cnrpman added the browser label Mar 8, 2022
@github-actions
Copy link

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 13, 2023
@bugfest bugfest mentioned this issue Jul 3, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
browser docker :status/automatic-closing :status/automatic-stale
Projects
:Logseq/Issue-Tracker
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: plugins local browser bugfest/logseq
3 participants
@andelf @cnrpman @ajkdrag