When loading homepage, default homepage shows up for a short moment

[ManiMatter]

Description

When I open my homepage, it shows the unconfigured homepage for a short moment (1sec or so)

Just a moment later, the real homepage starts to show.

Rather than the unconfigured website with placeholders, I'd expect a loading icon or a empty page to show while it is still loading.

Steps to reproduce

Refresh the page

homepage version

0.7.3

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

n/a

Other

No response

Before submitting, I have made sure to

• Check the documentation
• Follow the troubleshooting guide (please include output above if applicable).
• Search existing issues and discussions.

[shamoon]

In general there is no known issue here, I don’t really know if you’re describing the normal behavior, but I think so. There is a loading period as the app reprocesses loads your configs but otherwise should be instantaneous

[benphelps]

This display only happens once after updating the image or installing fresh. What you're seeing is the build-time configuration of the static site, on first visit the config will be reloaded and the site built again, then the page automatically reloaded. You will not see this build-time version again until you update the container version.

[ManiMatter]

First of all, thanks for the awesome app @benphelps !

You may be right that this only happens when the container reloaded freshly or updated; I tried force reloading the page several times and could not reproduce it.

Question, why does homepage wait till a user logs into the homepage for a first time until the configuration is built? If that is what results in the user seeing the default homepage quickly, coulnd't that be avoided by the configuration being built when the container starts? Then, when a user logs in, the homepage would already be ready.

Or is there a catch to this?

[benphelps]

If there is a mechanism that would allow for the Docker image to make a one-off API request to the refresh endpoint, it would be possible.

[ManiMatter]

Just thinking out aloud; couldn't that be done with calling the API at the end of the dockerfile? Ie. adding a call there (sh or py script, for example)?

ENTRYPOINT ["docker-entrypoint.sh"]
CMD ["node", "server.js"]

[schklom]

Even something a HEALTHCHECK wget http://localhost:3000 would do the trick by calling the API.

[ManiMatter]

@benphelps - which one is the specific API endpoint that needs to be called so that the one-off refresh is triggered?

I think we would solve this by adding a "fetch" call right after the following code in server.js
console.log("Listening on port", currentPort)

[schklom]

@benphelps I think replacing

homepage/Dockerfile

Lines 65 to 66 in 986a181

	ENTRYPOINT ["docker-entrypoint.sh"]
	CMD ["node", "server.js"]

with

ENV TIME_TO_START 10
ENTRYPOINT ["/bin/sh -c 'sleep $TIME_TO_START && curl localhost:$PORT &;", "docker-entrypoint.sh"]
CMD ["node", "server.js"]

might work, basically set curl localhost:$PORT to execute in the background after 10 seconds, and start the server code in the meantime.

Is there a better way to load the page once at the start? Maybe a particular API call, but would that even be necessary?

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.