How can I access/test a webgui of an app?

marafado88

Hello everyone,

Note that I am not a django dev and dont have experience with shared servers.

I have migrated a django app from Webfaction, and changed all the previous server paths to the new one of Opalstack here:

~/apps/django/apache2/bin/start
~/apps/django/apache2/bin/stop
~/apps/django/apache2/bin/restart
~/apps/django/apache2/conf/httpd.conf

changing also, the database password for the new one generated while it was migrated from Webfaction to Opalstack on:

~/apps/django/<workspace>/settings.py

and started apache2.

Now, I am trying to test the webgui, but I really dont know how to do it.

Can anyone enlight me where can I access the webgui?

marafado88

I forgot to say that I've followed the following HOWTO: https://docs.opalstack.com/user-guide/sites/

But still nothing using the DN selected, and from what I see, I think that the httpd.conf must be reconfigurate to current host, but trying with the DN user.opalstacked.com in one virtualhost, doesnt make any diference. The 37666 is the proxy port for django app, displayed in webgui (the other ports are from previous host, so you can ignore that).

ServerRoot "/home/user/apps/django/apache2"

LoadModule authz_core_module modules/mod_authz_core.so
LoadModule dir_module        modules/mod_dir.so
LoadModule env_module        modules/mod_env.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module       modules/mod_mime.so
LoadModule rewrite_module    modules/mod_rewrite.so
LoadModule setenvif_module   modules/mod_setenvif.so
LoadModule wsgi_module       modules/mod_wsgi.so
LoadModule unixd_module      modules/mod_unixd.so
LoadModule alias_module      modules/mod_alias.so

LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
CustomLog /home/user/apps/django/apache2/logs/access.log combined
Errorlog /home/user/apps/django/apache2/logs/error.log

Listen 37666
KeepAlive Off
SetEnvIf X-Forwarded-SSL on HTTPS=1

ServerLimit 2
StartServers 1
MinSpareThreads 1
MaxSpareThreads 3
ThreadsPerChild 5

WSGIRestrictEmbedded On
WSGILazyInitialization On

<VirtualHost *:37666>
  ServerName user.opalstacked.com

  WSGIProcessGroup rma
  WSGIDaemonProcess rma processes=2 threads=12 python-path=/home/user/apps/django:/home/user/apps/django/RMA
  WSGIScriptAlias / /home/user/apps/django/RMA/wsgi.py
</VirtualHost>

<virtualHost *:46764>
  ServerName www.remotesup.domain.org

  WSGIProcessGroup remotesup
  WSGIDaemonProcess remotesup processes=2 threads=12 python-path=/home/user/apps/django:/home/user/apps/django/remotesup
  WSGIScriptAlias / /home/user/apps/django/remotesup/wsgi.py
</VirtualHost>

<VirtualHost *:46764>
	ServerName www.orbited.domain.org
	ServerAlias domain.org
	Redirect permanent / localhost:11389
</VirtualHost>

sean

marafado88 your Apache setup might not work here. If you'd like to adapt your app to our uwsgi setup, we've got some tips here: WF to Opalstack (Django and Postgres). Where to begin?

If you want to continue using Apache and mod_wsgi: HOWTO: run Django on Apache and mod_wsgi

We might be able to get your existing Apache running, but we'd need to inspect it to determine that. Feel free to email support@opalstack.com for assistance if you need it 🙂

anjanesh

Why do you have an apache2 directory in ~/apps/django/ ? Did you not create the django app in the control panel's Application section ? https://my.opalstack.com/apps/

Your directory structure should look like this :

[username@opalX djangoapp]$ pwd
/home/username/apps/djangoapp
[username@opalX djangoapp]$ ls -la
total 20
drwxr-xr-x+  6 username username  150 Jun 30 03:13 .
drwxr-xr-x+ 26 root     root     4096 Jul 28 02:05 ..
drwxrwxr-x.  5 username username  106 Jul  5 10:20 djangoapp
drwxr-xr-x.  5 username username  128 May 16 03:23 env
drwx------.  3 username username   52 May 16 04:29 myproject
-rw-------.  1 username username 1086 May 16 03:24 README
-rwx------.  1 username username  402 May 16 03:24 start
-rwx------.  1 username username  532 May 16 03:24 stop
drwx------.  2 username username   31 Jun 30 03:15 tmp
-rw-------.  1 username username  437 May 16 04:42 uwsgi.ini

sean

anjanesh they copied the app from WebFaction.

marafado88

anjanesh this was migrated through opalstack wfmigrate from webfaction, and readded automatically on opalstack backoffice during that process.

I was able to also migrate another app that was responsable for frontend, and now I have frontend running as expected, but on django backoffice, I am only able to check the login part, but if I login I receive this http message:

Page not found (404)
Request Method: GET
Request URL: http://web.opalstacked.com/repair/rma/
App 'repair', model 'rma', not found

You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.

I've changed both settings.py and httpd.conf to use the new home folder path, and have also removed those two VirtualHost fields that was not being used, and changed database password to the new one.

After some search I didnt found any logs related with django in my home folder, only from apache2, but doesnt have any errors or warnings there...

Django:

Django 0.96
Python 2.5

Frontend:

PHP-5.6

Not sure how can I debug what is happening with that login.

The database on webfaction was MySQL, and in Opalstack is MariaDB, so Django is still using the db engine for mysql. I tried to edit it to other engine just to see if there was another type of error on http, and it was, so I think that the db is not the issue, and that db engine its retrocompatible with mariadb, and the problem relies with django frontend because of 404 error after performing login.

Note: This django have like almost 15 years, and I got zero documentation about this on my side, and the guy who made this desappeared 4 years ago.

marafado88

Also @sean I've been talking to you through e-mail since thrusday about a django app and his database, from a e-mail with a portuguese DN.