-
Notifications
You must be signed in to change notification settings - Fork 230
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
Demo site and API down #75
Comments
Exactly!!! Any update on this?? Can you kindly let us know whether you intend to revive this API? Thank you 🙇 !!! |
??? |
Hi 👋
Heroku deprecated the stack we were using. We will try to revive in the
following days.
In any case a new version is ready for deploy and working the last details.
I expect it will be
Alive again until tomorrow.
On Mon, 5 Dec 2022 at 00:44, nynewco ***@***.***> wrote:
… ???
—
Reply to this email directly, view it on GitHub
<#75 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABRAELH6OCSXIW6Q4L7O3LWLUUEPANCNFSM6AAAAAASRACSEY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thank you 🙇 |
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you visit http://yake.inesctec.pt/ you just see:
Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command
heroku logs --tail
The text was updated successfully, but these errors were encountered: