Delete tables/databases on railway
How can I delete a table or reset my database on railway?
I want to re-migrate all my data.
29 Replies
Project ID:
75f448f4-88c9-4d82-b428-61740d90e40c
75f448f4-88c9-4d82-b428-61740d90e40c
I can create new tables, but i dont know how to delete existing ones
you want to wipe your entire database?
yes, delete all tables to migrate them again
wipe the volume then
but i dont want to remove the service because of the envs
i dont want to re-create the mysql image
cant I just drop the database?
yep, wipe the volume, this will give you a brand new database
how?
oh
that helps
tks
OH I LOST MY DATA
just kidding
lmao
thanks, Brody
in preparation of you saying something like this i had edited my above message to be clearer haha
hahaha
im facing a new issue
my healthcheck is not working for any reason
for the record we wouldnt have been able to do anything anyway
locally my route is working perfectly
the /health app route is working fine, returns a 200
oh I can mind what is happening
probably the service is not starting because I didnt set up a redis service on railway yet
imma try to fix this to see if this is the problem
yeah
connect ECONNREFUSED ::1:6379
this deploy hasnt started its web server so its not going to answer the health checkyeah, ive imagined, forgot about the redis
tks
hmmm redis connection still refused
but now ive configured the variables
yeah, econnrefused ::1.6379
looks like it cant connect to db
is this possible to connect via internal host?
redis.railway.internal
i've set my envs
REDIS_HOST
REDIS_PORT
REDIS_PASSWORD
is there anything I can do to connect redis in this cases?
you set the variables, but are you consuming them in code?
yes, sure
i saw this topic
https://docs.railway.app/guides/private-networking#known-configuration-requirements-for-ipv6
can this be the problem?
is this needed?
i dont know if that would be valid syntax, but given you are getting
econnrefused ::1.6379
im going to say no, that is not valid syntaxit is a valid syntax, locally it works with my redis
not necessarily, if it was valid your app would not be attempting to connect to
::1
thats a fallback hostname that indicates that the redis client is using its default values to attempt a redis connection, instead of using the REDIS_HOST
no its has nothing to do with the current errork got it
solved the problem here
all done
awsome, what was the issue
actually the lib's doc was wrong
you'll have that
the lib that integrates redis on nest
well, the last update was in 2022, its expected haha
makes sense, glad you got it fixed
tks for the help, Brody
no problem!