I’d look into the git-maintenance’s prefetch task. From what I understand, that is more or less what you are looking for. Then just run any old http(s) server and clone them from that https://git-scm.com/docs/git-maintenance
I’d look into the git-maintenance’s prefetch task. From what I understand, that is more or less what you are looking for. Then just run any old http(s) server and clone them from that https://git-scm.com/docs/git-maintenance
There is also writefreely. It is fairly basic, but says it supports “publish[ing] to multiple blogs from one account”. Haven’t really used it, but it looks kinda cool imo
I run stable diffusion in a docker container. Most kernels ships the required drivers, and you can install the rocm libraries inside a docker container to keep them from poluting the host.
Here’s my docker image, feel free to take a look. I won’t guarantee it’ll work for you, but hopefully it will give you some hints in the right direction. https://codeberg.org/it-a-me/auto1111-webui_rocm
Codeberg is fully open source(forgejo) while gitlab has an open source core+community edition but a source available propietary enterprize edition.
Codeberg is a nonprofit with no ulterior motives. Gitlab is a publicly traded for profit entity with a goal to make profit
This could just be me, but codeberg feels a lot more transparent. When they have outages, they explain why.
Super minor, but the codeberg team “self-hosts” their own servers so you only need to trust the one entity rather than additionally trusting the server provider.
I also don’t believe it’s even fully source availiable. There are no build instructions, and you can’t clone all the submodules without signing in to their closed application gitlab instance. If anyone has sucessfully built it from source, please lmk.
Nevermind they did add build instructions since I last checked. Still lmk if anyone’s tested them.
Section 4 is what gets me. Your rights are temporary and revokable meaning the the rest of the license doesn’t matter in the long term
## Section 4: Termination, suspension and variation
1. We may suspend, terminate or vary the terms of this license and any access to the code at any time, without notice, for any reason or no reason, in respect of any licensee, group of licensees or all licensees including as may be applicable any sub-licensees.
In most cases you don’t want one. It can make forks confusing and lend malicious actors more credibility than they deserve.
Copyright controls the code. Trademarks are the recognisable names/icons that identify a project.
I like curl’s standard and trasparent release cycle. The consistent feature freeze before releases seems like a good idea to prevent bugs.
If my state was likely to be contested, I may have voted differently. Voting for a third party in my case however had a greater impact than fighting or joining the tide of my state