Krydos

Yeah, no problem. We all would appreciate it if you could create a wiki account at http://wiki.helionet.org/ and create a tutorial for people to do what you have just done. This would be especially useful for people if you use windows on your home pc since most people use that os. I find it makes more sense to people from the point of view of another user such as yourself. You could use http://wiki.helionet.org/Java_Servlet http://wiki.helionet.org/Installing_an_SSL_Certificate_on_Tommy_with_ZeroSSL or http://wiki.helionet.org/Running_Auto_Backups as templates.

Oh yeah, one other thing. The command django-admin startproject command creates your settings.py file with ALLOWED_HOSTS = [] Django on Tommy will report an error unless you specify your domain or use a wildcard there. ALLOWED_HOSTS = ['*'] Specifying an exact domain will be more secure, but for the future people who may read this the * will work for all of your websites.

Yeah, of course you can. The reason I did a structure like I did is because I started with our old djangotest.zip file which was originally created with like django 1.2 or something ancient, and adapted it to work with the newest django 1.10 that I installed. I'm guessing that's how the django-admin startproject command did things back then, but you're right that command has a very different structure in the latest version. Using python 3.6 and django 1.10 on my home computer I created a project called hello which looks like this /hello/ /db.sqlite3 /manage.py /hello/ /__init__.py /wsgi.py /settings.py /urls.py Obviously it doesn't work, as you found out already, if you just upload it like that. So we need to make a few changes. The most important things are the .htaccess to force django to process the files, and the .wsgi file that ties it all together. So on the server it looks like this so far: /public_html/ /db.sqlite3 /.htaccess /hello/ /__init__.py /dispatch.wsgi <----- simply wsgi.py renamed /settings.py /urls.py And the code for the .htaccess is this RewriteEngine On RewriteBase / RewriteRule ^(media/.*)$ - [L] RewriteRule ^(admin_media/.*)$ - [L] RewriteRule ^(hello/dispatch\.wsgi/.*)$ - [L] RewriteRule ^(.*)$ hello/dispatch.wsgi/$1 [QSA,PT,L] Obviously, the last two lines replace "hello" with whatever the name of your project is. This still won't work though because the wsgi.py/dispatch.wsgi file doesn't have the paths correct for running on the production server yet. Here is what django-admin created import os from django.core.wsgi import get_wsgi_application os.environ.setdefault("DJANGO_SETTINGS_MODULE", "hello.settings") application = get_wsgi_application() This is what I changed it to which works both locally and on Tommy import os, sys # edit your username below sys.path.append("/home/krydos1/public_html") from django.core.wsgi import get_wsgi_application os.environ['DJANGO_SETTINGS_MODULE'] = 'hello.settings' application = get_wsgi_application() Now, when you make a change to wsgi.py locally also copy it to dispatch.wsgi before you upload it. Here is my test case with the django project running on the root of the domain (instead of in a folder like on my main account). http://krydos1.heliohost.org/

Mono is installed for SSL now too https://www.laparcela.tk/aspa/index.aspx

Well, I made some progress on it, but now it looks like it's having some path related issues: http://sest.gq/ At least it's throwing helpful errors now instead of useless 500 errors.

@byron that was the reason /home/albertoc/public_html/djangotest/.htaccess was throwing a 500 error yesterday. He has fixed that and I was explaining why /home/albertoc/public_html/.htaccess was throwing a 500 error today which is the file you renamed. @albertoc there are a couple things going on here. First of all manage.py is pointless to upload since you don't have shell access so you may as well delete that to reduce the chance of security holes. Second since this isn't a dedicated django server the structure of your application is going to need to be a little different. On a dedicated django server like your application is set up to run on everything other than the media directory would be processed through mod_wsgi, but this is a shared server and the hundreds of other people sharing the server with you don't want the performance hit of everything being processed twice like that. The .htaccess rules is how you specify that you want things to be processed through your dispatch.wsgi file. In your application this is called wsgi.py, but it won't run like that because not all .py files on the server necessarily have to be django files. I have it set up so everything with the extension .wsgi is processed as django. Any other extension will not be processed through mod_wsgi. This is the key to tying the whole thing together. Simply renaming that file and setting up the proper rules in .htaccess so everything is processed correctly through the .wsgi file should be enough to get you going. I messed around with your files for a bit, but I can't get it working either and I've run out of time for now. I'll be back to fiddle with it some more later.

@byron, What the .htaccess file does on a django site in this example is force everything (other than static files in the media folder) to be processed through dispatch.wsgi. That's what ties the whole thing together as django rather than seperate html files etc. If the django site itself has a 500 error renaming the .htaccess just makes the django not process at all. @albertoc, the 500 error is because (as I explained about) /home/albertoc/public_html/.htaccess is trying to send all requested to be processed by /home/albertoc/public_html/dispatch.wsgi but that file doesn't exist.

It's not possible, but other people have requested it too https://features.cpanel.net/topic/multiple-cpanel-logins-cpanel-subusers Depending on what you need your subuser to be able to do you could just create them an FTP account so they can access or modify the files on your site. You can even set it up so one account only has access to one domain and another account only has access to another domain if you're account has more than one website on it.

You should have access to edit the wiki now. Let us know if you have any questions or would like us to review your changes and additions.

We hadn't installed Django on Tommy yet because no one had asked for it. Since you asked, Django 1.10.5 is now installed on Tommy running on Python 3.6.0. To get started download https://www.heliohost.org/assets/djangotest.tar.gzUpload this archive to /home/<USERNAME>/public_htmlExtract the archive and it will create a djangotest directory in public_htmlEdit djangotest/dispatch.wsgiChange <USERNAME> to your cPanel usernameEdit djangotest/settings.pyChange <DOMAIN> to your account's domainGo to <DOMAIN>.heliohost.org/djangotestIf it worked you should see the Django welcome page like https://krydos.heliohost.org/djangotest/

If you create a wiki account and post your username here I can grant you access to edit it.

Try this:

Updated.

I'll look at it some time to see if it's even possible.

2.7.5 is the only version because no one has asked for anything else yet. I installed python 3.6.0 for you, and it is available by using #!/usr/bin/python3.6

Your cpanel mysql account doesn't have permissions to create databases. When you use the cpanel mysql page it creates the database with root privileges and then assigns you access.

Installed.

On Tommy it depends on which version of php you want to use. For instance if you want to use php 7.1 then use AddType application/x-httpd-ea-php71 .html

The username gulliver, and the domain learnersabroad.heliohost.org are now available.

http://examenco.heliohost.org/MyHelioServlet/

Tommy PHP 7.1 memory limit has been increased to 128M.

Installed. http://ejweb.cu.cc/test.aspx

Which version of PHP are you using too?

Ok.

The usernames parcela and lparcela are now available. Keep in mind that each person is allowed to have only one account though.