Вся суть харча™ (на самом деле все далеко не так...)
| <template> | |
| <div> | |
| <label v-if="label" class="form-label" :for="`date-input-${_uid}`">{{ label }}:</label> | |
| <input v-bind="$attrs" class="form-input" :id="`date-input-${_uid}`" :class="{ error: error }" type="text" ref="input" :value="value" @change="change" @keyup="change"> | |
| <div v-if="error" class="form-error">{{ error }}</div> | |
| </div> | |
| </template> | |
| <script> | |
| import pikaday from 'pikaday' |
Example of deployment process which I use in my Nuxt.js projects. I usually have 3 components running per project: admin-panel SPA, nuxt.js renderer and JSON API.
This manual is relevant for VPS such as DigitalOcean.com or Vultr.com. It's easier to use things like Now for deployment but for most cases VPS gives more flexebillity needed for projects bigger than a landing page.
UPD: This manual now compatible with [email protected]. For older versions deployment, see revision history.
Let's assume that you have entered fresh installation of Ubuntu instance via SSH. Let's rock:
| // https://davidpiesse.github.io/tailwind-md-colours/ | |
| // | |
| //Notes | |
| // | |
| //All colours are generated from Material Design Docs | |
| //Colours have a base, a set of shades (50-900) accent colours | |
| //In addition a companion set of contrast colours are included for colouring text / icons | |
| // Example usage | |
| // class="w-full bg-red-600 text-red-600-constrast" |
| <!doctype html> | |
| <html lang="ru"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="$helmet-placeholder$"> | |
| <meta name="$sc-placeholder$"> | |
| <style> |
| let cssImport = require('postcss-import') | |
| let cssNext = require('postcss-cssnext') | |
| let glob = require('glob-all') | |
| let mix = require('laravel-mix') | |
| let purgeCss = require('purgecss-webpack-plugin') | |
| let tailwind = require('tailwindcss') | |
| mix.js('resources/assets/js/app.js', 'public/js') | |
| .postCss('resources/assets/css/app.css', 'public/css/app.css', [ | |
| cssImport(), |
| <?php | |
| namespace App; | |
| use Illuminate\Database\Eloquent\Builder; | |
| use Illuminate\Database\Eloquent\Model; | |
| use Illuminate\Database\Query\Builder as QueryBuilder; | |
| use Illuminate\Database\Query\Expression; | |
| abstract class BaseModel extends Model |
| const MODULE_NAME = 'base-app/events/' | |
| export const CONNECT_WS = MODULE_NAME.concat('CONNECT_WS') | |
| export const DISCONNECT_WS = MODULE_NAME.concat('DISCONNECT_WS') | |
| export const SUBSCRIBE_WS = MODULE_NAME.concat('SUBSCRIBE_WS') | |
| export const UNSUBSCRIBE_WS = MODULE_NAME.concat('UNSUBSCRIBE_WS') | |
| export const EMIT_WS = MODULE_NAME.concat('EMIT_WS') | |
| export const NEW_EVENT = MODULE_NAME.concat('NEW_EVENT') | |
| export const ADD_EVENT = MODULE_NAME.concat('ADD_EVENT') |
Options included below:
- Using Docker
docker-compose - Using Homebrew
brew
This gist was originally created for Homebrew before the rise of Docker, yet it may be best to avoid installing mysql via brew any longer. Instead consider adding a barebones docker-compose.yml for each project and run docker-compose up to start each project's mysql service.

