You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem was first reported as App deployment getting stuck at pushing image to fly. The problem was determined to be that the storage directory was being uploaded making the image too big. The identified solution was to remove two lines
# Ignore pidfiles, but keep the directory.
/tmp/pids/*
-!/tmp/pids/ # <-- bug: This line should be deleted, is basically making the previous line useless, all files inside /tmp/pids are being sent to the context
!/tmp/pids/.keep
# Ignore storage (uploaded files in development and any SQLite databases).
/storage/*
!/storage/.keep
/tmp/storage/*
-!/tmp/storage/ # <-- bug: This line should be deleted, is also making the previous line useless, all files inside /tmp/storage are being sent to the context. This directory had 5.5 GB of data in my case.
!/tmp/storage/.keep
The text was updated successfully, but these errors were encountered:
rubys
added a commit
to rubys/rails
that referenced
this issue
Sep 9, 2023
Steps to reproduce
Expected behavior
No
server.pid
in the containerActual behavior
server.pid
file exists in containerSystem configuration
Rails version:
--main
Ruby version:
ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]
Additional information
The problem was first reported as App deployment getting stuck at pushing image to fly. The problem was determined to be that the storage directory was being uploaded making the image too big. The identified solution was to remove two lines
The text was updated successfully, but these errors were encountered: