This is useful for anybody who is running Laravel Framework, but for some reason keep their User logic in Wordpress.
Note: This assumes any other Wordpress to Laravel migrations have already been taken care of (like adding remember_token to user table and setting up a User-model that extneds Illuminate\Contracts\Auth\Authenticatable)
requires either MikeMcLin\WpPassword or Hautelook\Phpass
PS. This can probably also be accomplished by swapping out the app-hasher for the entire project!
In a previous post we discovered that if Redis crashes and is restarted Daphne will not work properly for WebSocket connections. We discovered that it is a bug in Daphne and that using Supervisord to solve this problem might be a solution. We are going to use EventListeners in Supervisord to run a customized python script to restart Daphne if Redis crashes. First we add Redis to our supervisord configuration. Note: Remember that Redis should NOT be run in daemonized mode when running in Supervisord.
[program:Redis_Server]
command=redis-server /etc/redis/redis.conf
[...]
This post will focus on troubleshooting and debugging the channel layer of any Django Channels application. For this post a local Redis backend is used.
It is assumed for the purpose of this example that a working Django Channels application is running, and that a proxy service is running that is able to upgrade the HTTP connection to a WebSocket connection. A Redis server is also required.
This post describes how to enforce a secure https connection using the .htaccess-file in Apache. At the same time we would like to redirect all www-requests to a non-www secure request. This post is a concatenation of the following forum posts here and here. Edit .htaccess with the following content.
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^(.*)$ http://%1/$1 [R=301,L]
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
RewriteCond %{HTTPS_HOST} ^www\.(.*)$ [NC]
It's time to join the new era of safe internetting. This post descibes how an SSL certificate is acquired, installed and enabled for a server running VestaCP and Wordpress using the free Certificate Authority (CA) Let's Encrypt. The internet and software is ever changing and following one tutorial never suffices to a working solution. This post is my experience following this tutorial using this script. Also this forum post has helped. Prerequisites: This post assumes that you have a webserver with root access and own a domain name. Also that vesatcp is set up to host at least one site on your domain. There is plenty of information about vestacp online and it will therefore not be included here.
Lo
In this port we will be exploring possible logging options when having deployed our Django Channels app to AWS Elastic Beanstalk (see previous posts). An excellent guide to Logging with Django can as always be found in their docs. Here we will explore a simple logging setup that has a catch-all for both Django and Channels loggers. A quick reminder of the setup we have on our AWS Elastic Beanstalk server. HTTP requests are being server by Django as WSGI through Apache wsgi module. At the same time we are serving WebSocket connections using Daphne on a local port 5000 and several workers using [Su
This post will describe how to set up a Django Channels solution using AWS Elastic Beanstalk [EB]. This guide is written in response to there being very little information on the combination of Channels and AWS. Mainly many solutions end with problems regarding websockets, which is a fundamental part of Channels. See here and here. This guide will consist of multiple step-by-step parts including
This post describes how to set up a Django Channels environment in Vagrant using Apache as a reverse proxy. We are picking up from an environment we already configured, see this previous post. This guide will describe multiple steps of the process including:
This post will cover how to configure our vagrant guest machine [1, 2, 3, 4] to run a django server instead of our previous prop backends. We will continue using Vagrant and introduce virtualenv for our Django project.
We create a virtual environment and install django. We start off by installing python virtualenv and set up an environment in our vagrantfolder so we will have it ready on boot.
$ pip install virtualenv
~/vagrant$ mkdir django
This post will describe how we can run our different backends without any worry, mostly from crashing and then recovering. We will build on top of our already configurated Vagrant guest machine running Apache with reverse proxy [1, 2, 3]. Until now we are running our backend servers (SimpleHTTPServer and simple-websocket-server) directly from our provisioning script as a background daemon. This means that if we halt the machine and bring it back up, our servers are not running and need to be started again. It also means that if one of our backends experiences a crash (believe me, it happens) it does not recover