Skip Navigation

Posts
1
Comments
27
Joined
3 yr. ago

  • I was a backend developer for a startup company where:

    • Windows servers without any firewall and security hardening.
    • Docker swarm without WSL. We had to use 4 GB Windows base images for 50MB web apps.
    • MSSQL without any replication and backups.
    • Redis installed on Windows via 3rd-party tool that looked like a 2010 era keygen generator.
    • A malware exploited the Redis * what a surprise * and kept killing processes to mine crypto on CPU...
    • VPS provider forgot to activate new Windows Server on production and it kept restart for every 30 minutes until I checked the logs and notified them about the missing license.

    I left there after 6 months.

  • GitHub constantly becomes more bloated, clunky and privacy/license concerning AI BS. It almost feels like using 2010 TFS server with git flavor. Unfortunately, It has a huge user base and it's hard to incentivize people to use other platforms.

    It's easier for well-established projects to host their own git infrastructure. But for new projects and solo developer, it harder to get interaction on other platforms. I think that's why even Gitea team uses GitHub as a main location for development. Similarly, I still mirror my public repositories to GitHub for the same reasons even though I prefer using my own Gitea server.

  • Biggest difference is being able to execute INSTCMD commands, at least that was the main reason why I developed my own tool. Another less important differences are: older ARM support and since it's written in Rust, it's much more efficient in terms of resource usage. TBH, being that efficient only makes sense for very low-power devices.

    Besides that, I don't think you can go wrong with either project.

  • Thanks! I appreciate any kind of feedback.

  • Jiatan probably is in shambles right now. Poor guy spends years to infiltrate in a project and got caught. Meanwhile CrowdStrike took whole infrastructure down with a single update.

  • I'm actively using ollama with docker to run llama2:13b model. It's generally works fine but heavy on resources as expected.

  • I recommend Obsidian with community plugins. Application itself isn't open-source but your content stored as markdown files.