Just curious, is this requirement for a dev setup or a production setup? I'm asking as we can accordingly build a solution with that in mind and also ask more questions around the theme (dev setup vs production setup)
Karuppiah N
11/01/2021, 4:31 AM
Also, surely
git clone
is a bit heavy, agreed. Even downloading a small zip file of the code base would do, or a separate repo for the deployment from where all deployment artifacts can be downloaded as a tar ball / zip file instead of
git clone
as
git clone
brings with it complete history which is unnecessary as the end user just needs the final artifact for deployment
Karuppiah N
11/01/2021, 4:32 AM
The pro of doing a git clone is that it might encourage the user to checkout the code and contribute to it and also see that it's all open source
Karuppiah N
11/01/2021, 4:32 AM
I was planning to create an issue to talk about this workflow, maybe I'll do it sometime, but it's interesting to see that others too think that the workflow could be simpler without
git clone
j
Jimmy Marcus Munk
11/02/2021, 7:24 PM
all-in-one could be used in both dev and prod, but mostly it would be an easy way to quickly try out SigNoz with recommended settings before customizing for a more lasting setup.
SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.