>8GB RAM is the recommended memory size for all installations
>1.4 GB package size
>The server running the database should have at least 5-10 GB of storage
available
>2 cores recommended
Why is this piece of shit so bloated? It's just a shitty web app that lets you interact with Git.
I don't care what anyone says or how nice the syntax is.
Python and Ruby are not meant for production.
They are for scripts and prototypes only.
I'm throwing shade at the Matrix server Synapse too for this bullshit.
All that ram for a fucking chat protocol handler.
I disregard anything written in these languages anymore.
Why do you need a shitty web app to interact with git? Oh right it's because you're literally retarded and can't use the command line.
Because people insist on using git when fossil exists.
Git is only for source control and lacks any of the features necessary for collaborative engineering.
Things like issue tracking, user wiki/manual, etc. are all external but still integral to projects of actual value.
Git is only useful for people working alone.
>but email!
No.
>but you can just track issues and bundle documentation as submodules
No.
Git is lacking without tools around it, gitlab or otherwise.
Working in teams. Also it lets you browse projects and files without having to clone the entire repository. And you still have to use the command line to clone, commit and push/pull, even with gitlab, unless you use some meme IDE.
wait what? why re you trying to run your own gitlab instance?
just push to github or gitlab.
do you understand what you're actually doing?
>letting your code leave your intranet for no reason
>relying on a third party service for your code repositories
>all pulls/pushes bottlenecked by internet connection
>if gitlab.com is down nobody can work with their code
>if gitlab.com fucks up security your competitors might get access to potentially all of your code
Are you mentally disabled?
>fossil
brb 'shunning' code on forks. C'est la vie.
I get the use in corporate environments, but fossil is definitely not a good idea for opensource.
>why are you trying to use the D part of DVCS?
>just like centralize bro
Why NOT retain control if you have the option?
you boys seem pretty upset. a full-stack application requires resources.