chore: remove console log statements from WebSocket connection handling and ensure builder container for Railpack is created

This commit is contained in:
Mauricio Siu
2025-03-15 20:42:53 -06:00
parent 005f73d665
commit 31164c9798
2 changed files with 4 additions and 2 deletions

View File

@@ -61,7 +61,6 @@ export const setupDeploymentLogsWebSocketServer = (
} }
stream stream
.on("close", () => { .on("close", () => {
console.log("Connection closed ✅");
client.end(); client.end();
ws.close(); ws.close();
}) })
@@ -86,7 +85,6 @@ export const setupDeploymentLogsWebSocketServer = (
}); });
ws.on("close", () => { ws.on("close", () => {
console.log("Connection closed ✅, From WS");
client.end(); client.end();
}); });
} else { } else {

View File

@@ -131,6 +131,10 @@ export const getRailpackCommand = (
buildArgs.push(buildAppDirectory); buildArgs.push(buildAppDirectory);
const bashCommand = ` const bashCommand = `
# Ensure we have a builder with containerd
docker buildx create --use --name builder-containerd --driver docker-container || true
docker buildx use builder-containerd
echo "Preparing Railpack build plan..." >> "${logPath}"; echo "Preparing Railpack build plan..." >> "${logPath}";
railpack ${prepareArgs.join(" ")} >> ${logPath} 2>> ${logPath} || { railpack ${prepareArgs.join(" ")} >> ${logPath} 2>> ${logPath} || {
echo "❌ Railpack prepare failed" >> ${logPath}; echo "❌ Railpack prepare failed" >> ${logPath};