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

chore: update org name #61

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: update org name #61

wants to merge 1 commit into from

Conversation

Readpato
Copy link
Member

It's me again, changing the repo name

Copy link

netlify bot commented Oct 31, 2024

Deploy Preview for clever-sopapillas-765a45 failed. Why did it fail? →

Name Link
🔨 Latest commit
🔍 Latest deploy log https://app.netlify.com/sites/clever-sopapillas-765a45/deploys/673df4e3bd0ffbd36a1e7f3e

@Readpato Readpato requested review from TheJoin95 and Wabri October 31, 2024 13:19
@Readpato Readpato self-assigned this Oct 31, 2024
@Readpato
Copy link
Member Author

@Wabri @TheJoin95 Build is failing because it's apparently pointing at wrapped.schrodinger-hat.it do we have to update that directly from Netlify options?

image

@Wabri
Copy link
Member

Wabri commented Oct 31, 2024

Yes, everything domain related is ok, but maybe we miss to update it in netfify! Tomorrow I'll have my personal pc and I'll take a look into it.

@Readpato
Copy link
Member Author

@Wabri reminder over here

@TheJoin95
Copy link
Member

TheJoin95 commented Nov 20, 2024

Are you able to run the build locally?
Maybe we need to refresh the yarn.lock with the good addresses as it's pretty old and it's using node16

@Wabri
Copy link
Member

Wabri commented Nov 20, 2024

There was the production domains outdated, I've change the primary with the .org domain, but the problem is with .next directory that is not created in the building step i guess

@Wabri
Copy link
Member

Wabri commented Nov 20, 2024

@Readpato have you try to build locally? does the .next directory been created?

@TheJoin95
Copy link
Member

The primary domain is just a label in netlify, it was not affecting the build nor the org domain visibility;
I believe it requires an npm install, it'll refresh the .lock, then you'll able to deploy it (I believe)

@Readpato
Copy link
Member Author

Readpato commented Nov 20, 2024

If it changes something, I can run the build locally and execute the server

PS: we should think about updating the node version

image

@TheJoin95
Copy link
Member

Try to do a fresh install: I suspect some packages are being updated

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

Successfully merging this pull request may close these issues.

3 participants