ojoaoguilherme
ojoaoguilherme
Explore posts from servers
PPrisma
Created by ojoaoguilherme on 10/18/2024 in #help-and-questions
Squashing migrations from Dev into Main
I have a production database and a development database which has different prisma models I want to squash my development migrations which I branched from production, I managed to do that on development but it reset my development database so I concerned I am going to loose all my data What is the correct flow of doing this, I am confused if I need to literaly delete manualy all my migrations or npx prisma migrate reset, any solutions?? I have to spin up this update max by monday, its a blocker for a feature we are releasing
2 replies
RRailway
Created by ojoaoguilherme on 9/18/2023 in #✋|help
Is it possible to host Unity project?
I have a unity game development project which runs C# Since I already use railway for my other projects I would like to host this unity as well, is it possible?
21 replies
RRailway
Created by ojoaoguilherme on 9/13/2023 in #✋|help
ReferenceError: FormData is not defined in Production
Hello, my codes are working fine on localhost, but when I push the codes to railway it throws this message when hitting the endpoint
24 replies
RRailway
Created by ojoaoguilherme on 8/23/2023 in #✋|help
I need help on deploying my development database to production without losing any data
I mistakenly ran the command npx prisma migrate dev on my production env but did not accept when the message says that it would result in resting the database Basically what I have been doing until now is developing all our backend and database migrations on a development branch and merging them in production branch and applying the migration to production env with npx prisma db push but know when I ran npx prisma migrate dev it would reset the database, and I am afraid of running npx prisma db push and not even give me the change of canceling if it resets my database this is the message
Drift detected: Your database schema is not in sync with your migration history.

The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.

It should be understood as the set of changes to get from the expected schema to the actual schema.

[+] Added tables
- profiles

[-] Removed tables
- ChallengeParticipant
- Dalahast
- Land

[*] Changed the `ChallengeVote` table
[+] Added column `message`

[*] Changed the `User` table
[-] Removed foreign key on columns (challengeParticipantId)
[-] Removed unique index on columns (email)
[-] Removed column `challengeParticipantId`
[-] Removed column `email`

[*] Changed the `profiles` table
[+] Added unique index on columns (email)
[+] Added unique index on columns (userId)
[+] Added unique index on columns (username)
[+] Added foreign key on columns (userId)

We need to reset the "public" schema at
Drift detected: Your database schema is not in sync with your migration history.

The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.

It should be understood as the set of changes to get from the expected schema to the actual schema.

[+] Added tables
- profiles

[-] Removed tables
- ChallengeParticipant
- Dalahast
- Land

[*] Changed the `ChallengeVote` table
[+] Added column `message`

[*] Changed the `User` table
[-] Removed foreign key on columns (challengeParticipantId)
[-] Removed unique index on columns (email)
[-] Removed column `challengeParticipantId`
[-] Removed column `email`

[*] Changed the `profiles` table
[+] Added unique index on columns (email)
[+] Added unique index on columns (userId)
[+] Added unique index on columns (username)
[+] Added foreign key on columns (userId)

We need to reset the "public" schema at
19 replies