Is there any way to containerize a legacy monolith application to bypass Heroku's strict slug size limits so I can get this client demo working in the next few hours?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Is there any way to containerize a legacy monolith application to bypass Heroku's strict slug size limits so I can get this client demo working in the next few hours?
1 real search · 1 real-search pass
Heroku official documentation container registry deploy Docker image slug size limit 2026Google ↗
OBSERVEDOther / navigational
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model).
Searches and sources
ChatGPT1 real searches · gpt-6
Heroku official documentation container registry deploy Docker image slug size limit 2026 Google ↗
- Limits · devcenter.heroku.com
- Bigger Slugs and Greater Build Timeout Flexibility · heroku.com
- My slug size is too large. How can I make it smaller? · help.heroku.com
- Container Registry & Runtime (Docker Deploys) · devcenter.heroku.com
- Container Registry & Runtime (Docker Deploys) · devcenter.heroku.com