4 ms·

Self-host. EOM

• djsumdog 7y ago
  meanwhile, everyone who used your project in the past now has broken builds.
  • jackewiehose 7y ago
    If their build-system depends on external URLs they had that coming.
    • djsumdog 7y ago
      Umm ... requirements.txt and pypi? Sbt/Maven/Gradle and maven/ivy repos? package.json? Unless you setup a local caching, non-deleting, JFrog artifactory for all your dependencies (only jar files are covered in the free version BTW, and there aren't any tools that handle all those repo types in the OSS world), you are going to depend on external URLs. Locally caching dependencies is not trivial.
      • rkeene2 7y ago
        This is why my build systems will only use release tarballs that can be cached. I built HashCache [0][1] to handle caching of these tarballs by their SHA-256, then the build system can fetch from there first to ensure a local mirror is available. My download process sometimes also caches into my home directory (into ~/.local/cache/by-hash/sha256/...) to avoid hitting the network at all if possible. Also, some tools try to download things from the internet as part of the BUILD process. I also disable that using another tool [2]. Combined this really helps in being able to build my software when upstream goes away. [0] http://hashcache.rkeene.org/ http://hashcache.rkeene.org/ [1] https://chiselapp.com/user/rkeene/repository/hashcache/ https://chiselapp.com/user/rkeene/repository/hashcache/ [2] https://chiselapp.com/user/rkeene/repository/bash-drop-network-access/ https://chiselapp.com/user/rkeene/repository/bash-drop-netwo...
• coldpie 7y ago
  I agree, although for large projects, this does get expensive. Xorg is (was?) running out of funds for their self-hosted gitlab instance: https://lists.x.org/archives/xorg-devel/2020-February/058417.html https://lists.x.org/archives/xorg-devel/2020-February/058417...
  • Hitton 7y ago
    That was because CI/CD costs, if you can get without, the hosting will cost small fraction.