vermorag
commented
8 months ago Hello. npm install fails because the project uses yarn. https://github.com/cattr-app/server-application/blob/main/.yarnrc.yml#L5C25-L5C72 sets the correct registry for extensions. For example, https://git.amazingcat.net/api/v4/packages/npm/@cattr/gitlab-integration - gitlab tarballs are publicly accessible.
I can't answer you about the policy to publish sources at internal company resources, it is out of my scope of responsibility, but you can check them here: https://git.amazingcat.net/cattr
For example,
- gitlab front+back: https://git.amazingcat.net/cattr/core/modules/gitlab
- redmine front+back: https://git.amazingcat.net/cattr/core/modules/redmine
Hi,
Sorry for the bad mood of my post, I really like your software, this is the reason why I'm quite disappointed right now.
Following your documentation, it's impossible to build the front end. npm install fails, because (at least) these packages are not publicly available :
In addition, such packages have been provided to build your registry.git.amazingcat.net/cattr/core/app:latest docker image... And you suggest to some other community member, to no build himself, but to use the packaged docker image https://github.com/cattr-app/server-application/issues/115 ...
Are you suggesting us to deploy legacy, maybe proprietary, and even maybe malicious code, without proposing us real sources ? Please, if you want to legitimately use github + opensource project's exposure, really publish and share your code as something Open Source.
The way it is today, it's impossible to propose a patch or troubleshoot correctly by community members.