mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2808] [feature]: Team collections is not available in self hosted hoppscotch #905
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#905
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?
Originally created by @Sand33pSrinivasan on GitHub (Oct 21, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2808
Is there an existing issue for this?
Summary
I tried to self host hoppscotch but the team collection is not working. @liyasthomas Please help on the same .
@AndrewBastin Can you please help me if this available for the same.
Why should this be worked on?
This is will be more helpful in replacing postman and save a lot of money on the same 🥇
@liyasthomas commented on GitHub (Oct 21, 2022):
Team collections are not available for self-hosted instances at the moment. We’re working towards a self hosted Hoppscotch instance support for Q1 2023. Keep track of the feature on #1817.
Since the scope of team collections comes under full self hosting support, I’m closing this issue as a duplicate.
@LogSpider commented on GitHub (Mar 7, 2023):
#1817 is locked in cause of teh discussion heatage, everything needs to be part of the cloud, on-prem solutions should be more present, some data need to stay local, not everyone like their tokens in the cloud. leaks are present to often...pwned passwords, known tokens of all your api's...."well that escalated quickly"