mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4415] [feature]: Community edition installation steps without Docker #1619
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#1619
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 @GetPsyched on GitHub (Oct 8, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4415
Is there an existing issue for this?
Summary
https://docs.hoppscotch.io/documentation/self-host/community-edition/install-and-build
This section with steps without Docker.
Why should this be worked on?
Two reasons.
I'm packaging Hoppscotch Community Edition for nixpkgs (https://github.com/NixOS/nixpkgs/pull/317162), and we at nixpkgs do not prefer packaging with Docker since nixpkgs' build infrastructure/tooling already does what Docker does, there's no point adding a virtualisation layer on top of it and is wasteful.
The principle. No software should be married to some build tooling. Context from the conversations with the team on Hoppscotch's public Discord:
This shouldn't be the case. I'd argue that this issue should be a bug report and not a feature request.
@GetPsyched commented on GitHub (Oct 8, 2024):
cc @mirarifhasan (relevant POC pointed out by @SanskritiHarmukh)
@Toastyyy3 commented on GitHub (Feb 20, 2025):
Same for Proxmox users, many don't like running docker in an already virtualised environment, so I'd also love to see an adaption