sebastian® Posts - Answer Overflow

sebastian®

Explore posts from servers

•Created by sebastian® on 2/7/2024 in #✋｜help

Using my GitHub account on two different "paid" Railway accounts

I have one GitHub account with multiple projects that must be deployed in different Railway accounts. Both Railway accounts are paid. Why is it restricting me from adding my GitHub to the second Railway account, and how do I get around it? I have ZERO desire to setup a new GitHub account. Thanks for any help.

13 replies

RRailway

•Created by sebastian® on 1/31/2024 in #✋｜help

Prorated Billing on Last Day of Month

Hey Guys -- QUESTION ABOUT RAILWAY BILLING: I converted a trial account today (January 31st) an added a team member. Railway charged a prorated fee for today of $19.99 + $40 = $59.99. Does this seem correct to be billed a full fee for one day of service? If so, I would have waited a few hours until midnight. Or maybe I'm just misunderstanding the billing structure. Anybody know anything about this?

3 replies

RRailway

•Created by sebastian® on 6/19/2023 in #✋｜help

Puppeteer Deployment Issue

PUPPETEER DEPLOYMENT ISSUES -- I've seen a lot of chatter around various issues deploying Puppeteer, but nothing jumps out as a complete answer or example for deployment of the current versions. I'm seeing the deployment errors, below after setup in .puppeteerrc.cjs. I also tried nixpacks.toml described in various places but have since removed it after looking at a railway PR. NOTE: We are using Puppeteer for internal URL screenshot / image generation as it's proven most reliable for our requirement.

// .puppeteerrc.cjs
const { join } = require('path');

/**
 * @type {import("puppeteer").Configuration}
 */
module.exports = {
  cacheDirectory: join(__dirname, '.cache', 'puppeteer'),
};

// .puppeteerrc.cjs
const { join } = require('path');

/**
 * @type {import("puppeteer").Configuration}
 */
module.exports = {
  cacheDirectory: join(__dirname, '.cache', 'puppeteer'),
};

ERRORS:

#13 13.02 file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:278
#13 13.02                     throw new Error(`Could not find Chrome (ver. ${this.puppeteer.browserRevision}). This can occur if either\n` +
#13 13.02                           ^
#13 13.02
#13 13.02 Error: Could not find Chrome (ver. 114.0.5735.133). This can occur if either
#13 13.02  1. you did not perform an installation before running the script (e.g. `npm install`) or
#13 13.02  2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
#13 13.02 For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
#13 13.02     at ChromeLauncher.resolveExecutablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:278:27)
#13 13.02     at ChromeLauncher.executablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:174:25)
#13 13.02     at ChromeLauncher.computeLaunchArguments (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:91:37)
#13 13.02     at async ChromeLauncher.launch (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:57:28)
#13 13.02
#13 13.02 Node.js v18.12.1
#13 13.02
#13 13.03  ELIFECYCLE  Command failed with exit code 1.
 
#13 ERROR: process "/bin/bash -ol pipefail -c pnpm build" did not complete successfully: exit code: 1
-----
> [stage-0  9/11] RUN --mount=type=cache,id=s/d2f8a6b1-6a3d-46dc-9755-43c359214c26-node_modules/cache,target=/app/node_modules/.cache pnpm build:
#13 13.02  2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
#13 13.02 For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
#13 13.02     at ChromeLauncher.resolveExecutablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:278:27)
#13 13.02     at ChromeLauncher.executablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:174:25)
#13 13.02     at ChromeLauncher.computeLaunchArguments (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:91:37)
#13 13.02     at async ChromeLauncher.launch (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:57:28)
#13 13.02

#13 13.02 file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:278
#13 13.02                     throw new Error(`Could not find Chrome (ver. ${this.puppeteer.browserRevision}). This can occur if either\n` +
#13 13.02                           ^
#13 13.02
#13 13.02 Error: Could not find Chrome (ver. 114.0.5735.133). This can occur if either
#13 13.02  1. you did not perform an installation before running the script (e.g. `npm install`) or
#13 13.02  2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
#13 13.02 For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
#13 13.02     at ChromeLauncher.resolveExecutablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:278:27)
#13 13.02     at ChromeLauncher.executablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:174:25)
#13 13.02     at ChromeLauncher.computeLaunchArguments (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:91:37)
#13 13.02     at async ChromeLauncher.launch (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:57:28)
#13 13.02
#13 13.02 Node.js v18.12.1
#13 13.02
#13 13.03  ELIFECYCLE  Command failed with exit code 1.
 
#13 ERROR: process "/bin/bash -ol pipefail -c pnpm build" did not complete successfully: exit code: 1
-----
> [stage-0  9/11] RUN --mount=type=cache,id=s/d2f8a6b1-6a3d-46dc-9755-43c359214c26-node_modules/cache,target=/app/node_modules/.cache pnpm build:
#13 13.02  2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
#13 13.02 For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
#13 13.02     at ChromeLauncher.resolveExecutablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:278:27)
#13 13.02     at ChromeLauncher.executablePath (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:174:25)
#13 13.02     at ChromeLauncher.computeLaunchArguments (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:91:37)
#13 13.02     at async ChromeLauncher.launch (file:///app/node_modules/.pnpm/[email protected][email protected]/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:57:28)
#13 13.02

@Mafdet Did you ever get your deployment issue solved? If so, any guidance here?

61 replies

Gaming

Programming