#heroku — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #heroku, aggregated by home.social.
-
I think I triggered a #Heroku incident...
-
I think I triggered a #Heroku incident...
-
I think I triggered a #Heroku incident...
-
I think I triggered a #Heroku incident...
-
I think I triggered a #Heroku incident...
-
It's absolutely mindblowing what's possible today when you decide to self host your services, instead of trusting the big companies to do it.
When I got into #Django development some years ago, I soon discovered how nice and easy it was to host my projects on #Heroku. The CLI was nice and simple, there was no need to hand-roll complex config files, and I could even hook up GitHub so a push to main would automatically trigger a new Heroku deployment. It was so smooth and seamless, Heroku even had a free tier for small projects at the time so this was perfect.
Well, today Heroku is essentially on life support, the platform still exists and does what it always has done, but it's no longer being actively developed. So, for me this meant I'd have to find a good alternative eventually, and it looks like I've just discovered the right fit, #Dockhand.
This is a really nice web UI for managing Docker Compose stacks, and the really awesome thing about it is it totally supports Git deployments and authenticated web hooks so GitHub or other platforms can ping Dockhand when a new push has occurred. What's really neat also is Dockhand’s extensive support for push notifications, so I can set up notifications for when a deployment succeeds or fails, when any of my other containers have updates available, when a container is experiencing an issue, etc. Overall this seems really stable as far as I can tell, and new deployments happen much, much faster compared to Heroku. I’ll have to run some more tests to be completely sure, but so far this looks really, really solid and I’m extremely happy with this new setup.
#Selfhost #Docker #DevOps #Git -
It's absolutely mindblowing what's possible today when you decide to self host your services, instead of trusting the big companies to do it.
When I got into #Django development some years ago, I soon discovered how nice and easy it was to host my projects on #Heroku. The CLI was nice and simple, there was no need to hand-roll complex config files, and I could even hook up GitHub so a push to main would automatically trigger a new Heroku deployment. It was so smooth and seamless, Heroku even had a free tier for small projects at the time so this was perfect.
Well, today Heroku is essentially on life support, the platform still exists and does what it always has done, but it's no longer being actively developed. So, for me this meant I'd have to find a good alternative eventually, and it looks like I've just discovered the right fit, #Dockhand.
This is a really nice web UI for managing Docker Compose stacks, and the really awesome thing about it is it totally supports Git deployments and authenticated web hooks so GitHub or other platforms can ping Dockhand when a new push has occurred. What's really neat also is Dockhand’s extensive support for push notifications, so I can set up notifications for when a deployment succeeds or fails, when any of my other containers have updates available, when a container is experiencing an issue, etc. Overall this seems really stable as far as I can tell, and new deployments happen much, much faster compared to Heroku. I’ll have to run some more tests to be completely sure, but so far this looks really, really solid and I’m extremely happy with this new setup.
#Selfhost #Docker #DevOps #Git -
It's absolutely mindblowing what's possible today when you decide to self host your services, instead of trusting the big companies to do it.
When I got into #Django development some years ago, I soon discovered how nice and easy it was to host my projects on #Heroku. The CLI was nice and simple, there was no need to hand-roll complex config files, and I could even hook up GitHub so a push to main would automatically trigger a new Heroku deployment. It was so smooth and seamless, Heroku even had a free tier for small projects at the time so this was perfect.
Well, today Heroku is essentially on life support, the platform still exists and does what it always has done, but it's no longer being actively developed. So, for me this meant I'd have to find a good alternative eventually, and it looks like I've just discovered the right fit, #Dockhand.
This is a really nice web UI for managing Docker Compose stacks, and the really awesome thing about it is it totally supports Git deployments and authenticated web hooks so GitHub or other platforms can ping Dockhand when a new push has occurred. What's really neat also is Dockhand’s extensive support for push notifications, so I can set up notifications for when a deployment succeeds or fails, when any of my other containers have updates available, when a container is experiencing an issue, etc. Overall this seems really stable as far as I can tell, and new deployments happen much, much faster compared to Heroku. I’ll have to run some more tests to be completely sure, but so far this looks really, really solid and I’m extremely happy with this new setup.
#Selfhost #Docker #DevOps #Git -
It's absolutely mindblowing what's possible today when you decide to self host your services, instead of trusting the big companies to do it.
When I got into #Django development some years ago, I soon discovered how nice and easy it was to host my projects on #Heroku. The CLI was nice and simple, there was no need to hand-roll complex config files, and I could even hook up GitHub so a push to main would automatically trigger a new Heroku deployment. It was so smooth and seamless, Heroku even had a free tier for small projects at the time so this was perfect.
Well, today Heroku is essentially on life support, the platform still exists and does what it always has done, but it's no longer being actively developed. So, for me this meant I'd have to find a good alternative eventually, and it looks like I've just discovered the right fit, #Dockhand.
This is a really nice web UI for managing Docker Compose stacks, and the really awesome thing about it is it totally supports Git deployments and authenticated web hooks so GitHub or other platforms can ping Dockhand when a new push has occurred. What's really neat also is Dockhand’s extensive support for push notifications, so I can set up notifications for when a deployment succeeds or fails, when any of my other containers have updates available, when a container is experiencing an issue, etc. Overall this seems really stable as far as I can tell, and new deployments happen much, much faster compared to Heroku. I’ll have to run some more tests to be completely sure, but so far this looks really, really solid and I’m extremely happy with this new setup.
#Selfhost #Docker #DevOps #Git -
It's absolutely mindblowing what's possible today when you decide to self host your services, instead of trusting the big companies to do it.
When I got into #Django development some years ago, I soon discovered how nice and easy it was to host my projects on #Heroku. The CLI was nice and simple, there was no need to hand-roll complex config files, and I could even hook up GitHub so a push to main would automatically trigger a new Heroku deployment. It was so smooth and seamless, Heroku even had a free tier for small projects at the time so this was perfect.
Well, today Heroku is essentially on life support, the platform still exists and does what it always has done, but it's no longer being actively developed. So, for me this meant I'd have to find a good alternative eventually, and it looks like I've just discovered the right fit, #Dockhand.
This is a really nice web UI for managing Docker Compose stacks, and the really awesome thing about it is it totally supports Git deployments and authenticated web hooks so GitHub or other platforms can ping Dockhand when a new push has occurred. What's really neat also is Dockhand’s extensive support for push notifications, so I can set up notifications for when a deployment succeeds or fails, when any of my other containers have updates available, when a container is experiencing an issue, etc. Overall this seems really stable as far as I can tell, and new deployments happen much, much faster compared to Heroku. I’ll have to run some more tests to be completely sure, but so far this looks really, really solid and I’m extremely happy with this new setup.
#Selfhost #Docker #DevOps #Git -
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_).
-
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_).
-
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_).
-
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_).
-
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_).
-
🚨 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.
-
🚨 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.
-
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?
-
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?
-
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?
-
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?
-
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?
-
@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?
-
@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?
-
@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?
-
@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?
-
@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?
-
"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! 🎉"
https://github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated -
"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! 🎉"
https://github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated -
"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! 🎉"
https://github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated -
"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! 🎉"
https://github.com/InsForge/InsForge #InsForge #allinone #reinvented #HackerNews #ngated -
InsForge – Open-source Heroku for coding agents
https://github.com/InsForge/InsForge
#HackerNews #InsForge #OpenSource #Heroku #CodingAgents #CloudDevelopment
-
InsForge – Open-source Heroku for coding agents
https://github.com/InsForge/InsForge
#HackerNews #InsForge #OpenSource #Heroku #CodingAgents #CloudDevelopment
-
InsForge – Open-source Heroku for coding agents
https://github.com/InsForge/InsForge
#HackerNews #InsForge #OpenSource #Heroku #CodingAgents #CloudDevelopment
-
InsForge – Open-source Heroku for coding agents
https://github.com/InsForge/InsForge
#HackerNews #InsForge #OpenSource #Heroku #CodingAgents #CloudDevelopment
-
InsForge – Open-source Heroku for coding agents
https://github.com/InsForge/InsForge
#HackerNews #InsForge #OpenSource #Heroku #CodingAgents #CloudDevelopment
