RetroPie-Manager web app (Recalbox-Manager fork/mod)

wmcclelion

@wmcclelion Hah, needed to add :8000 to direct to the port. /blush

Ekstreme

WOW, I just came across this today, looking forward to giving it a try.
Myself, I can't see it getting used a lot, be people I've built PIs for sure will. What do you think about adding a virtual shell\console to it? I realise there is remote tools, but while you're in there....

Not sure how this would work, it's just an idea. I managed a lot of devices that do this, web based UI, then you can throw to a shell for more advanced work. Prob is, it's often java based and no one wants that

wmcclelion

I am loving this package. It makes managing my rom and bios sets a lot easier. I was wondering, would it be possible to add the ability to rename the files from the web app? I know I can do it via the Samba share or even directly from an SSH session, but it would be nice to be able to do it from the web page. Also, where is it pulling the file info when you upload? I used it to upload a Sega CD bios file and it told me it was a unsupported bios after the upload.

wmcclelion

Any future updates for the manager?

meleu

@wmcclelion sadly @Botolo seems to be very busy nowadays. And he is the webdevelopment guy...

robertybob

Has anyone tried to run this lately? I've just installed this and am getting an error:

"A server error occurred, please contact the administrator."

meleu

@robertybob did you installed using the RetroPie-Setup? If yes, can you paste the log somewhere? (I like ghostbin.com for pasting long files).

Pyjamarama

I have the exact same issue

"A server error occurred, please contact the administrator."

I have installed it via the RetroPie Setup

BuZz

I will look into it

robertybob

@meleu Sorry to come across like an idiot, but which log?

meleu

@robertybob look at your /home/pi/RetroPie-Setup/logs/ ;-)
The RetroPie-Setup logs are named as rps_TIME_STAMP.log.gz and are gziped, but you can read it with the zless command.

larryd85

@meleu said in RetroPie-Manager web app (Recalbox-Manager fork/mod):

/home/pi/RetroPie-Setup/logs/

i am running into the same problem
here is my log from trying to update the package through the retropie setup

http://pastebin.com/ZJv8UTFT

BuZz

Did you have it installed before? If so please try removing then re-installing as I changed the module install method which is incompatible with the old one when it was first added. I've not had a chance to look yet though if there is another issue.

BuZz

Installed fine here (and updated fine after). I suspect you just need to remove and reinstall - then it should be good for future upgrades.

larryd85

@BuZz i removed the package and then reinstalled it, here is the log from re-installing.
http://pastebin.com/UQcH4rkc
i still get "A server error occurred. Please contact the administrator." when i try to connect through chrome

BuZz

the install issue is different from that error. I am looking into that.

BuZz

The previous module installed the requisites system wide afair, and I changed it to not do this but to install correctly just in the install folder. I missed the fact that the rpmanager.sh doesn't initialise the python virtualenv - it will need the addition to do this.

source /opt/retropie/supplementary/retropie-manager/bin/activate before running. I'll fork it and do the code and submit a PR.

BuZz

I don't have more time to do this right now, so I will look further in a bit (unless someone else wants to have a go). I missed this when I converted the module, as it had already installed the requirements system wide. As this is a retropie module we want to be able to "remove" I changed that so it just needs adjusting to work via the virtualenv.

BuZz

Sorry, my mistake, the env was ok - I just thought it wasn't due to my debugging.

Looks like django security is at play in the current version

following changes sort it for me (to access via http://retropie:8000/)

see - https://docs.djangoproject.com/en/1.10/ref/settings/

Changed in Django 1.10.3:
In older versions, ALLOWED_HOSTS wasn’t checked if DEBUG=True. This was also changed in Django 1.9.11 and 1.8.16 to prevent a DNS rebinding attack.

and we use django 1.8.16 now.

so we will need to put the retropie name in here.

--- a/project/settings.py
+++ b/project/settings.py
@@ -39,7 +39,7 @@ SECRET_KEY = '(_0!&^^xekahfp=s5(9+^wlq6gvn6z90%i*p+wn^4ir+mvl4lx'
 # SECURITY WARNING: don't run with debug turned on in production!
 DEBUG = True
 
-ALLOWED_HOSTS = []
+ALLOWED_HOSTS = ['retropie']
 
 
 # Application definition

there may be a way to disable this check also.

detron

I appreciate the hard work that the people behind the scenes of RetroPie put into fixing issues.
I was just coming here to ask what I was doing wrong, but see others already had mentioned the same issue, and the fix is on the way!

bravo!