Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Starter Kit - enterprise and it does not render #135

Open
Vukani351 opened this issue Jun 9, 2024 · 3 comments
Open

Running Starter Kit - enterprise and it does not render #135

Vukani351 opened this issue Jun 9, 2024 · 3 comments

Comments

@Vukani351
Copy link

Hi,

please help me figure out what's wrong with my starter kit project.

I am running it on windows 10 machine, I first ran npm install -g pnpm inside the enterprise folder then I ran npm run dev and it runs and shows a bunch of terminal logs - > success' but it never reaches the terminal log showing the host and port its running on "localhost:3001"

Screenshot 2024-06-09 070945

I also assumed its many the configs - but the configs in the .env file are the same as the ones on vercel and its working the but not locally -> this is what I have in the .env file:

NEXT_PUBLIC_HASHNODE_GQL_ENDPOINT=https://gql.hashnode.com
NEXT_PUBLIC_HASHNODE_PUBLICATION_HOST=vukanig.hashnode.com
NEXT_PUBLIC_MODE=development

If any one has suggestion on what could be blocking me please assist.

Highly appreciate it

@Harsh062
Copy link
Contributor

Thanks for reaching out and providing detailed information.

Based on your description, it seems the issue might be related to the configuration in your file, specifically the NEXT_PUBLIC_HASHNODE_PUBLICATION_HOST variable. The host vukanig.hashnode.com does not have a blog associated with it in our system. Instead, the correct host where your blog is available is vukanig.hashnode.dev.

Please update the NEXT_PUBLIC_HASHNODE_PUBLICATION_HOST in your configuration file to:

NEXT_PUBLIC_HASHNODE_PUBLICATION_HOST=vukanig.hashnode.dev

After updating the variable, save the file and restart your development server by running npm run dev again.
This change should ensure that your local environment correctly points to the appropriate host and allows the server to display the expected message.
If you continue to encounter issues or if this solution resolves your problem, please let us know.

@Harsh062
Copy link
Contributor

Hi @Vukani351 ,
I hope you're doing well.
I wanted to follow up on the above suggestion. I was wondering if you had a chance to review the proposed change or if there's anything more I can assist you with.
Please let me know if you have any questions or if there's any additional information you need. I'm here to help!
Looking forward to your response.

@jayantbh
Copy link

jayantbh commented Jul 19, 2024

Breaks for me in the same way.

I'm trying with the default config.

NEXT_PUBLIC_HASHNODE_GQL_ENDPOINT=https://gql.hashnode.com
NEXT_PUBLIC_HASHNODE_PUBLICATION_HOST=engineering.hashnode.com
NEXT_PUBLIC_MODE=development

I'm noticing that the next process exits with code 0. I wonder if that's related.

[next] next exited with code 0

I'm on MacOS, and Node 20.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants