It seems like the author is opposed to adding this sort of functionality: https://github.com/dangrossman/bootstrap-daterangepicker/issues/295
- re.match - If zero or more characters at the beginning of string match the regular expression pattern.
- re.search - Scan through string looking for a location where the regular expression pattern produces a match
Here are the commands I use when I bring up a new Ubuntu server for flask development:
I tried running some select queries on both of the both the virtual container and host for benchmark purposes. My conclusion? MySQL read performance inside and outside the LXC container is the exactly the same.
Site error: the file <b>/var/www/accounts/admin/cron.php</b> requires the ionCube PHP Loader ioncube_loader_lin_5.3.so to be installed by the website operator. If you are the website operator please use the <a href="http://www.ioncube.com/lw/">ionCube Loader Wizard</a> to assist with installation.
You need to add your the ioncube zend extension to the CLI php.ini too: /etc/php5/cli/php.ini
Oct 19 14:04:34 Billing sm-mta: STARTTLS=client, relay=aspmx.l.google.com., version=TLSv1/SSLv3, verify=FAIL, cipher=ECDHE-RSA-RC4-SHA, bits=128/128
If you see those errors in your mail.log and your emails are failing to send, you need to add your ssl cert from apache to the sendmail config in /etc/mail/sendmail.cf:
# CA directory
# CA file
# Server Cert
# Server private key
I was getting the following error when I tried testing with openssl:
error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:177
The solution? It turns out that /etc/default/slapd needs to be configured to use /etc/ldap/ldap.conf using the following:
Add the following to /etc/apache2/ports.conf:
Add a file that describes your site to /etc/apache2/sites-available with this:
Run this command: sudo a2ensite misc
And restart apache: sudo service apache2 restart
Simple explanation: http://prakhar.me/articles/flask-on-nginx-and-gunicorn/
Nginx SSL configuration: https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-with-ssl-as-a-reverse-proxy-for-jenkins
The thing I spent the longest on was getting supervisor to work. Gunicorn kept giving me "gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3>", because I was missing the "directory" parameter. I needed to tell supervisor which directory to start from.
command=/<path>/venv/prod/bin/gunicorn -w 8 main:app -b 127.0.0.1:8080
You will need to create an upstart script to get supervisor to run when the system starts: http://serverfault.com/a/96500