badrihippo

Ahh. That's one point to keep in mind!

From what I can make out, the email addresses linked to Tommy are used for downloading backups. Does that mean we should create our temporary Ricky accounts using a different email address (and possibly change it back once the whole thing is cleared up)?

There's a thread here, where I presume they'll post updates when they get them: https://www.helionet.org/index/topic/36440-tommy-downtime/

OK I got this from another thread: I guess that answers my question. I suppose you'll have to finish backing up everyone's data before repairs can even start?

Any updates on Tommy? Is there some issue with the data storage, or something?

I'm trying to upload a bunch of files for my website. Since FTP takes a long time for multiple small files, I'm thinking of using a zipfile so I can do them all at one go. I remember this "Upload as ZIP" option used to be available from the cPanel FileManager, but now I can't find it anywhere. Any idea where it is?

I can confirm this is possible; I've done it several times for my site for both Flask and Django. Rough steps: Remove all *.pyc files from your local Python package (or better, virtualenv) directory. This will usually look like [env directory or /usr]/lib/python[X.X]/site-packages/Upload the contents of aforementioned site-packages directory to a folder on the server (let's call it myenv)Add the lines import sys sys.path.insert(0, '/path/to/myenv')to the beginning of your script file If all goes well, your script should now be able to import libraries from your uploaded folder. Caveat: this works well for pure-Python libraries. For others, it'll only work if your system is compatible with your HelioHost server's architecture/setup.

I just found the automated status and renewal pages (https://heliohost.org/status/?u=hippo), and have submitted a request there. So I guess you can ignore this post. Sorry for troubling you

I just realised my account's been suspended. Could you reactivate it, please? Username: hippo Server: tommy It's probably my fault, I think I missed a monthly login. But if there's any other reason do let me know.

I can sign in now, after resetting the password. Thanks a lot

I signed up for a Tommy account this midnight (3 March 2017 at about 00:00 GMT) but haven't been able to sign in yet. When I signed up, I got the confirmation message saying "you might need to wait for your account to be activated" but I don't remember how long that wait was. But the Account Status page is still saying "There is no account in our database that matches that [username/email].", depending on which I try, and I am not able to log in either. It's been about 11 hours now. Do signups usually take this long? Or is there something else I have to do? Username: hippo Domain: hippo.heliohost.org(I had a previous account on Stevie with the same username but a different domain, if that makes a difference. Also, I clicked on the email confirm link a bunch of times before the actual signup)

Makes sense. About deleting the oldest unused information, I mean. Just to let you know—I downloaded the backup, and have actually recovered all the files! I didn't expect to get all of them back—though this has taught me to be more regular about taking backups in the future. Now to set up my new account. I'm actually looking forward to building my new /home on Tommy. To second nuk, thanks for running this great service!

Thanks. Is there a deadline for downloading the backup? Can I afford to wait till the beginning of next month (Feb)?

Another request to free up a Stevie account! username: hippo domain: sss.heliohost.org extra domains: sssnet.tk, *.sssnet.tkI haven't managed a Tommy donation yet, but I'd like the account freed up so I can sign up as soon as I can manage. Also, I had requested a recovery attempt for some directories in my old home folder (/home1/hippo). Will the account deletion affect this in any way?

Hi, This is related to the Stevie server crash. I got an automatic backup of my files from the backup page; however this only contains backups for the /public_html directory. I have most of my server scripts in external directories; would it be possible to recover those as well? My username is hippo (/home1/hippo on the server), and the directories I need are: /django /databasesRecovery of the following directories would be nice, but is not so urgent: /pyenvs /pymodulesThanks in advance, and good luck with the backups!

What I do is to upload the whole Django source folder (whichever version you want) to the HelioHost server, eg. /home/[username]/pyenvs/django. Then I add that directory to sys.path in the dispatch.wsgi file: sys.path.insert(0, '/home/[username]/pyenvs') I use the same method to add any other Python libraries I want to use.

Here's the post I made on how to set up Django 1.5; I think you could follow the same instructions for Django 1.4 as well: helionet.org/index/topic/17025-successfully-runnig-django-151-on-heliohost/

I created a website using Django 1.5, and I managed to get it running on HelioHost! Here's what I did, after following the instructions at http://www.heliohost...anguages/python... First, I downloaded the Django-1.5.1.tar.gz file from the Django website. Then, I extracted it and uploaded the Django-1.5.1/django/ folder to /home/username/django_1.5_override/django. I also created an empty __init__ file in /home/username/django_1.5_override, to tell Python that it could import stuff from here. I'm not sure if it's needed, though. I then added a few lines to the dispatch.wsgi file; the modifications are in the first 3 lines: import os, sys oldpath = sys.path sys.path = ['/home/username/django_override/django-1.5.1/'] + oldpath sys.path.append("/home/username/myapp"); os.environ['DJANGO_SETTINGS_MODULE'] = 'myapp.settings' os.environ['PYTHON_EGG_CACHE'] = '/home/username/.python_egg_cache' import django.core.handlers.wsgi _application = django.core.handlers.wsgi.WSGIHandler(); def application(environ, start_response): environ['PATH_INFO'] = environ['SCRIPT_NAME'] + environ['PATH_INFO']; try: # added so that I can see errors if they occur; should be removed once the website is fully functional return _application(environ, start_response) except Exception, e: import traceback trace = traceback.format_exc() status = '500 Internal Server Error' output = trace response_headers = [('Content-type', 'text/plain'),('Content-Length', str(len(output)))] start_response(status, response_headers) return [output] Basically, what I did was to add the Django 1.5.1 folder to the beginning of sys.path, so that when Python needs to import django, it imports my uploaded one instead of the default one. After following these steps, Django 1.5.1 is running perfectly, and I can make use of all the new features!

You don't need to switch! I just figured out a way to run Django 1.5 in my HelioHost account . I'll start another topic on that and then get back to you here...