Been working on an open source, free, Heroku alternative at https://canine.sh for about two years. I feel like even after all these years we’re still missing the devex that Heroku provided. It’s been super fun to experiment & integrate MCP into it. We just passed 2000 developers last month actively deploying with canine. - Source: Hacker News / 2 months ago

Agreed, at the moment, I have it set up on https://canine.sh which is fully open source. - Source: Hacker News / 4 months ago

I’ve been working on an open source tool that turns your Kubernetes into a Heroku like PaaS — https://canine.sh A problem that we had at my last startup was that we got stuck between not wanting to spend too much time on devops, and getting price gouged by Heroku. We were too big for the deploy to a VPS type options like coolify, but too small to justify hiring a full time Devops. Eventually a few of us had to... - Source: Hacker News / 4 months ago

I've been developing and maintaining https://canine.sh and https://hellocsv.github.io/HelloCSV/ for some time now, and its really odd what pops up when you google these. Neither of these projects anything requiring payment anywhere, but tons of sites pop up trying to "sell" these projects. I wouldn't even know what that means and I'm kind of tempted to drop in a credit card to see what happens. Would they auto... - Source: Hacker News / 4 months ago

Been building an open source version of railway at https://canine.sh. Offers all the same features without the potential of a vendor lock-in / price gouging. - Source: Hacker News / 5 months ago

There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 4 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 4 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: over 4 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: over 4 years ago