title: Setting Up Laravel in Ubuntu / DigitalOcean keywords: servers, laravel, coderstape, coder's tape description: Let's take a look at settting up a server from scratch for Laravel. date: April 1, 2019 tags: servers, laravel permalink: setting-up-laravel-in-ubuntu-digitalocean img: https://coderstape.com/storage/uploads/GZTXUbyGum2xeUZM9qBD5aPv8EKLwG3C8RGcRon4.jpeg author: Victor Gonzalez authorlink: https://github.com/vicgonvt
| package io.github.sazid | |
| import java.sql.Connection | |
| import java.sql.Date | |
| import java.sql.PreparedStatement | |
| import java.sql.ResultSet | |
| import java.time.LocalDate | |
| import javax.sql.DataSource | |
| typealias RowMapper<T> = (ResultSet) -> T |
The given solution does not work when using a package that does a lot of the work after you define the with() relations like datatables
here is a solution that works for any model.
<?php| thread | goroutine |
|---|---|
| OS threads are managed by kernal and has hardware dependencies. | goroutines are managed by go runtime and has no hardware dependencies. |
| OS threads generally have fixed stack size of 1-2MB | goroutines typically have 8KB (2KB since Go 1.4) of stack size in newer versions of go |
| Stack size is determined during compile time and can not grow | Stack size of go is managed in run-time and can grow up to 1GB which is possible by allocating and freeing heap storage |
| There is no easy communication medium between threads. There is huge latency between inter-thread communication. | goroutine use channels to communicate with other goroutines with low latency (read more). |
| Threads have identity. There is TID which identifies each thread in a process. | goroutine do not have any identity. go implemented this because go does not have TLS([Thread Local Storage](https://msdn.microsoft.com/en-us/library/win |
| package main | |
| import ( | |
| "math" | |
| "fmt" | |
| ) | |
| //::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: | |
| //::: ::: | |
| //::: This routine calculates the distance between two points (given the ::: |
| /*** Laravel mix API cheat sheet **/ | |
| mix.js(src, output); | |
| mix.react(src, output); /** Identical to mix.js(), but registers React Babel compilation. **/ | |
| mix.extract(vendorLibs); | |
| mix.sass(src, output); | |
| mix.standaloneSass('src', output); /** Faster, but isolated from Webpack. **/ | |
| mix.fastSass('src', output); /** Alias for mix.standaloneSass(). **/ | |
| mix.less(src, output); | |
| mix.stylus(src, output); | |
| mix.postCss(src, output, [require('postcss-some-plugin')()]); |
| package main | |
| import ( | |
| "context" | |
| "flag" | |
| "fmt" | |
| "log" | |
| "net/http" | |
| "os" | |
| "os/signal" |
(from Understanding Nginx Server and Location Block Selection Algorithms - https://goo.gl/YyzshP)
server {
There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.
All other files should be in your own global gitignore file:
- Create a file called
.gitignorein your home directory and add any filepath patterns you want to ignore. - Tell git where your global gitignore file is.
Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute
.config/git/ignorefor.gitignorein your home directory, if you prefer.