tag:blogger.com,1999:blog-2600354524922709185.post1078286065100697729..comments2023-07-23T15:35:04.984+00:00Comments on Tech Biter: Running Crypt Server on a Mac via Server.appJohn Lockwoodhttp://www.blogger.com/profile/15899717580146455869noreply@blogger.comBlogger16125tag:blogger.com,1999:blog-2600354524922709185.post-9109469228726138752018-02-01T15:25:33.671+00:002018-02-01T15:25:33.671+00:00Thanks for this.
Just ran through the setup again...Thanks for this.<br /><br />Just ran through the setup again using an Ubuntu 17 server and got the same error. <br /><br />I am new to python so completely lost.Anonymoushttps://www.blogger.com/profile/17677347566663210744noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-5186622053746403272018-02-01T09:56:51.868+00:002018-02-01T09:56:51.868+00:00As per Mart's comment I also long ago gave up ...As per Mart's comment I also long ago gave up on using a Mac and switched to running Crypt in a Linux VM. Also this article was written with Crypt v1 and Crypt v2 is considerably different.John Lockwoodhttps://www.blogger.com/profile/15899717580146455869noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-85906911964090633592018-02-01T09:49:34.129+00:002018-02-01T09:49:34.129+00:00Hi Chris,
Just a hunch: could be the crypt.db file...Hi Chris,<br />Just a hunch: could be the crypt.db file doesn’t exist, you could try creating an empty one first by running <br />touch crypt.db <br />Strongly recommend moving to a Linux setup and docker though. I got it to run on on Yosemite before, but had to abandon it after upgrading to Sierra a while ago and recently attempting to update to latest Crypt-server release. Just couldn’t get it to work anymore, let alone run stable on macOS server’ Apache.Anonymoushttps://www.blogger.com/profile/15491705174583253784noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-36055167171297161462018-02-01T09:30:30.229+00:002018-02-01T09:30:30.229+00:00Hi,
Not sure if this is still being monitored.
T...Hi,<br /><br />Not sure if this is still being monitored.<br /><br />Trying to setup Crypt on a Sierra machine and getting this error when running sudo python manage.py migrate from step 6<br /><br /><br />UnknownMigration: Migration 'server:0001_initial' probably doesn't exist.<br />Traceback (most recent call last):<br /> File "/usr/local/crypt_env/lib/python2.7/site-packages/south/migration/base.py", line 302, in migration<br /> migration = __import__(full_name, {}, {}, ['Migration'])<br /> File "/usr/local/crypt_env/crypt/server/migrations/0001_initial.py", line 4, in <br /> from django.db import models, migrations<br />ImportError: cannot import name migrations<br /><br />Your help would be greatly appreciatedAnonymoushttps://www.blogger.com/profile/17677347566663210744noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-57649856085817886952015-08-05T15:22:03.679+00:002015-08-05T15:22:03.679+00:00Both the installation on the OS X 10.10 server I d...Both the installation on the OS X 10.10 server I did following your instructions and the and on the CentOS 7 minimal install I did following Grahams own recipe had the issue at first with the website throwing an Internal server error, and apache error logs showing smtp connection related errors triggered by the crypt.wsgi. <br />(the wgsi script does get installed automatically if you clone using git by the way). <br />I got the issue resolved on both installs by changing the logging section of settings.py to log to file instead of email, but reverting those sections to email logging like in the example file doesn't produce the issue again so far, but I have yet to test with client Macs.Anonymoushttps://www.blogger.com/profile/15491705174583253784noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-34880598571309558832015-08-05T13:14:40.929+00:002015-08-05T13:14:40.929+00:00Thanks for your information. I have not personally...Thanks for your information. I have not personally tried Django with Yosemite as I now use Linux VMs myself, however back when I was using Django webapps like Crypt with Mavericks I did not have any problems with not having mail setup. Nor do I currently have problems with the same issue in my Linux VM.John Lockwoodhttps://www.blogger.com/profile/15899717580146455869noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-23576147124456658962015-08-05T13:11:37.504+00:002015-08-05T13:11:37.504+00:00PS - Used the combined pip command in step 2 in or...PS - Used the combined pip command in step 2 in order to install all the requirements at once<br />pip install -r setup/requirements.txtAnonymoushttps://www.blogger.com/profile/15491705174583253784noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-466137211516341872015-08-05T13:08:40.159+00:002015-08-05T13:08:40.159+00:00Finally got this to work on OS X 10.10.3. Thought...Finally got this to work on OS X 10.10.3. Thought I might report back for other readers to benefit from. What threw me off big time as a first time user turned out to be the logging configuration for Django. After attempting setup on a Linux VM as a last resort I finally found out by reading the Apache log that the web app crashes when the mail is not configured. As there's no smtp server available at this site, I set up logging to file instead. Maybe I'll setup an smtp service and configure it in Django to get mail alerts later. As this is a small scale setup, I did't want the overhead of supporting multiple servers for Mac deployment, hence the setup on the Apple server.<br /><br />Here's what I had to change at the end of the LOGGING section in /usr/local/crypt_env/crypt/fvserver/settings.py to:<br /> 'handlers': {<br /> 'mail_admins': {<br /> 'level': 'ERROR',<br /> 'filters': ['require_debug_false'],<br /> 'class': 'django.utils.log.AdminEmailHandler'<br /> },<br /> 'file': {<br /> 'level': 'ERROR',<br /> 'filters': ['require_debug_false'],<br /> 'class': 'logging.FileHandler',<br /> 'filename': '/var/log/django/crypt-server-error.log',<br /> }<br /> },<br /> 'loggers': {<br /> 'django.request': {<br /> 'handlers': ['file'],<br /> 'level': 'ERROR',<br /> 'propagate': True,<br /> },<br /> }<br />}<br /><br /><br />To get the permissions for the log file access to work I ran a <br /> chmod -R 765 /var/log/django <br />I also had to insert a couple of extra lines in the Apache config file for the virtual host. At the start I put in WSGIDaemonProcess _www user=_www group=wheel and then at the start of the section I put in a line<br /> WSGIProcessGroup _www<br /><br />Otherwise in step 2 I had to make some adjustments. Firstly the sudo source bin/activate throws an error. I got around it by turning the line for bash into sudo bash, and skipping the sudo part for the other commands in step 2. Remember to run the chown -R _www /usr/local/crypt_env as root afterwards. As there is a proxy at this site which is dealt with through environment variables, I added the -E switch to sudo to invoke bash as well at the start of step 2.<br /><br />Hopes this helps someone that comes looking here.Anonymoushttps://www.blogger.com/profile/15491705174583253784noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-29339492330775962232014-08-26T05:17:35.581+00:002014-08-26T05:17:35.581+00:00Thanks for this post....
Web development services...Thanks for this post....<br /><br /><a href="http://chiptek.com.au" rel="nofollow">Web development services</a>Anonymoushttps://www.blogger.com/profile/17537491464251615618noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-41715420626457794602014-07-11T10:05:08.577+00:002014-07-11T10:05:08.577+00:00I am currently running Crypt in a Linux virtual ma...I am currently running Crypt in a Linux virtual machine with Apache but (obviously) as per this article have previously got it working in OS X in Apache. I did modify this article in November to address some issues regarding installing for OS X.<br /><br />I would certainly expect you to have problems with Django if you have installed 1.6, the original version of Crypt was only written to work with Django 1.4 although I got round that, and as far as I am aware it now officially works with Django 1.5 but has not been officially tested with 1.6. <br /><br />I just checked it currently wants Django 1.5.3<br /><br />I therefore recommend you start again and make sure you install Django 1.5.3 and the versions of any other components it asks for rather than the latest versions. This is where using VirtualEnv helps.<br /><br />Crypt (server) comes with a file called requirements.txt which lists the versions it wants which are as follows<br /><br />Django==1.5.3<br />South==0.8.2<br />django-bootstrap-toolkit==2.15.0<br />docutils==0.11<br />wsgiref==0.1.2<br /><br />Either you can install the whole bunch using the command<br /><br />pip install -r setup/requirements.txt<br /><br />or you can do individual installs like<br /><br />pip install django==1.5.3<br /><br />Do this at the stage where I listed installing them to make sure you are doing it in the VirtualEnv (if you use that).<br /><br />If your still stuck after this send me a contact via the contact form with details of what is happening.John Lockwoodhttps://www.blogger.com/profile/15899717580146455869noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-14249694809603356882014-07-11T01:37:20.633+00:002014-07-11T01:37:20.633+00:00Any update with this? I'm trying to configure ...Any update with this? I'm trying to configure crypt-server on my mac mini server with no luckAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-64470471053997138502013-11-15T11:30:44.095+00:002013-11-15T11:30:44.095+00:00I have the latest Crypt Server working in the deve...I have the latest Crypt Server working in the development Django web server with Django 1.5.3 but not yet in Apache. If you can send me a note via the contact form at the right of this page we can discuss this further privately via email.John Lockwoodhttps://www.blogger.com/profile/15899717580146455869noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-81727965847636221412013-11-15T09:12:24.726+00:002013-11-15T09:12:24.726+00:00I am going to download and install the new version...I am going to download and install the new version you have pointed out. I will then post revised instructions. This will probably be in the form of a new page so this page may be deleted at that point (as being out of date). So keep an eye open for a possible new page. This may take a couple of days or so.John Lockwoodhttps://www.blogger.com/profile/15899717580146455869noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-55432283708986973482013-11-15T01:44:28.063+00:002013-11-15T01:44:28.063+00:00John thanks I tried that but no luck. I have tried...John thanks I tried that but no luck. I have tried 4 times now and I can not get this working. Not sure if the instruction need revising or what. It looks like Graham has made some modifications to the program recently for 1.5 and now your process does not work. I have a feeling /usr/local/crypt_env/crypt/templates/base.html and /usr/local/crypt_env/crypt/server/templates/server/index.html need some additional modification with Django 1.5.3 as his install now suggests as the version needed.<br /><br />I really appreciate the help.<br />Steve and Michellehttps://www.blogger.com/profile/00398067175470356263noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-77211725555557808552013-11-14T09:36:05.707+00:002013-11-14T09:36:05.707+00:00Crypt is officially still only written for use wit...Crypt is officially still only written for use with Django 1.4, I did as discussed above work out how to get it to work correctly with Django 1.5 by changing just two lines, I have not tried it with Django 1.6.<br /><br />I recommend you force the installation of an older version of Django by using a slightly different form of the command so try the following.<br /><br />sudo pip install django==1.4.3<br /><br />or<br /><br />sudo pip install django==1.5.1John Lockwoodhttps://www.blogger.com/profile/15899717580146455869noreply@blogger.comtag:blogger.com,1999:blog-2600354524922709185.post-58914196404307650972013-11-14T03:03:43.139+00:002013-11-14T03:03:43.139+00:00John followed this and I get a Bad Request 400 whe...John followed this and I get a Bad Request 400 when trying to go to the website, only difference I have is Django 1.6Steve and Michellehttps://www.blogger.com/profile/00398067175470356263noreply@blogger.com