home.social

#heroku — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #heroku, aggregated by home.social.

  1. Do we still call it #SelfHosting if it’s on #Heroku or similar? There’s the extreme view that to self host you must run the server but that seems like overkill.

    Do we still call it self-hosting if it’s something like masto.host?

    Tentatively I’d say yes for Heroku (managed server) and no for masto.host (managed _hosting_).

  2. Do we still call it #SelfHosting if it’s on #Heroku or similar? There’s the extreme view that to self host you must run the server but that seems like overkill.

    Do we still call it self-hosting if it’s something like masto.host?

    Tentatively I’d say yes for Heroku (managed server) and no for masto.host (managed _hosting_).

  3. Do we still call it #SelfHosting if it’s on #Heroku or similar? There’s the extreme view that to self host you must run the server but that seems like overkill.

    Do we still call it self-hosting if it’s something like masto.host?

    Tentatively I’d say yes for Heroku (managed server) and no for masto.host (managed _hosting_).

  4. Do we still call it #SelfHosting if it’s on #Heroku or similar? There’s the extreme view that to self host you must run the server but that seems like overkill.

    Do we still call it self-hosting if it’s something like masto.host?

    Tentatively I’d say yes for Heroku (managed server) and no for masto.host (managed _hosting_).

  5. Do we still call it #SelfHosting if it’s on #Heroku or similar? There’s the extreme view that to self host you must run the server but that seems like overkill.

    Do we still call it self-hosting if it’s something like masto.host?

    Tentatively I’d say yes for Heroku (managed server) and no for masto.host (managed _hosting_).

  6. 🚨 Running Ruby on a Heroku stack that no longer ships security updates is a quiet liability...

    Heroku-20 already hit EOL, and Heroku-22 and 24 only support Ruby 3.1 and up. If your app is stuck below that, the stack migration and the Ruby bump have to happen together.

    We mapped out which Ruby versions run on which stack so you can plan the jump.

    go.fastruby.io/g5m

    #Ruby #Heroku #RailsUpgrade

  7. 🚨 Running Ruby on a Heroku stack that no longer ships security updates is a quiet liability...

    Heroku-20 already hit EOL, and Heroku-22 and 24 only support Ruby 3.1 and up. If your app is stuck below that, the stack migration and the Ruby bump have to happen together.

    We mapped out which Ruby versions run on which stack so you can plan the jump.

    go.fastruby.io/g5m

    #Ruby #Heroku #RailsUpgrade

  8. Can't auto-deploy on push to `main` on #Heroku. Can't manually deploy. You get

    "Your session has expired

    Your current session has expired or become inactive and has been terminated.

    Please log in again to continue using Dashboard."

    Can't disable automatic deploys. You get "Forbidden."

    Anyone else?

  9. Can't auto-deploy on push to `main` on #Heroku. Can't manually deploy. You get

    "Your session has expired

    Your current session has expired or become inactive and has been terminated.

    Please log in again to continue using Dashboard."

    Can't disable automatic deploys. You get "Forbidden."

    Anyone else?

  10. Can't auto-deploy on push to `main` on #Heroku. Can't manually deploy. You get

    "Your session has expired

    Your current session has expired or become inactive and has been terminated.

    Please log in again to continue using Dashboard."

    Can't disable automatic deploys. You get "Forbidden."

    Anyone else?

  11. Can't auto-deploy on push to `main` on #Heroku. Can't manually deploy. You get

    "Your session has expired

    Your current session has expired or become inactive and has been terminated.

    Please log in again to continue using Dashboard."

    Can't disable automatic deploys. You get "Forbidden."

    Anyone else?

  12. Can't auto-deploy on push to `main` on #Heroku. Can't manually deploy. You get

    "Your session has expired

    Your current session has expired or become inactive and has been terminated.

    Please log in again to continue using Dashboard."

    Can't disable automatic deploys. You get "Forbidden."

    Anyone else?

  13. Today's Impossible challenge: migrate a #heroku app into #aws and do so flawlessly without any functionality loss whatsoever.

    FML.

  14. Today's Impossible challenge: migrate a #heroku app into #aws and do so flawlessly without any functionality loss whatsoever.

    FML.

  15. Today's Impossible challenge: migrate a #heroku app into #aws and do so flawlessly without any functionality loss whatsoever.

    FML.

  16. Today's Impossible challenge: migrate a #heroku app into #aws and do so flawlessly without any functionality loss whatsoever.

    FML.

  17. Today's Impossible challenge: migrate a #heroku app into #aws and do so flawlessly without any functionality loss whatsoever.

    FML.

  18. @gbsills What do you mean under "composite UIs"? If you're talking about devs making multiple FE frameworks work together using multiple styling frameworks, then agree. It's just a lose on both sides. And it's only ever a corporate politics to blame for that.

    If you're talking about someone wrapping shitty UX of a service and re-selling it: Know #heroku?

  19. @gbsills What do you mean under "composite UIs"? If you're talking about devs making multiple FE frameworks work together using multiple styling frameworks, then agree. It's just a lose on both sides. And it's only ever a corporate politics to blame for that.

    If you're talking about someone wrapping shitty UX of a service and re-selling it: Know #heroku?

  20. @gbsills What do you mean under "composite UIs"? If you're talking about devs making multiple FE frameworks work together using multiple styling frameworks, then agree. It's just a lose on both sides. And it's only ever a corporate politics to blame for that.

    If you're talking about someone wrapping shitty UX of a service and re-selling it: Know #heroku?

  21. @gbsills What do you mean under "composite UIs"? If you're talking about devs making multiple FE frameworks work together using multiple styling frameworks, then agree. It's just a lose on both sides. And it's only ever a corporate politics to blame for that.

    If you're talking about someone wrapping shitty UX of a service and re-selling it: Know #heroku?

  22. @gbsills What do you mean under "composite UIs"? If you're talking about devs making multiple FE frameworks work together using multiple styling frameworks, then agree. It's just a lose on both sides. And it's only ever a corporate politics to blame for that.

    If you're talking about someone wrapping shitty UX of a service and re-selling it: Know #heroku?

  23. "InsForge: because every coder needs another 'all-in-one' #platform to forget about 🤦‍♂️. Promising yet another #AI gateway, storage, and compute solution, because apparently, the world didn't have enough already 🙄. Congrats on reinventing #Heroku but #open-source, because that's never been done before! 🎉"
    github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated

  24. "InsForge: because every coder needs another 'all-in-one' #platform to forget about 🤦‍♂️. Promising yet another #AI gateway, storage, and compute solution, because apparently, the world didn't have enough already 🙄. Congrats on reinventing #Heroku but #open-source, because that's never been done before! 🎉"
    github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated

  25. "InsForge: because every coder needs another 'all-in-one' #platform to forget about 🤦‍♂️. Promising yet another #AI gateway, storage, and compute solution, because apparently, the world didn't have enough already 🙄. Congrats on reinventing #Heroku but #open-source, because that's never been done before! 🎉"
    github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated

  26. "InsForge: because every coder needs another 'all-in-one' #platform to forget about 🤦‍♂️. Promising yet another #AI gateway, storage, and compute solution, because apparently, the world didn't have enough already 🙄. Congrats on reinventing #Heroku but #open-source, because that's never been done before! 🎉"
    github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated

  27. Hey, #Django devs who deploy (or used to deploy) stuff to #Heroku — are you looking at moving to some other #PaaS? If so, where to? Is there a standard, boring, dependable option that folks are gravitating toward?

  28. Hey, #Django devs who deploy (or used to deploy) stuff to #Heroku — are you looking at moving to some other #PaaS? If so, where to? Is there a standard, boring, dependable option that folks are gravitating toward?

  29. Hey, #Django devs who deploy (or used to deploy) stuff to #Heroku — are you looking at moving to some other #PaaS? If so, where to? Is there a standard, boring, dependable option that folks are gravitating toward?

  30. Hey, #Django devs who deploy (or used to deploy) stuff to #Heroku — are you looking at moving to some other #PaaS? If so, where to? Is there a standard, boring, dependable option that folks are gravitating toward?

  31. Hey, #Django devs who deploy (or used to deploy) stuff to #Heroku — are you looking at moving to some other #PaaS? If so, where to? Is there a standard, boring, dependable option that folks are gravitating toward?

  32. gotta love when #heroku changes their CLI on-the-fly and without warnings

    a few couple of hours ago I was able to filter the logs by using `--process-type=router`, the next time the option is gone. Why?

    it looks like #Salesforce really hate us.

  33. gotta love when #heroku changes their CLI on-the-fly and without warnings

    a few couple of hours ago I was able to filter the logs by using `--process-type=router`, the next time the option is gone. Why?

    it looks like #Salesforce really hate us.

  34. gotta love when #heroku changes their CLI on-the-fly and without warnings

    a few couple of hours ago I was able to filter the logs by using `--process-type=router`, the next time the option is gone. Why?

    it looks like #Salesforce really hate us.

  35. gotta love when #heroku changes their CLI on-the-fly and without warnings

    a few couple of hours ago I was able to filter the logs by using `--process-type=router`, the next time the option is gone. Why?

    it looks like #Salesforce really hate us.

  36. gotta love when #heroku changes their CLI on-the-fly and without warnings

    a few couple of hours ago I was able to filter the logs by using `--process-type=router`, the next time the option is gone. Why?

    it looks like #Salesforce really hate us.