How do I rollback an environment to before running the migration script?
I tried to use the database migration script in a project filled of 6 utility services. This included 2 database backup services and an uptime kuma service. I no longer can log into my uptime kuma services, it overwrote data in my backup services I think, and the only service that's working in this project now is a service that doesn't use a database and the main service that the project was created on (listmonk). I don't even know where Uptime Kuma's service was pointing to, as it must have had a database, but now because I can't log in, it looks like it's just gone. If I had the old database connection information, I would be able to figure this out. Can I see old environment variables or rollback the environment variables?
How do I roll back this change of the database migration script?
3 Replies