You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Do you plan to solve this?
The text was updated successfully, but these errors were encountered:
This is an issue I've been meaning to deal with but haven't had time to get round to it yet. Heroku removed their free tier option and the app was deleted from their servers. We have a few options to deal with this:
Remove the Heroku app from the repo and just leave the version that runs on the RFSoC board.
Remove the Heroku app from the repo and replace it with an app that will run on a computer.
Start paying for a Heroku paid subscription tier.
I don't have time at the moment to action this, but I'll revisit it in a couple of weeks. If anyone has any more suggestions, or have a preference to the options I listed above, then feel free to chime in.
From my side, It would better to replace de Heroku app and modify it to be runned on a compute EVEN WITHOUT a RFSoC board, since it can be interesting to make analysis previously to pruchase one board.
The frequency planner can execute on a computer with Anaconda/Jupyter Lab installed. Just run the pip3 command, and the notebooks will appear in the Jupyter working folder. We will decide on Heroku shortly.
I tried the link of the readme: https://rfsoc-frequency-planner.herokuapp.com/
but the online web app is not working. The following message appears:
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
Do you plan to solve this?
The text was updated successfully, but these errors were encountered: