railwayapp / blog Goto Github PK

When building the project it gives the following error. Don't know why this is happening but the env value for POSTS_TABLE_ID has hyphens that I didn't put in the env.

APIResponseError: Could not find database with ID: 2369f90d-f8ac-****-ba**-b14******200. Make sure the relevant pages and databases are shared with your integration.

The Database ID shown in the error message is: 2369f90d-f8ac-****-ba**-b14******200 where as the one that I provided in the env is: 2369f90df8ac****ba**b14******200

After following all of the steps in the tutorial, I'm getting this error:

> Build error occurred
 
TypeError: Cannot read properties of undefined (reading 'date')
at /workspace/.next/server/chunks/490.js:32:50
at Array.filter (<anonymous>)
at getDatabase (/workspace/.next/server/chunks/490.js:32:20)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getStaticPaths (/workspace/.next/server/pages/p/[slug].js:515:19)
at async buildStaticPaths (/workspace/node_modules/next/dist/build/utils.js:497:31)
at async /workspace/node_modules/next/dist/build/utils.js:640:119
at async Span.traceAsyncFn (/workspace/node_modules/next/dist/trace/trace.js:75:20) {
type: 'TypeError'
}
 
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
 
error Command failed with exit code 1.
 
ERROR: failed to build: exit status 1
 
ERROR: failed to build: executing lifecycle: failed with status code: 51

If for whatever reason my table has any errors, feel free to check it out here: https://n3rd3x3.notion.site/f1faacfd89bd45ce888b5e335245a176?v=7062f5b173344f50bda90c1dda1ba70c

If you don't have a field in the database called "Description" you'll get an error on deployment.

"TypeError: Cannot read properties of undefined (reading 'rich_text')"

Other required fields are:

Featured: checkbox
FeaturedImage: text
Category: selection or tags or something? I just renamed the default Tags field to Category

That at least gets it to build and deploy.

There's a lot of work one needs to do after this to clean it all up.

The readme says Image and FeaturedImage should be of type text but the code seems to say otherwise.

export const FeaturedPostItem: React.FC<{ post: PostProps }> = ({ post }) => {
  const formattedDate = useMemo(
    () =>
      dayjs(new Date(post.properties.Date.date.start)).format("MMM D, YYYY"),
    [post.properties.Date.date.start]
  );

  const author = post.properties.Authors.people[0];
  const category = post.properties.Category.select?.name;
  const featuredImage = post.properties.FeaturedImage.url;

Once I have changed type of FeaturedImage from text to url in my notion db, it started to display on my blog.
I suggest just update the README.md

Hi there, apologies for posting this random question here, but I was curious about how you overcame the issue for rendering images hosted on Notion and also using next/image for optimisation? (As I myself ran into a similar problem when switching to Notion's public API for blog hosting.)

• The problem I ran into was that Notion's public API responds with URLs of images hosted on Notion that are short-lived - they would expire after a certain amount of time (seems to be 1 hour).
• This means that there would exist a possible time span where ISR is still revalidating but the images have already expired, resulting in broken images for visitors accessing the site during this particular time - and I've personally ran into this for a couple of times over on my site.
• It also implies that next/image would have to optimise a whole lot of images with different URLs while they are still the same one in reality - leading to an email from Vercel telling me that I have gone over my limit for image optimisation.

It was not until Next.js 12.1 (released literally yesterday) before we could on-demand ISR with webhooks (On-demand Incremental Static Regeneration). So I was curious about if you had some solutions to this issue without on-demand ISR?

My workaround was that I had to resort to using getServerSideProps without image optimisation for serving fresh images. But I skimmed through your repo and found that you were still using getStaticProps, and hence this question ;)

And thanks for the awesome railway.app, I'm loving it!

Post: https://blog.railway.app/p/nx-railway-with-gh-actions

Right about the end of the post the following is written

Deploy affected step which triggers the railway-trigger.sh script shared below.

The link railway-trigger.sh does not resolve, because it was not linked to the correct file,
which would be this one: https://github.com/IgnisDa/npm-libs/blob/main/deployment/railway-trigger.sh

Hi team, getting the following build error:

Cannot read properties of undefined (reading 'rich_text'). seem to have to do with the slug (which I have set up as "text" inside Notion as per the tutorial.

TypeError: Cannot read properties of undefined (reading 'rich_text')
at /app/.next/server/chunks/490.js:32:91
at Array.filter (<anonymous>)
at getDatabase (/app/.next/server/chunks/490.js:32:20)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async getStaticPaths (/app/.next/server/pages/p/[slug].js:515:19)
 at async buildStaticPaths (/app/node_modules/next/dist/build/utils.js:497:31)
at async /app/node_modules/next/dist/build/utils.js:640:119
at async Span.traceAsyncFn (/app/node_modules/next/dist/trace/trace.js:75:20) {
type: 'TypeError'
}
error Command failed with exit code 1.