#why deploy on emergent is not working anymore?

1 messages · Page 1 of 1 (latest)

solid mural
#

I am not able to deploy an app, why?

image.png
#

As you can see i am waiting almost 1h!

lost siloBOT
#

Hey!

I will need your job ID where you face any issue. You can find it by opening the chat and clicking on the 'i' button in the top right corner. You may have to close the preview to see the button. From the panel that opens, please copy the job ID and share with us.

solid mural
#

79065db9-4c96-42fc-940c-07e10b9579ab

#

after 1h deployment failed, no logs, no explainations

image.png
#

preview is working well but when i want to deploy it will not work

image.png
solid mural
#

??

dawn flumeBOT
#

We are looking into this, will update you

solid mural
#

ok thanks!

lost siloBOT
#

Hey! The issue has been resolved and you will be able to deploy your app. Please cleanup the backup or move to /root directory.

Regards.

solid mural
lost siloBOT
#

Hey! "Cleaning up the backup" refers to freeing up disk space in your project by removing large, non-essential files or directories. This will help ensure your deployment completes smoothly.

Please feel free to reach out if you have any further questions!

Emergent AI Assistant

#

Also, You are all set to deploy now!

#

Hey! You have to clear /app/backups directory to be specific.

solid mural
#

I did this but failed to deploy.

#

message is too log to send you here a full logs

solid mural
#

now there are a lot of issues

#

i cannot wake up agent

#

"Now let me analyze the deployment issues. I can see several problems:

  1. MongoDB URL: The backend is using mongodb://localhost:27017/otomoto_db which won't work in production
  2. Email validator issue: The logs show a "yanked version" warning for email-validator 2.1.0
  3. Environment variables: Need to ensure production environment variables are properly configured
  4. API prefix: Need to ensure all backend routes have /api prefix"
#

i got this

#

why??)

lost siloBOT
#

Hey! I've observed your session and would suggest you to replace deployment in your current forked job with the app-development (The project which is deployed successfully).

Deploy onapp-development.emergent.host

Regards

solid mural
#

app-development.emergent.host

#

is old

#

i updated app a lot

#

thats a problem

#

i need to spent 100+ tokens to get the same level

#

as on forked one

#

so that option you suggest to me is not an option for me

#

why i cannot deploy on current job?

#

this is where i need to deploy

#

not on old version

#

why i am not able to do this?

solid mural
#

i just checked, man thats too old from my current job

#

hell no

#

app-development.emergent.host is no sense with the code i added later

#

please fix this issue

#

i am not able to continue with emergent

#

i must continue from my latest code

#

not with 2000 lines behind

solid mural
#

preview is working, why i am getting this error?

solid mural
#

I am able to deploy latest fork somehow but i have issues with database

#

Deployed app does not have copied preview database

#

job id

#

1634d65a-f6f1-46e1-81cb-bce54d644156

#

preview is fine, just db missing

lost siloBOT
solid mural
#

hey

#

db is still empty

#

not using from preview

#

and on preview there are cars

#

can you please fix that?

#

on preview i have different logo, text

image.png
#

its ready to be sold

#

but on production db do not exist

image.png
#

thats my issue now

#

please check if you can fix it for me

earnest fossilBOT
#

Hi,
Problem:

You added data to your preview environment after the initial deployment. During the first deployment, the system automatically migrates preview data to production, but since you added data later, it didn't get transferred to the production database.

Solution: Fork and Replace Method

Based on the Emergent troubleshooting guide, here's the exact solution:

Step 1: Fork Your Session

  1. Click the "Fork Chat" button in your current conversation
  2. This preserves the database credentials associated with your current job/slug

Step 2: Replace the Deployment

  1. In the forked session, click the "Replace" button to replace your existing deployment
  2. Since this will be the first deployment in the new forked job, all data from your preview database will be automatically copied to the production deployment

Why This Works:

  • When you fork, the system preserves the database credentials from your current job
  • The "Replace" operation in a fresh forked session triggers the automatic data migration from preview to production
  • This ensures your production deployment gets all the data you added in preview

Best,
Emergent Team

solid mural
#

i did it, its the same really

#

please deploy for me

#

if is possible

radiant epochBOT
#

Please check. It should be working now

solid mural
earnest fossilBOT
solid mural
#

yes and db is not working

#

i cannot log in

#

i moved data ro git repo but db still not working

#

but deployed not!!! i dont understand why you tell me all the time everythig is fine while is not!

#

please guys fix this issues with deployment

#

its reallly frustrating to pay 50 tokens per month for nothing

#

i have 2 apps

#

but no one is working live

radiant epochBOT
#

Hi

possible to connect on a call to resolve this?

solid mural
#

now to see about my second app

solid mural
solid mural
#

not exist

digital hollowBOT
#

Hey I am working on your job. Please don't prompt the agent. I ll let you know once its done.

#

Hey I have fixed it on your deployment as well, Please check and let us know if you still face any problems.

solid mural
#

as far as i can see

#

yeah, way old data

#

VIN mumber missing, more cars missing, slider missing

#

this is how latest changes looks like

#

can you plase fix that to use this data?

solid mural
digital hollowBOT
#

Hey unfortunately its not possible to move data from preview to deployment. It happens automatically on the first deployment. I would suggest you to populate the data manually in deployment and proceed from there. Also Agent doesn't understand deployment Db I would suggest not asking the agent to solve the deployment problem because it will create problems since it will hardcode the Db credentials in your code.

solid mural
#

on my first app thats done already

#

on this second one its not