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

Automatically restore after the render platform is deployed #4609

Closed
2 tasks done
ohyoxo opened this issue Mar 21, 2024 · 13 comments
Closed
2 tasks done

Automatically restore after the render platform is deployed #4609

ohyoxo opened this issue Mar 21, 2024 · 13 comments
Labels
area:deployment related to how uptime kuma can be deployed help question Further information is requested

Comments

@ohyoxo
Copy link

ohyoxo commented Mar 21, 2024

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Automatically restore after the render platform is deployed

The database is set up, but it will still be restored to its original state

image

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

2.0.0-dev

💻 Operating System and Arch

Render

🌐 Browser

Google Chrome

🖥️ Deployment Environment

  • Runtime:
  • Database:
  • Filesystem used to store the database on:
  • number of monitors:
@ohyoxo ohyoxo added the help label Mar 21, 2024
@ohyoxo ohyoxo changed the title Automatically restored after successful render deployment Automatically restore after the render platform is deployed Mar 21, 2024
@CommanderStorm CommanderStorm added the area:deployment related to how uptime kuma can be deployed label Mar 21, 2024
@CommanderStorm
Copy link
Collaborator

Note

v2.0 is not ready yet, see #4500 for further context on what needs to be done to get to said state.
Please don't use it until it is stable or expect to be impacted by breaking bugs.

You can use our isntallation guide to install a stable version:
https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install

For your issue it is quite unclear what you mean with

Automatically restore after the render platform is deployed

Restore from where?

@CommanderStorm CommanderStorm added the question Further information is requested label Mar 21, 2024
@ohyoxo
Copy link
Author

ohyoxo commented Mar 21, 2024

For your issue it is quite unclear what you mean with

Automatically restore after the render platform is deployed

Restore from where?

After successfully deploying and registering, the login information will be deleted after a few hours and will be restored to the registration page.

@CommanderStorm
Copy link
Collaborator

So basically, your cloud provider is not persisting the database. Am I taking this correctly?

Could you please report all the details we asked in above form (Error Message(s) or Log,Deployment Environment)? It is really hard to remote-debug if don't.
Could you also please share the exact way you are deploying on render?

@chakflying
Copy link
Collaborator

Render would automatically shutdown idle web services after some delay for the Free tier. Most likely configuration is lost because of this.

https://docs.render.com/free#spinning-down-on-idle

@CommanderStorm
Copy link
Collaborator

That sounds very much like it. => closing as resolved.
Feel free to reopen if it is not

@ohyoxo
Copy link
Author

ohyoxo commented Mar 22, 2024

Render would automatically shutdown idle web services after some delay for the Free tier. Most likely configuration is lost because of this.Render 将在免费层延迟一段时间后自动关闭空闲 Web 服务。很可能因此而丢失了配置。

https://docs.render.com/free#spinning-down-on-idle

I have connected an external database in the environment variables, and the situation is the same.

@ohyoxo
Copy link
Author

ohyoxo commented Mar 22, 2024

So basically, your cloud provider is not persisting the database. Am I taking this correctly?因此,基本上,您的云提供商不会持久化数据库。我做对了吗?

Could you please report all the details we asked in above form (Error Message(s) or Log,Deployment Environment)? It is really hard to remote-debug if don't.您能否报告我们在上面表格( Error Message(s) or LogDeployment Environment )中询问的所有详细信息?如果不这样做,真的很难进行远程调试。 Could you also please share the exact way you are deploying on render?您能否分享一下您在渲染上部署的确切方式?

There were no error logs, the deployment was successful. The deployment method was simply importing the repository, keeping other settings as default, and then deploying.

@CommanderStorm
Copy link
Collaborator

What is your exact environment? (redacting secrets)

@CommanderStorm
Copy link
Collaborator

There were no error logs

What are the logs of uptime kuma?
I somewhat doubt that there are no logs.

keeping other settings as default

When I was asking about the Deployment Environment, I was specifically asking what you consider those defaults.
Remember that I don't use render => don't know what these defaults are…

@ohyoxo
Copy link
Author

ohyoxo commented Mar 22, 2024

There were no error logs

What are the logs of uptime kuma? I somewhat doubt that there are no logs.

keeping other settings as default

When I was asking about the Deployment Environment, I was specifically asking what you consider those defaults. Remember that I don't use render => don't know what these defaults are…

image
image
image
This is the settings and Log that I deployed, and I didn't see an error when logging in before

@chakflying
Copy link
Collaborator

The correct environment variable names (note that these are undocumented and unstable):

UPTIME_KUMA_DB_TYPE=mariadb
UPTIME_KUMA_DB_HOSTNAME=<your-database-hostname>
UPTIME_KUMA_DB_PORT=3306
UPTIME_KUMA_DB_NAME=<your-database-name>
UPTIME_KUMA_DB_USERNAME=<your-database-username>
UPTIME_KUMA_DB_PASSWORD=<your-database-password>

@ohyoxo
Copy link
Author

ohyoxo commented Mar 22, 2024

The correct environment variable names (note that these are undocumented and unstable):

UPTIME_KUMA_DB_TYPE=mariadb
UPTIME_KUMA_DB_HOSTNAME=<your-database-hostname>
UPTIME_KUMA_DB_PORT=3306
UPTIME_KUMA_DB_NAME=<your-database-name>
UPTIME_KUMA_DB_USERNAME=<your-database-username>
UPTIME_KUMA_DB_PASSWORD=<your-database-password>

OK,I will try
Thx

@CommanderStorm
Copy link
Collaborator

I think the issue for using the development builds (not alpha/beta) of uptime kuma is resolved with this.
We can reopen if this is not the case ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:deployment related to how uptime kuma can be deployed help question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants