fixed CURRENT_TIMESTAMP to support miliseconds in database schema

sails/roles/database/files/pictodb-schema.sql

@@ -27,7 +27,7 @@ SET time_zone = "+00:00";
 CREATE TABLE IF NOT EXISTS `action` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `type` varchar(20) COLLATE utf8_unicode_ci NOT NULL CHECK (type IN ('Add','Select','Delete','Show','Unshow','Pause','tryinit','tryend','initsession','endsession','pausesession','resumesession')),
-  `timestamp` timestamp(3) DEFAULT CURRENT_TIMESTAMP,
+  `timestamp` timestamp(3) DEFAULT CURRENT_TIMESTAMP(3),
   `id_sup` int(11) DEFAULT NULL,
   `id_stu` int(11) NOT NULL,
   `id_try` int(11) DEFAULT NULL,
@@ -366,7 +366,7 @@ COMMENT="Supervisors information";
 CREATE TABLE IF NOT EXISTS `try` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `id_ws` int(11) NOT NULL,
-  `begin` timestamp(3) DEFAULT CURRENT_TIMESTAMP,
+  `begin` timestamp(3) DEFAULT CURRENT_TIMESTAMP(3),
   `end` timestamp(3) NULL,
   `result` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL,
   `description` varchar(4096) COLLATE utf8_unicode_ci DEFAULT NULL,
@@ -388,7 +388,7 @@ CREATE TABLE IF NOT EXISTS `working_session` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `id_sup` int(11) NOT NULL,
   `id_ins` int(11) NOT NULL,
-  `begin` timestamp(3) DEFAULT CURRENT_TIMESTAMP,
+  `begin` timestamp(3) DEFAULT CURRENT_TIMESTAMP(3),
   `end` timestamp(3) NULL,
   `current` boolean NULL DEFAULT 1,
   `description` varchar(4096) COLLATE utf8_unicode_ci DEFAULT NULL,

sails/src/config/local.js~

+/**
+ * Local environment settings
+ *
+ * Use this file to specify configuration settings for use while developing
+ * the app on your personal system: for example, this would be a good place
+ * to store database or email passwords that apply only to you, and shouldn't
+ * be shared with others in your organization.
+ *
+ * These settings take precedence over all other config files, including those
+ * in the env/ subfolder.
+ *
+ * PLEASE NOTE:
+ *		local.js is included in your .gitignore, so if you're using git
+ *		as a version control solution for your Sails app, keep in mind that
+ *		this file won't be committed to your repository!
+ *
+ *		Good news is, that means you can specify configuration for your local
+ *		machine in this file without inadvertently committing personal information
+ *		(like database passwords) to the repo.  Plus, this prevents other members
+ *		of your team from commiting their local configuration changes on top of yours.
+ *
+ *    In a production environment, you probably want to leave this file out
+ *    entirely and leave all your settings in env/production.js
+ *
+ *
+ * For more information, check out:
+ * http://sailsjs.org/#!/documentation/anatomy/myApp/config/local.js.html
+ */
+
+const path = require('path');
+const fs = require('fs');
+
+module.exports = {
+  /**
+   * Your SSL certificate and key, if you want to be able to serve HTTP
+   * responses over https:// and/or use websockets over the wss:// protocol
+   * (recommended for HTTP, strongly encouraged for WebSockets)
+   */
+  ssl: {
+    // ca: fs.readFileSync(path.join(__dirname, 'ssl', 'bundle.crt')),
+    key: fs.readFileSync(path.join(__dirname, 'ssl', 'key.key')),
+    cert: fs.readFileSync(path.join(__dirname, 'ssl', 'cert.crt')),
+  },
+
+  /**
+   * The `port` setting determines which TCP port your app will be
+   * deployed on.
+   *
+   * By default, if it's set, Sails uses the `PORT` environment variable.
+   * Otherwise it falls back to port 1337.
+   *
+   * In env/production.js, you'll probably want to change this setting
+   * to 80 (http://) or 443 (https://) if you have an SSL certificate
+   */
+  port: process.env.PORT || 1337,
+
+  /*
+   * The runtime "environment" of your Sails app is either typically
+   * 'development' or 'production'.
+   *
+   * In development, your Sails app will go out of its way to help you
+   * (for instance you will receive more descriptive error and
+   * debugging output)
+   *
+   * In production, Sails configures itself (and its dependencies) to
+   * optimize performance. You should always put your app in production mode
+   * before you deploy it to a server.  This helps ensure that your Sails
+   * app remains stable, performant, and scalable.
+   *
+   * By default, Sails sets its environment using the `NODE_ENV` environment
+   * variable.  If NODE_ENV is not set, Sails will run in the
+   * 'development' environment.
+   */
+  environment: process.env.NODE_ENV || 'development',
+};

sails/src/config/ssl/csr.pem

+-----BEGIN CERTIFICATE REQUEST-----
+MIICijCCAXICAQAwRTELMAkGA1UEBhMCQVUxEzARBgNVBAgMClNvbWUtU3RhdGUx
+ITAfBgNVBAoMGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDCCASIwDQYJKoZIhvcN
+AQEBBQADggEPADCCAQoCggEBAPkWZj6TTJQon1rupP1SUY8dQiSv3+1xByQAGYaf
+J9vZWfe6ZAy0ndFH26m0lc2S76BkQRfhWBTvWcsFhACWefSlGxpIiwxWdQOcF6cf
+WyFi9VBPUXvTPyd64hCd+9+XML/0hzU4BpzJsEbPyhOv7VZA2VCZ+GAP86b/MGCS
+s2QgWi7ZW0bTX0tO1WDC8JdHeaUXspwfJaqsw25SiDsNfWQmAZOa5F9I0vl4GCku
+ivy16Cn/1XnpBw9M9DH18H1ENDFkOnUJYa8NU/t9lJJqNapDZ3zTLIlNd28nl3LP
+HfbPGhq7qMAYmtiYt6rxHRBazL1OEFf2xb9DIVVlIKQXf/cCAwEAAaAAMA0GCSqG
+SIb3DQEBCwUAA4IBAQArBhbVjPadSIWK9yGO7oca2TT+ZMp2kw4OY7+NHj+4NUFk
+CKe2ZOAdvKM9wqY5P4QHux1WnqzEtga78ykaJofHeB/EFFqMkun5ETFbd/wIGKMy
+WdB/vNNbsv5Hf2/ezGiw1HUsCGp2P/JTDO9+a5O3ioFhp4tvfJ7TBfdzD5eq7Xlq
+DAHXPimbtnqiGGBf6efefG/Rl4cvvLyH5k/mUj00/stx3rjVayvedzOL8W4oRoxJ
+SQEaqlp/MtPLXBuG0RkZsJloon+aZfcR3WE4iG2BVQe7Dqtdto+mRa9e1ba0ZUQK
+Fq1iIGvsp9YIHCS3NXeJBeIllYkFK2hI7o6hALPf
+-----END CERTIFICATE REQUEST-----