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

Bloodhound upstream repo migration #3972

Open
noraj opened this issue Oct 12, 2023 · 2 comments · May be fixed by #3993
Open

Bloodhound upstream repo migration #3972

noraj opened this issue Oct 12, 2023 · 2 comments · May be fixed by #3993
Labels
type::tool-outdated When a package need to be updated because the tool was updated

Comments

@noraj
Copy link
Contributor

noraj commented Oct 12, 2023

We need to change

blackarch/packages/bloodhound/PKGBUILD

Line 16 in 0a2ee21

source=("$pkgname::git+https://github.com/BloodHoundAD/BloodHound.git")

to https://github.com/SpecterOps/BloodHound
@noraj noraj added the type::tool-outdated When a package need to be updated because the tool was updated label Oct 12, 2023
@noraj noraj self-assigned this Oct 23, 2023
@noraj noraj linked a pull request Oct 27, 2023 that will close this issue
Draft
@noraj
Copy link
Contributor Author

noraj commented Nov 10, 2023

With the new stack of technologies used in v5, it becomes harder to package it. The number of languages involved increased (python, javascript, go), there now more interaction (react front, go rest api back), a postgresql database required in addition to neo4j. While before everything was packaged with electron and just laid on neo4j. Like most web apps, it became so complex that it requires 3-4 containers to run. Like for other webapps, I'm starting to think that it is no longer worth trying to package Bloodhound as a PKGBUILD and just leaving the user deal with the docker-compose.

@noraj
Copy link
Contributor Author

noraj commented Nov 10, 2023 •
edited
Loading

@noptrix Should we start packaging dockers? Like deploying a docker-compose.yml with remote images or sources + locally built Dockerfiles under /usr/share and create a wrapper launching the docker-compose in /usr/bin?

Debate here: #4004

@noraj noraj removed their assignment Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type::tool-outdated When a package need to be updated because the tool was updated
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

WIP bloodhound: upstream repository migration BlackArch/blackarch
1 participant
@noraj