Closed 24tiptlo closed 1 year ago
I would also like to point out that https://website-aio-e9x.koyeb.app/ isn't working, as well as https://website-aio.herokuapp.com/. although, I can understand the herokuapp one is down because I heard they removed free dynos in issue #34
This has something to do with how we start Rammerhead. You have timed the issue to be 30 seconds, exactly the amount of time we wait before starting rammerhead.
This was fixed by listening on only one port, which requires running Rammerhead in the same process as the Bare server and the static webserver. ba030737b6a9dc323dcffbb5038cf81f927fce6d.
I would also like to point out that https://website-aio-e9x.koyeb.app/ isn't working, as well as https://website-aio.herokuapp.com/.
The service isn't active due to the Railway account's inactivity. We will need to use a combination of CI and self-hosting to demo website-aio. And yes, Heroku has removed free dynos, which would explain why our official Heroku deployment is down.
My deployment is on replit. For some reason, after clicking "Run", it would work completely fine for about 30 seconds where it would do two different things depending on what you were using:
On the Replit "Web View" window, it would display a blank white screen before showing the little replit robot and a loading bar.
On the actual webpage, it would stop loading certain things (like the twitter view, for example). And when you tried to refresh, it would try to awake the REPL.
sometimes on both, it would load multiple robots.
It should be noted that this happened after I updated the fork.
I have tried updating the dependencies using
npm update
as well asnpm audit fix
. I have also tried using one of my forks.I am however not getting many errors.
I say many because once, I got an error saying it couldn't find a 404.html, and another time I got an error about the bare server node, however I haven't been able to recreate them.