I think you have looked at the tutorial from Mr. Heinemeier Hansson at least once or twice and have a similar setup.
rails new kamal_pg --css tailwind --skip-test --database=postgresql
cd kamal_pg
win-bash
I have one computer and two different github accounts. One is for work, the other is for my personal stuff. I can't use the same ssh key twice, so I have to use different ssh key for each of my accounts. How do I do that? How do I switch between these ssh keys?
// Custom Validator to add errors into vuex store and also handle laravel form errors. | |
import { mapGetters } from 'vuex'; | |
import { CLEAR_FORM_ERRORS, ERROR } from '../vuex/types'; | |
import Vue from 'vue'; | |
export default { | |
data() { | |
return { | |
errors: [], | |
keepServerErrors: ['unique', 'boolean', 'exists', 'regular_chars', 'identifier', 'date'], |
<?php | |
namespace App\Http\Middleware; | |
use Closure; | |
use Illuminate\Http\Request; | |
class JsonMiddleware | |
{ | |
public function handle(Request $request, Closure $next) |
<my-component inline-template> | |
<h1>@lang('users.edit') {{ $user->name }}</h1> | |
<form method="post" action="{{ route('users.update', ['user' => $user]) }}"> | |
{!! csrf_field() !!} | |
<input name="_method" type="hidden" value="PATCH"> | |
<!-- Some form fields --> | |
<button type="submit">{{ __('button.update') }}</button> | |
</form> |
<?php namespace App\Traits; | |
use App\MeetingApprovalCommittee; | |
use App\Role; | |
trait CheckRequestPermission { | |
/** | |
* Check role permission to form request class to be validated | |
* |
//8 Methods to Iterate through Array | |
//forEach (Do Operation for Each Item in the Array) | |
[1,2,3].forEach(function(item,index) { | |
console.log('item:',item,'index:',index); | |
}); | |
//map (Translate/Map all Elements in an Array to Another Set of Values.) | |
const oneArray = [1,2,3]; | |
const doubledArray = oneArray.map(function(item) { |
You can't merge with local modifications. Git protects you from losing potentially important changes. | |
You have three options. | |
1. Commit the change using | |
git commit -m "My message" | |
2. Stash it. | |
Stashing acts as a stack, where you can push changes, and you pop them in reverse order. |
You could update your index: | |
cd /root/folder/of/your/repo | |
git update-index --assume-unchanged nbproject/project.properties | |
and make sure it never shows as "updated" in your current repo. | |
That means it won't ever been pushed, but it is still present in the index. | |
(and it can be modified at will in your local working tree). |