Dityalovers

OAuth2 and JWT Authentication in Laravel in 2026

2026-05-23T19:55:44.918+07:00

Authentication architecture has evolved significantly in modern Laravel applications.

Today’s systems must support:

mobile applications
SPAs
microservices
AI platforms
third-party integrations
enterprise APIs

Simple session authentication is no longer enough for distributed applications.

In 2026, most scalable Laravel systems rely on:

OAuth2
JWT authentication
token-based authorization
zero trust identity systems

This guide explains how OAuth2 and JWT work in Laravel, their differences, and production-grade implementation strategies.

Understanding OAuth2 vs JWT

Many developers confuse OAuth2 and JWT.

They solve different problems.

OAuth2

OAuth2 is:

an authorization framework.

It defines:

how clients obtain access
token issuance flows
delegated authorization
permission scopes

OAuth2 is commonly used for:

third-party login
API access delegation
enterprise integrations

JWT

JWT (JSON Web Token) is:

a token format.

It contains encoded claims such as:

user identity
expiration
permissions
issuer

JWT is commonly used for:

stateless authentication
APIs
microservices
distributed systems

OAuth2 Flow Overview

OAuth2 authorization flow:

User authenticates
Authorization server issues token
Client stores token
API validates token
Access granted

This enables:

delegated access
fine-grained permissions
token expiration
revocation systems

JWT Authentication Flow

JWT authentication works differently.

User logs in
Server generates JWT
Client stores token
Client sends token on requests
API validates signature

JWT removes server-side session dependency.

Choosing Between Sanctum, Passport, and JWT

Laravel provides multiple authentication options.

Laravel Sanctum

Best for:

SPAs
first-party apps
lightweight APIs

Advantages:

simple
secure
minimal complexity

Laravel Passport

Best for:

OAuth2
enterprise integrations
third-party access
delegated authorization

Passport implements full OAuth2 server functionality.

JWT Authentication

Best for:

stateless APIs
microservices
distributed systems
external auth providers

Common package:

tymon/jwt-auth

Installing Laravel Passport

Install Passport:

composer require laravel/passport

Run migrations:

php artisan migrate

Install encryption keys:

php artisan passport:install

Enable Passport:

use Laravel\Passport\Passport;

public function boot(): void
{
    Passport::routes();
}

Configuring API Authentication

In config/auth.php:

'guards' => [
    'api' => [
        'driver' => 'passport',
        'provider' => 'users',
    ],
],

Creating Access Tokens

Example:

$token = $user->createToken(
    'mobile-app',
    ['orders:read']
);

OAuth2 scopes provide granular permission control.

JWT Authentication Setup

Install JWT package:

composer require tymon/jwt-auth

Publish configuration:

php artisan vendor:publish \
--provider="Tymon\JWTAuth\Providers\LaravelServiceProvider"

Generate secret key:

php artisan jwt:secret

Generating JWT Tokens

Example login controller:

public function login(Request $request)
{
    $credentials = $request->only(
        'email',
        'password'
    );

    if (! $token = auth()->attempt($credentials)) {
        return response()->json([
            'error' => 'Unauthorized'
        ], 401);
    }

    return response()->json([
        'token' => $token
    ]);
}

Protecting Routes

JWT middleware example:

Route::middleware('auth:api')->group(function () {
    //
});

Use Refresh Tokens

Never issue permanent tokens.

Modern authentication should use:

short-lived access tokens
refresh tokens
automatic rotation

Benefits:

reduced compromise window
safer mobile authentication
improved revocation handling

Implement Token Rotation

Production systems should rotate:

access tokens
signing keys
refresh tokens

Token rotation limits long-term abuse after leaks.

Use Scoped Permissions

Never allow unrestricted API access.

Bad:

['*']

Better:

[
    'orders:read',
    'orders:create',
]

Principle:

least privilege access.

Secure Token Storage

Frontend security matters.

Never:

store tokens in localStorage for sensitive systems
expose refresh tokens to JavaScript unnecessarily

Safer approaches:

HTTP-only cookies
secure cookies
encrypted storage

Enable MFA for Sensitive Systems

Authentication alone is insufficient.

Add:

OTP verification
WebAuthn
hardware keys
device approval flows

Critical for:

fintech
enterprise SaaS
admin dashboards

Prevent Token Theft

Protect against:

XSS attacks
token replay
MITM interception

Recommended:

HTTPS everywhere
CSP headers
device fingerprinting
token expiration

Revoke Compromised Tokens

Modern auth systems must support revocation.

Examples:

suspicious IP access
credential leaks
logout events
password resets

Passport supports token revocation directly.

Use API Rate Limiting

Authentication endpoints are high-risk attack surfaces.

Protect:

login routes
token refresh endpoints
password reset APIs

Laravel example:

RateLimiter::for('login', function (Request $request) {
    return Limit::perMinute(5)
        ->by($request->ip());
});

Secure Microservice Authentication

For microservices:

avoid shared secrets
use short-lived JWTs
implement mutual TLS
isolate internal APIs

Zero trust networking is increasingly important.

Monitor Authentication Activity

Track:

failed logins
abnormal token issuance
suspicious devices
geographic anomalies

Useful tools:

Laravel Pulse
OpenTelemetry
Grafana
SIEM systems

OAuth2 Security Best Practices

Production OAuth2 systems should:

enforce HTTPS
rotate secrets
restrict redirect URLs
validate scopes
use PKCE flows

PKCE is especially important for:

mobile apps
public clients
SPAs

JWT Security Best Practices

JWT systems should:

use strong signing keys
keep expiration short
rotate tokens
validate issuer/audience
avoid sensitive payload data

Never store confidential data directly inside JWT payloads.

OAuth2 vs JWT Comparison

Feature	OAuth2	JWT
Purpose	Authorization framework	Token format
Session Storage	Optional	Stateless
Third-party Access	Excellent	Limited
Complexity	Higher	Simpler
Microservices	Good	Excellent
Enterprise Integrations	Excellent	Moderate
Token Revocation	Easier	Harder

Recommended Architecture in 2026

Use Sanctum When:

building SPAs
handling first-party APIs
simplicity matters

Use Passport When:

implementing OAuth2
supporting third-party integrations
enterprise authorization is needed

Use JWT When:

building distributed systems
scaling microservices
requiring stateless authentication

Production Authentication Checklist

Before deploying Laravel authentication systems:

HTTPS enforced
MFA enabled
Refresh tokens implemented
Token scopes configured
Expiration policies active
Rate limiting enabled
Token rotation enabled
Logging centralized
Revocation supported
PKCE enabled
CSP headers configured
Monitoring enabled

Conclusion

Modern Laravel authentication is no longer just about login forms.

Production-grade systems require:

secure token management
delegated authorization
layered defenses
observable authentication flows
zero trust principles

OAuth2 and JWT are both powerful tools.

The best choice depends on:

architecture
scalability requirements
third-party integrations
security posture

Authentication is now part of infrastructure architecture itself.

Tutorial OAuth2 dengan CodeIgniter

Laravel API Security Best Practices in 2026

2026-05-23T19:42:16.243+07:00

APIs have become the backbone of modern Laravel applications.

From:

mobile apps
AI services
SaaS platforms
fintech systems
microservices
third-party integrations

Almost every modern Laravel architecture depends heavily on APIs.

This also means APIs are one of the biggest attack surfaces in production systems.

In 2026, securing Laravel APIs requires more than authentication middleware.

Modern API security involves:

identity verification
request integrity
infrastructure isolation
abuse prevention
observability
zero trust networking

This guide covers production-grade Laravel API security strategies used in scalable systems.

1. Always Use HTTPS

APIs should never be exposed over plain HTTP.

Without HTTPS:

tokens can be intercepted
credentials leak
session hijacking becomes possible

Force HTTPS in production.

use Illuminate\Support\Facades\URL;

public function boot(): void
{
    if (app()->environment('production')) {
        URL::forceScheme('https');
    }
}

Also enable HSTS:

add_header Strict-Transport-Security "max-age=31536000" always;

2. Use Token-Based Authentication Properly

For modern Laravel APIs, recommended authentication methods include:

Laravel Sanctum
OAuth2
JWT
WebAuthn-backed flows

For first-party SPAs:

Sanctum is usually the best option

For third-party integrations:

OAuth2 is safer and more scalable

Avoid:

long-lived static API keys
shared credentials
plaintext token storage

3. Scope API Permissions

Never give APIs unlimited access.

Bad:

$user->createToken('api-token');

Better:

$user->createToken(
    'mobile-app',
    ['orders:read', 'orders:create']
);

Scoped permissions reduce blast radius during compromise.

4. Implement Rate Limiting

Rate limiting protects APIs against:

brute force attacks
credential stuffing
scraping
denial-of-service abuse

Laravel example:

RateLimiter::for('api', function (Request $request) {
    return Limit::perMinute(60)->by(
        $request->user()?->id ?: $request->ip()
    );
});

For sensitive endpoints:

Limit::perMinute(5)

5. Validate Every Request

Never trust client input.

Always validate:

payload structure
types
enums
file uploads
nested objects

Example:

$request->validate([
    'email' => ['required', 'email'],
    'role' => ['in:user,admin'],
]);

Use Form Requests for cleaner security architecture.

6. Prevent Mass Assignment Vulnerabilities

Mass assignment attacks still affect many APIs.

Bad:

User::create($request->all());

Safer:

User::create(
    $request->validated()
);

And use explicit fillable fields:

protected $fillable = [
    'name',
    'email',
];

7. Add API Request Logging

Security incidents are impossible to investigate without logs.

Log:

failed logins
permission denials
token creation
suspicious IPs
abnormal traffic spikes

Useful stack:

Laravel Pulse
OpenTelemetry
Grafana
Loki

8. Rotate API Tokens Regularly

Never allow permanent API tokens.

Recommended:

short-lived access tokens
refresh tokens
automated rotation
revocation support

For high-security systems:

revoke tokens after suspicious behavior
bind tokens to devices/IPs

9. Use Signed Requests for Sensitive Operations

Critical operations should verify request integrity.

Examples:

payment callbacks
webhook endpoints
internal service communication

Laravel signed URLs:

URL::signedRoute('download', [
    'file' => $id
]);

For APIs:

HMAC signatures
timestamp verification
nonce validation

10. Protect Against Enumeration Attacks

Avoid exposing:

whether emails exist
user IDs
internal references

Bad:

{
  "message": "Email not found"
}

Safer:

{
  "message": "Invalid credentials"
}

11. Use API Versioning

Versioning improves:

security upgrades
deprecation management
client isolation

Example:

Route::prefix('v1')->group(function () {
    //
});

This prevents breaking older integrations during security changes.

12. Secure File Upload APIs

File upload endpoints are high-risk attack vectors.

Always:

validate MIME types
limit file size
randomize filenames
scan uploads
store outside public directories

Example:

$request->validate([
    'document' => [
        'required',
        'file',
        'mimes:pdf,png,jpg',
        'max:2048',
    ]
]);

13. Use Security Headers

APIs should include protective headers.

Important headers:

X-Content-Type-Options
Referrer-Policy
Content-Security-Policy
X-Frame-Options

Example middleware:

$response->headers->set(
    'X-Frame-Options',
    'DENY'
);

14. Protect Against CORS Misconfiguration

Bad CORS policies expose APIs to abuse.

Avoid:

'allowed_origins' => ['*']

Instead:

'allowed_origins' => [
    'https://app.example.com'
]

Misconfigured CORS is still one of the most common API vulnerabilities.

15. Isolate Internal APIs

Internal APIs should never be public.

Protect internal services using:

VPN
private networking
API gateways
service mesh
mutual TLS

In Kubernetes:

use NetworkPolicies
isolate namespaces
disable public exposure

16. Prevent SQL Injection

Laravel query builder already helps prevent injection attacks.

Safe:

User::where('email', $email)->first();

Dangerous:

DB::statement(
    "SELECT * FROM users WHERE email = '$email'"
);

Never concatenate raw SQL from user input.

17. Secure Webhooks

Webhook endpoints should verify:

signatures
timestamps
replay protection

Never trust incoming webhook payloads automatically.

Recommended:

HMAC verification
request expiration windows
idempotency checks

18. Add Bot & WAF Protection

Production APIs should use:

Cloudflare WAF
bot filtering
IP reputation systems
geo restrictions

This reduces:

scraping
automated attacks
malicious crawlers

19. Monitor API Abuse in Real Time

Modern security requires observability.

Monitor:

sudden request spikes
failed authentication bursts
unusual token activity
abnormal geographic access

Useful metrics:

requests per second
error rates
latency spikes
token issuance frequency

20. Adopt Zero Trust Security

Modern API security assumes:

no request is trusted automatically.

Every request should verify:

identity
permissions
integrity
device context
risk signals

Zero trust becomes essential in:

microservices
multi-tenant SaaS
distributed systems

Production Laravel API Security Checklist

Before deploying production APIs:

HTTPS enforced
Authentication hardened
Rate limiting enabled
Token scopes configured
Input validation active
API logs centralized
Tokens rotated regularly
Security headers configured
CORS restricted
File uploads sandboxed
Webhooks verified
SQL injection protections reviewed
Internal APIs isolated
Monitoring enabled
WAF configured

Conclusion

Laravel provides an excellent foundation for building secure APIs.

But modern API security requires:

layered defenses
infrastructure awareness
observability
strict access control
zero trust principles

The most secure Laravel APIs are designed assuming:

attackers will probe endpoints
credentials may leak
infrastructure may fail
abuse attempts are continuous

Security is not middleware alone.

It is part of the entire API architecture.

Laravel Security Hardening in 2026: Production-Grade Security Checklist for Modern Laravel Applications

2026-05-23T19:15:45.223+07:00

Modern Laravel applications are no longer simple CRUD systems running on shared hosting. Today’s Laravel ecosystems power fintech platforms, enterprise dashboards, AI services, SaaS applications, internal government systems, and large-scale APIs. As infrastructure complexity increases, security can no longer rely only on validation rules and CSRF protection.

Laravel 2026 applications must be hardened across:

Application layer
API layer
Infrastructure layer
Database layer
Queue & worker isolation
Cloud networking
Authentication systems
Deployment pipelines

This guide covers practical Laravel security hardening strategies used in real production systems.

1. Enforce HTTPS Everywhere

The first security baseline is mandatory HTTPS.

Never allow:

mixed content
insecure cookies
HTTP fallback routes

Force HTTPS inside AppServiceProvider.

use Illuminate\Support\Facades\URL;

public function boot(): void
{
    if (app()->environment('production')) {
        URL::forceScheme('https');
    }
}

Also configure:

HSTS headers
Secure cookies
Reverse proxy trust

For Nginx:

add_header Strict-Transport-Security "max-age=31536000" always;

2. Harden Authentication Systems

Modern authentication should include:

MFA / 2FA
Device tracking
Session invalidation
Passwordless login
Risk-based authentication
Rate limiting

Laravel starter kits are only the beginning.

Recommended stack:

Laravel Sanctum
WebAuthn
OTP verification
Session fingerprinting

Example login throttling:

RateLimiter::for('login', function (Request $request) {
    return Limit::perMinute(5)->by(
        $request->ip()
    );
});

3. Use Strict Authorization Policies

Authentication checks identity.

Authorization checks permissions.

Never rely on frontend role checks.

Bad:

if ($user->role === 'admin')

Better:

Gate::authorize('update', $project);Or policy-based authorization:

public function update(User $user, Project $project): bool
{
    return $user->id === $project->owner_id;
}

4. Protect APIs Against Abuse

Public APIs are constant attack targets.

Add:

rate limiting
API scopes
IP reputation filtering
request signing
bot protection

Example API throttling:

Route::middleware('throttle:api')->group(function () {
    //
});

Advanced production systems use:

Cloudflare WAF
API gateways
token rotation
geo restrictions

5. Disable Debug Mode in Production

Never deploy with:

APP_DEBUG=true

Debug mode leaks:

SQL queries
stack traces
environment data
internal architecture

Production must always use:

APP_ENV=production
APP_DEBUG=false

6. Secure Environment Variables

Your .env file is one of the most sensitive assets.

Never:

commit .env
expose storage directories
allow public access
store secrets in frontend builds

Best practice:

use cloud secret managers
rotate credentials regularly
isolate staging and production credentials

Examples:

AWS Secrets Manager
Google Secret Manager
HashiCorp Vault

7. Harden File Upload Systems

File uploads are high-risk attack vectors.

Never trust:

extension names
MIME type alone
client validation

Laravel validation example:

$request->validate([
    'document' => [
        'required',
        'file',
        'mimes:pdf,docx',
        'max:2048',
    ]
]);

Additional protections:

virus scanning
private object storage
randomized filenames
image re-encoding
upload sandboxing

8. Add Security Headers

Security headers reduce browser-based attacks.

Recommended headers:

Content-Security-Policy
X-Frame-Options
X-Content-Type-Options
Referrer-Policy

Example middleware:

$response->headers->set(
    'X-Frame-Options',
    'SAMEORIGIN'
);

For CSP:

Content-Security-Policy:
default-src 'self';

9. Secure Laravel Queues & Workers

Queue workers often run with elevated privileges.

Hardening checklist:

isolate workers
separate queue credentials
limit Redis access
disable shell execution
use supervisor restrictions

Example Supervisor config:

user=forge
autorestart=true
stopasgroup=true
killasgroup=true

10. Prevent Mass Assignment Vulnerabilities

Never use unguarded models carelessly.

Bad:

protected $guarded = [];

Safer:

protected $fillable = [
    'name',
    'email',
];

Mass assignment bugs are still common in SaaS systems.

11. Encrypt Sensitive Data

Laravel encryption should be used for:

tokens
API secrets
recovery keys
financial metadata

Example:

use Illuminate\Support\Facades\Crypt;

$encrypted = Crypt::encryptString($token);

12. Database Security Hardening

Database users should never have full privileges.

Avoid:

root database users
wildcard permissions
public database exposure

Recommended:

private networking
least privilege access
read/write separation
audit logging

13. Container & Docker Security

Many Laravel apps now run inside containers.

Common mistakes:

running as root
exposing internal ports
embedding secrets in images

Safer Dockerfile:

RUN addgroup -g 1000 laravel
RUN adduser -u 1000 -G laravel -s /bin/sh -D laravel

USER laravel

14. Secure Laravel Horizon

Laravel Horizon exposes queue metrics and controls.

Never expose Horizon publicly.

Restrict access:

Horizon::auth(function ($request) {
    return auth()->check()
        && auth()->user()->is_admin;
});

Even better:

VPN-only access
internal subnet access
zero trust access policies

15. Add Centralized Security Monitoring

Security monitoring is essential for modern production systems.

Monitor:

login failures
suspicious IPs
privilege escalation
API abuse
abnormal queue behavior

Recommended observability stack:

OpenTelemetry
Grafana
Loki
Prometheus
Laravel Pulse

16. Prevent Supply Chain Attacks

Composer packages are now major attack surfaces.

Best practices:

audit dependencies
pin versions
remove abandoned packages
verify maintainers

Useful commands:

composer audit

And:

composer outdated

17. Secure CI/CD Pipelines

Attackers increasingly target deployment systems.

Protect:

GitHub Actions secrets
SSH deployment keys
container registries
production environments

Best practices:

ephemeral credentials
signed builds
branch protection
mandatory reviews

18. Use Zero Trust Infrastructure

Modern Laravel production environments should assume:

no network is trusted.

Principles:

identity verification
short-lived credentials
service isolation
least privilege networking

This becomes critical in:

Kubernetes
multi-service architectures
distributed APIs

Final Production Security Checklist

Before deploying Laravel production systems:

HTTPS enforced
Debug disabled
MFA enabled
CSP configured
Queue isolation enabled
Rate limiting active
Secrets externalized
Dependency audit completed
API protection enabled
Horizon restricted
Database isolated
Centralized logging enabled
Backups encrypted
CI/CD hardened

Conclusion

Laravel already provides an excellent security foundation.

But production-grade security in 2026 requires much more than framework defaults.

Real security hardening involves:

infrastructure isolation
operational monitoring
authentication architecture
deployment security
cloud-native protections

The most secure Laravel systems are built with:

layered defenses
least privilege access
observable infrastructure
continuous auditing

Security is no longer a feature.

It is part of the architecture itself.

Cara Main Game PS2 via LAN SMB di Tahun 2026 Menggunakan OPL + HDD/Flashdisk

2026-05-22T21:41:42.489+07:00

Komunitas PlayStation 2 masih sangat aktif sampai sekarang. Salah satu metode favorit untuk memainkan game PS2 tanpa DVD adalah menggunakan jaringan LAN SMB melalui Open PS2 Loader (OPL). Metode ini terkenal lebih cepat dibanding USB biasa dan jauh lebih awet karena tidak memakai optical drive.

Artikel ini membahas cara setting PS2 SMB terbaru di tahun 2026 menggunakan:

Free McBoot (FMCB)
Open PS2 Loader (OPL)
Kabel LAN
Sharing folder SMB di Windows/Linux
HDD internal, SSD, atau flashdisk sebagai storage game

Metode ini cocok untuk:

PS2 Fat
PS2 Slim
OPL terbaru
Pengguna jaringan rumah modern

Apa Itu SMB di PS2?

SMB (Server Message Block) adalah protokol sharing file melalui jaringan lokal. Dengan SMB, PS2 dapat membaca game ISO langsung dari komputer atau NAS tanpa perlu membakar DVD.

Keunggulan SMB dibanding USB:

Fitur	USB	SMB LAN
Kecepatan loading	Lambat	Lebih cepat
FMV patah-patah	Kadang iya	Lebih stabil
Kompatibilitas game	Sedang	Tinggi
Umur USB	Cepat panas	Lebih aman
Cocok untuk game besar	Tidak selalu	Sangat cocok

Kebutuhan yang Harus Disiapkan

Sebelum mulai, siapkan beberapa perangkat berikut:

Hardware

PS2 Fat atau Slim
Memory Card Free McBoot
Kabel LAN RJ45
Router atau koneksi langsung ke PC
Flashdisk/HDD/NAS/SSD

Software

Open PS2 Loader terbaru
OPL Manager
SMB Server (Windows Sharing atau Samba Linux)

Struktur Folder Game OPL SMB

Buat folder sharing misalnya:

PS2SMB/

Di dalamnya buat struktur:

CD/
DVD/
ART/
CFG/
THM/
VMC/

Keterangan:

DVD untuk game DVD ISO
CD untuk game format CD
ART untuk cover game
CFG untuk konfigurasi OPL
THM untuk theme
VMC untuk virtual memory card

Cara Sharing Folder SMB di Windows 11

1. Aktifkan SMB 1.0

Walaupun SMB1 sudah tua, OPL masih menggunakan kompatibilitas SMB klasik.

Masuk ke:

Control Panel → Programs → Turn Windows features on or off

Centang:

SMB 1.0/CIFS File Sharing Support

Restart komputer.

2. Share Folder

Klik kanan folder:

PS2SMB → Properties → Sharing

Aktifkan:

Advanced Sharing

Berikan nama share:

PS2SMB

Permission:

Everyone → Full Control

3. Atur IP Static PC

Contoh:

IP Address : 192.168.1.10
Subnet     : 255.255.255.0
Gateway    : 192.168.1.1

Setting OPL SMB di PS2

Masuk ke:

Settings → Network Settings

Isi:

Parameter	Contoh
PS2 IP	192.168.1.20
Mask	255.255.255.0
Gateway	192.168.1.1
SMB Server Address	192.168.1.10
Share Name	PS2SMB
Username	guest
Password	kosong

Simpan konfigurasi lalu restart OPL.

Format Penamaan ISO PS2

Gunakan format:

SLUS_123.45.Nama Game.iso

Contoh:

SLUS_209.46.God of War.iso

Format ini penting agar cover dan compatibility database terbaca dengan benar.

Cara Transfer Game ke Folder SMB

Cukup copy file ISO ke folder:

DVD/

Untuk game CD:

CD/

Tidak perlu install seperti WinHIIP.

Menggunakan OPL Manager

Agar tampilan lebih rapi:

Install OPL Manager
Scan folder game
Download cover otomatis
Generate ART dan CFG

Keuntungan:

Cover game otomatis
Informasi game lengkap
Setting compatibility lebih mudah

Setting Optimal OPL Tahun 2026

Berikut setting yang umum dipakai komunitas:

Setting	Rekomendasi
ETH Device Start Mode	Auto
Default Menu	ETH Games
Enable Write Operations	Off
IGR	Off jika game crash
GSM	Sesuaikan TV

Game PS2 yang Cocok via SMB

Beberapa game berjalan sangat baik lewat SMB:

God of War
Resident Evil 4
Shadow of the Colossus
Final Fantasy X
Persona 4
Gran Turismo 4
Black
Okami

Game FMV berat biasanya lebih lancar dibanding USB.

Kelebihan SMB Dibanding HDD Internal

Walaupun HDD internal tetap paling cepat untuk PS2 Fat, SMB punya beberapa keunggulan:

1. Mudah Menambah Game

Tidak perlu bongkar HDD.

2. Storage Lebih Fleksibel

Bisa menggunakan:

SSD
NAS
HDD eksternal
Server Linux

3. Multi Device

Satu server bisa dipakai beberapa PS2.

Troubleshooting OPL SMB

OPL Tidak Menemukan Server

Cek:

Firewall Windows
Kabel LAN
IP Address
SMB1 aktif

Game Tidak Muncul

Pastikan:

ISO berada di folder DVD
Nama file benar
Share folder permission benar

Loading Lama

Gunakan:

Kabel LAN berkualitas
SSD/NVMe pada server
Router gigabit

SMB di Linux Menggunakan Samba

Untuk pengguna Linux:

Install Samba:

sudo apt install samba

Contoh konfigurasi:

[PS2SMB]
path = /srv/ps2
browseable = yes
read only = no
guest ok = yes

Restart service:

sudo systemctl restart smbd

Kombinasi Setup PS2 Terbaik Tahun 2026

Berikut setup favorit komunitas retro gaming:

Komponen	Rekomendasi
FMCB	Versi terbaru
OPL	OPL Daily Build
Storage	SSD SATA
Network	Gigabit Router
Display	HDMI Converter PS2

Apakah SMB Masih Worth It di Tahun 2026?

Jawabannya masih sangat worth it.

Bahkan banyak komunitas retro gaming modern lebih memilih SMB karena:

Setup fleksibel
Tidak merusak optik PS2
Loading lebih stabil
Mudah backup game
Bisa integrasi NAS rumah

Dengan OPL terbaru, kompatibilitas game juga semakin baik.

Kesimpulan

Main game PS2 via LAN SMB masih menjadi salah satu metode terbaik di tahun 2026. Dengan kombinasi Free McBoot dan Open PS2 Loader, pengguna bisa menikmati game PS2 langsung dari jaringan tanpa DVD.

Selain lebih cepat dibanding USB, metode SMB juga lebih aman untuk hardware PS2 yang usianya sudah cukup tua.

Jika sebelumnya kamu sudah menggunakan:

Free McBoot
uLaunchELF
OPL
HDD internal

maka SMB adalah upgrade berikutnya yang wajib dicoba.

Free McBoot dan uLaunchELF: Kombinasi Wajib untuk Modding PlayStation 2

2026-05-16T21:54:40.273+07:00

Bagi penggemar modding PlayStation 2, dua nama yang hampir tidak bisa dipisahkan adalah Free McBoot (FMCB) dan uLaunchELF. Keduanya menjadi fondasi utama untuk menjalankan homebrew, backup game, emulator, hingga Open PS2 Loader (OPL) tanpa perlu modchip tambahan.

Di artikel lama DityaLovers tentang uLaunchELF, aplikasi ini dijelaskan sebagai file explorer untuk PS2 yang mampu membuka dan menjalankan berbagai file dari memory card maupun flashdisk. Sekarang, mari kita bahas bagaimana Free McBoot dan uLaunchELF bekerja bersama untuk membuka fitur tersembunyi PS2.

Apa Itu Free McBoot?

Free McBoot adalah exploit memory card PS2 yang memungkinkan konsol menjalankan aplikasi homebrew secara otomatis saat booting.

Dengan FMCB, pengguna bisa:

Menjalankan Open PS2 Loader (OPL)
Membuka uLaunchELF
Menjalankan emulator retro
Memutar video dengan SMS Player
Mengakses file manager PS2
Menjalankan aplikasi ELF tanpa modchip

FMCB menjadi sangat populer karena instalasinya relatif aman dan tidak memerlukan solder hardware seperti modchip lama.

Peran uLaunchELF dalam Free McBoot

uLaunchELF berfungsi sebagai “Windows Explorer” di PS2. Hampir semua pengguna FMCB memakai uLaunchELF untuk:

Copy file ELF
Install aplikasi homebrew
Backup save game
Mengatur memory card
Memindahkan file OPL
Mengakses flashdisk USB

Tanpa uLaunchELF, proses manajemen file di PS2 akan jauh lebih sulit.

Kenapa Kombinasi Ini Sangat Populer?

Pada era PS2 modern, kombinasi FMCB + uLaunchELF dianggap setup standar karena:

1. Tidak Perlu Modchip

Banyak pengguna PS2 slim takut risiko solder modchip merusak motherboard. FMCB menawarkan solusi softmod yang jauh lebih aman.

2. Bisa Menjalankan Game dari HDD atau USB

Setelah FMCB aktif, pengguna bisa menjalankan OPL untuk memainkan game dari:

Harddisk internal
SMB Network
USB Flashdisk

uLaunchELF membantu proses setup file dan konfigurasi OPL.

3. Backup Save Game Jadi Mudah

Save game PS2 sangat rentan corrupt, terutama memory card murah. Dengan uLaunchELF, backup save ke flashdisk bisa dilakukan hanya dalam beberapa langkah.

4. Mendukung Banyak Homebrew

Komunitas homebrew PS2 masih aktif sampai sekarang. Banyak aplikasi modern masih kompatibel dengan FMCB dan uLaunchELF.

Contohnya:

RetroArch PS2
GSM Selector
POPStarter
OPL Daily Builds
ESR Disc Launcher

Cara Menggunakan uLaunchELF untuk Install OPL

Berikut langkah sederhana:

Persiapan

Yang dibutuhkan:

PS2 dengan FMCB
Flashdisk FAT32
File OPL .ELF
uLaunchELF

Langkah Install

Copy OPL.ELF ke flashdisk
Colok USB ke PS2
Jalankan uLaunchELF
Buka mass:/
Copy file OPL
Paste ke memory card atau HDD
Tambahkan shortcut di menu FMCB

Setelah itu OPL bisa dijalankan langsung dari menu utama PS2.

uLaunchELF vs File Browser Bawaan PS2

Browser bawaan PS2 sangat terbatas. Hanya bisa melihat memory card dan disc.

Sedangkan uLaunchELF mendukung:

Fitur	Browser PS2	uLaunchELF
Copy file	Tidak	Ya
USB support	Tidak	Ya
Jalankan ELF	Tidak	Ya
FTP	Tidak	Ya
HDD internal	Tidak	Ya
Edit konfigurasi	Tidak	Ya

Karena itulah hampir semua tutorial modding PS2 menggunakan uLaunchELF.

Tips Aman Menggunakan uLaunchELF

Gunakan Flashdisk FAT32

PS2 lebih stabil membaca FAT32 dibanding NTFS atau exFAT pada versi lama.

Jangan Hapus Folder Sistem FMCB

Folder seperti:

BOOT
SYS-CONF
FREEMCB

sangat penting untuk booting FMCB.

Backup Memory Card Secara Berkala

Gunakan uLaunchELF untuk copy seluruh isi memory card ke USB.

Apakah uLaunchELF Masih Relevan di 2026?

Jawabannya: masih sangat relevan.

Komunitas PS2 retro gaming terus berkembang karena:

Harga PS2 masih murah
Banyak kolektor retro
Emulator PS2 belum selalu stabil di perangkat low-end
Sensasi bermain di hardware asli tetap berbeda

uLaunchELF masih menjadi tool utama untuk maintenance dan homebrew PS2.

Kesimpulan

Jika Free McBoot adalah “pintu masuk” modding PS2, maka uLaunchELF adalah alat utama untuk mengelola semuanya.

Kombinasi keduanya membuat PlayStation 2 memiliki fitur jauh lebih modern dibanding fungsi bawaan Sony dahulu.

Bagi penggemar retro gaming dan modding konsol, memahami cara kerja uLaunchELF adalah skill dasar yang wajib dimiliki.

uLaunchELF PS2: File Explorer Legendaris untuk Modding dan Backup Save Game

2026-05-16T21:51:06.528+07:00

Kalau kamu pernah utak-atik PlayStation 2, kemungkinan besar kamu pernah dengar nama uLaunchELF atau biasa disingkat uLE. Aplikasi homebrew ini sudah jadi “senjata wajib” bagi pengguna PS2 modchip, Free McBoot, maupun harddisk internal sejak era warnet PS2 dan rental game dulu.

Artikel lama di DityaLovers Blog pernah membahas fungsi dasar uLaunchELF sebagai file manager PS2. Sekarang, mari kita bahas lebih lengkap fitur, manfaat, dan kenapa software ini masih relevan di tahun 2026.

Apa Itu uLaunchELF?

uLaunchELF adalah aplikasi homebrew untuk PS2 yang berfungsi seperti Windows Explorer di PC. Dengan aplikasi ini, pengguna dapat membuka, menyalin, menghapus, menjalankan, hingga memindahkan file dari berbagai media penyimpanan di PS2. ([Dityalovers][1])

Selain menjadi file manager, uLaunchELF juga bisa digunakan untuk:

Menjalankan file .ELF
Backup dan restore save game
Mengelola harddisk PS2
Membuka file TXT dan JPG
FTP transfer via jaringan
Launch aplikasi homebrew lain
Instal booting Free McBoot
Menjalankan emulator dan utility PS2

Bahkan komunitas modding PS2 menyebut uLaunchELF sebagai software paling penting untuk modifikasi PS2. ([ConsoleMods][2])

Fitur Utama uLaunchELF

Berikut beberapa fitur populer dari uLaunchELF:

1. File Browser Lengkap

uLaunchELF dapat membaca berbagai direktori PS2 seperti:

mc0:/ → Memory Card slot 1
mc1:/ → Memory Card slot 2
mass:/ → USB Flashdisk
hdd0:/ → Harddisk internal PS2
cdfs:/ → CD/DVD PS2
host:/ → Koneksi jaringan/PC

Fitur ini membuat transfer save game atau aplikasi homebrew jadi jauh lebih mudah. ([Gmzware][3])

2. Menjalankan File ELF

File .ELF di PS2 mirip seperti .EXE di Windows. Dengan uLaunchELF, kamu bisa menjalankan:

Open PS2 Loader (OPL)
Emulator PS1/Arcade
RetroArch
HDLoader
SMS Media Player
Utility patcher dan installer

Karena itulah uLaunchELF sering jadi launcher utama pada memory card Free McBoot.

3. Backup Save Game PS2

Salah satu fungsi favorit pengguna PS2 adalah backup save game ke flashdisk.

Langkah sederhananya:

Masuk ke mc0:/
Pilih folder save game
Tekan R1
Pilih Copy
Masuk ke mass:/
Paste save game

Fitur ini sangat berguna untuk mencegah save corrupt atau memory card rusak.

4. Booting Langsung dari Memory Card

Pengguna modchip seperti Matrix atau Modbo sering memakai uLaunchELF sebagai boot utama dari memory card.

Bahkan banyak tutorial lama menggunakan kombinasi tombol seperti:

Tahan R1
Tahan R2
DEV1 mode

untuk langsung masuk ke uLaunchELF saat PS2 dinyalakan. ([Dityalovers][1])

Perbedaan uLaunchELF dan wLaunchELF

Versi modern dari uLaunchELF sekarang dikenal sebagai wLaunchELF. Proyek ini merupakan penerus resmi komunitas homebrew PS2. ([ConsoleMods][2])

Beberapa peningkatan wLaunchELF:

Support exFAT
Kompatibilitas USB lebih baik
Perbaikan FTP server
Stabilitas lebih tinggi
Dukungan homebrew terbaru

Meski begitu, banyak pengguna masih menyebutnya “uLaunchELF” karena sudah menjadi nama legendaris di komunitas PS2.

Kenapa uLaunchELF Masih Populer?

Walaupun PlayStation 5 dan emulator modern sudah berkembang, komunitas PlayStation 2 masih sangat aktif.

Alasan uLaunchELF tetap dipakai:

PS2 masih populer di Indonesia
Banyak rental dan kolektor retro
Mendukung homebrew
Sangat ringan
Kompatibel dengan Free McBoot
Mempermudah instalasi OPL dan game HDD

Bahkan di forum Reddit masih banyak pengguna baru yang belajar menggunakan uLaunchELF untuk instal emulator dan OPL di PS2 mereka. ([Reddit][4])

Cara Install uLaunchELF di PS2

Menggunakan Free McBoot

Cara paling mudah:

Copy file BOOT.ELF ke flashdisk
Jalankan File Browser
Masuk ke mass:/
Copy file ELF
Paste ke memory card
Tambahkan shortcut di FMCB Configurator

Menggunakan CD/DVD

Metode klasik:

Download ISO uLaunchELF
Burn ke CD/DVD
Jalankan di PS2 modchip

Metode ini populer di era PS2 optik sebelum OPL booming. ([Dityalovers][1])

Kesimpulan

uLaunchELF bukan sekadar file manager biasa. Software ini adalah fondasi utama dunia modding PS2. Mulai dari backup save, menjalankan homebrew, instal Free McBoot, hingga launch OPL — semuanya hampir selalu melibatkan uLaunchELF.

Bagi pecinta PlayStation 2, aplikasi ini masih menjadi tool wajib bahkan setelah lebih dari 20 tahun sejak PS2 dirilis.

Kalau kamu masih punya PS2 di rumah, uLaunchELF adalah aplikasi pertama yang wajib dicoba.

Referensi dan Dokumentasi

Laravel 13 AI SDK: Building Real AI Features Without Fighting the Framework

2026-05-05T01:07:00.001+07:00

Laravel has always had a habit of absorbing complexity and returning something clean on the other side. The new Laravel 13 AI SDK follows that same pattern—but this time the complexity isn’t just HTTP or queues. It’s AI integration itself.

Most developers don’t struggle with calling AI APIs. They struggle with everything around it: provider differences, streaming quirks, structured output parsing, retries, tool calling, embeddings, and glue code that slowly turns into a second framework inside your framework.

The Laravel AI SDK tries to collapse all of that into something that still feels like Laravel. Not “Laravel inspired”. Actually Laravel.

The real shift in Laravel 13: AI is no longer “external”

Before this SDK, integrating AI in Laravel usually looked like:

OpenAI PHP client (or similar)
custom service layer
manual prompt handling
JSON decoding everywhere
ad-hoc retry logic
scattered controller logic

It worked, but it never felt native.

Laravel 13 changes that assumption. AI is now treated like cache, queues, and HTTP client—a first-class system, not a side integration.

The SDK provides a unified API across providers like OpenAI, Anthropic, Gemini, and others while keeping a consistent Laravel-style interface.

The core idea: “Agents” instead of “requests”

The most important mental model shift is this: you don’t call AI. You define an agent that behaves like a system.

An agent is a PHP class that owns:

instructions (system behavior)
conversation context
tools (functions it can call)
structured output rules
optional memory

Instead of writing:

$response = OpenAI::chat([...]);

You define something like:


class SupportAgent implements Agent
{
    public function instructions(): string
    {
        return "You are a strict support assistant. Be precise.";
    }
}

And use it like a service:

$response = app(SupportAgent::class)->prompt("My order is late");

AI logic stops leaking into controllers. That’s the real win.

Structured output: where things get serious

If you’ve ever parsed AI responses in production, you know the pain: invalid JSON, missing fields, and inconsistent formatting.

Laravel AI SDK solves this by enforcing structure using PHP schemas.


public function schema(JsonSchema $schema): array
{
    return [
        'score' => $schema->integer()->required(),
        'confidence' => $schema->string()->required(),
    ];
}

This turns AI output into something you can safely rely on in backend logic.

Tools: where AI stops being a chatbot

Tools allow an AI agent to call real application logic:

database queries
API calls
file search
internal services

This is where “AI feature” becomes “AI system”.

Instead of just generating text, AI can execute workflows. Laravel’s existing architecture—queues, jobs, service container—makes this feel natural.

Streaming, queues, and real UX thinking

The SDK doesn’t treat AI as a blocking request. You can stream responses, queue long generations, and broadcast events in real time.

This matters because AI latency is unpredictable. Laravel leans on queues and events instead of reinventing async patterns.

Embeddings and vector workflows become native patterns

Embeddings support enables semantic search, document retrieval, and recommendation systems without external glue code.

Most real-world AI features aren’t chatbots—they are retrieval systems wrapped in chat interfaces.

What actually changes in your architecture

Before:

Controllers contain AI logic
Prompt strings scattered everywhere
JSON parsing in multiple places
No consistent retry or tool system

After:

Agents own behavior
Controllers just call services
AI logic becomes testable
Structured outputs replace fragile parsing
Tools extend system capabilities cleanly

Fewer failure points, not just cleaner code.

The uncomfortable truth

The SDK doesn’t make AI easy. It removes repetition, not responsibility.

You still need to understand:

prompt design
context limits
tool safety
cost control
latency tradeoffs

What Laravel removes is the distracting glue code around those problems.

When you shouldn’t use it

This SDK is not always necessary. It may be overkill for:

simple one-off completions
static prompt utilities
scripts without structure or tools

In those cases, direct API calls can still be simpler.

Final thoughts

Laravel 13’s AI SDK is not interesting because it adds AI. It’s interesting because it normalizes AI inside backend architecture.

It treats AI like something that can be structured, tested, queued, extended with tools, and versioned.

Not smarter prompts. Cleaner systems.

Laravel Query Scopes Like a Pro (Clean, Reusable & Powerful Eloquent Queries)

2026-05-05T00:45:00.000+07:00

If your Laravel queries are starting to look messy, repeated, or hard to maintain, you’re not alone. Most projects eventually hit this wall where Eloquent logic is scattered across controllers, services, or even views.

This is exactly where Query Scopes become a game changer. They help you turn repetitive query logic into clean, reusable, and expressive methods.

Why Query Scopes Matter

Without scopes, your code often looks like this:

$users = User::where('is_active', 1)
    ->whereNotNull('email_verified_at')
    ->where('role', 'admin')
    ->get();

Now imagine repeating similar filters across multiple controllers. That’s when things get:

Hard to maintain
Easy to duplicate
Difficult to debug

Query Scopes solve this by centralizing your query logic inside the model.

What Are Query Scopes in Laravel?

Laravel Query Scopes are methods defined inside a model that allow you to reuse query constraints.

There are two types:

Local Scopes
Global Scopes

1. Local Scopes (Most Common & Useful)

Local scopes let you define reusable query parts inside a model.

Example: Active Users Scope

class User extends Model
{
    public function scopeActive($query)
    {
        return $query->where('is_active', 1);
    }
}

Usage:

$users = User::active()->get();

Now your query becomes:

Cleaner
Reusable
Easier to read

Scopes with Parameters

public function scopeRole($query, $role)
{
    return $query->where('role', $role);
}

Usage:

$admins = User::active()->role('admin')->get();

Real-World Example (Production Style)

class Order extends Model
{
    public function scopePaid($query)
    {
        return $query->where('status', 'paid');
    }

    public function scopeThisMonth($query)
    {
        return $query->whereMonth('created_at', now()->month);
    }
}

Usage:

$orders = Order::paid()->thisMonth()->get();

This is how clean production queries should look.

2. Global Scopes (Automatic Filters)

Global scopes apply automatically to every query.

Example: Only Active Users Everywhere

use Illuminate\Database\Eloquent\Builder;

class ActiveScope implements \Illuminate\Database\Eloquent\Scope
{
    public function apply(Builder $builder, Model $model)
    {
        $builder->where('is_active', 1);
    }
}

Apply in Model:

class User extends Model
{
    protected static function booted()
    {
        static::addGlobalScope(new ActiveScope);
    }
}

Now every query automatically filters active users.

How Query Scopes Improve Code Quality

Without scopes:

Logic scattered everywhere
Hard to refactor
Repeated conditions

With scopes:

Centralized logic
Cleaner controllers
Easier testing
Better readability

Visual Understanding

Without Scopes:

Controller → messy query → repeated logic → hard maintenance

With Scopes:

Controller → clean call → model handles logic → reusable system

Combining Scopes (Power Move)

User::active()
    ->role('admin')
    ->latest()
    ->get();

This is where Laravel Eloquent becomes really expressive.

Best Practices

Keep scope logic simple and focused
Use meaningful names (active, paid, verified)
Avoid heavy business logic inside scopes
Combine scopes instead of duplicating queries
Prefer local scopes unless global filtering is required

Understanding the N+1 Problem in Laravel

2026-05-05T00:31:00.003+07:00

If you’ve worked with Laravel for a while, you’ve probably heard developers mention the “N+1 problem.” It’s one of those issues that quietly hurts performance without obvious errors, making your application slow as data grows.

In this article, we’ll break down what the N+1 problem is, why it happens in Laravel, and how to fix it properly.

What is the N+1 Problem?

The N+1 problem happens when your application executes:

1 query to retrieve a list of records
N additional queries to retrieve related data for each record

Instead of a single optimized query strategy, you end up with many repeated database calls.

Simple Example

Imagine you have two models:

Post
Comment

Each post has many comments. Now consider this code:


$posts = Post::all();

foreach ($posts as $post) {
    echo $post->comments->count();
}

What actually happens:

1 query: get all posts
N queries: get comments for each post

If you have 100 posts, Laravel executes 101 queries. That’s the N+1 problem.

Why It Becomes a Problem

The issue isn’t noticeable with small datasets. But as your application grows:

Database load increases
Response time slows down
Server resources get wasted
API responses become inconsistent under load

In production systems, this can become a serious bottleneck.

How to Detect N+1 in Laravel

You can detect it using query logging or debugging tools.


DB::enableQueryLog();

// your code here

dd(DB::getQueryLog());

Or use tools like:

Laravel Debugbar
Telescope

The Fix: Eager Loading

Laravel provides a solution called eager loading. Instead of loading relationships one by one, you load them upfront.

Fixed Example


$posts = Post::with('comments')->get();

foreach ($posts as $post) {
    echo $post->comments->count();
}

What Changed?

1 query for posts
1 query for all related comments

Now Laravel executes only 2 queries total, regardless of how many posts exist.

When You Need Multiple Relationships


$posts = Post::with('comments.user')->get();

This prevents hidden N+1 issues across nested relationships.

Nested Relationships

Laravel also supports deep eager loading:


$posts = Post::with('comments.user')->get();

This loads:

Posts
Comments
Users of each comment

All in optimized queries.

Lazy vs Eager Loading

Type	Behavior	Performance
Lazy Loading	Loads relation when accessed	Can cause N+1
Eager Loading	Loads upfront	Optimized

Best Practices

Always consider relationships when looping data
Use with() for known relationships
Avoid accessing relationships inside loops without eager loading
Monitor queries during development
Use Debugbar or Telescope regularly

Laravel Filament: The Best Admin Panel for Laravel Developers in 2025

2025-10-09T14:56:00.004+07:00

What Is Laravel Filament?

Laravel Filament is a modern admin panel and form builder designed for Laravel developers who want to create professional, data-driven dashboards without the complexity of front-end frameworks. It runs on Livewire and Alpine.js, making it fully reactive and interactive while remaining purely PHP-based.

With Filament, developers can manage database records, create dynamic forms, and design elegant back-office systems in minutes. It is widely adopted because it offers both simplicity and flexibility for building administrative tools.

Key Features of Laravel Filament

Laravel Filament provides a clean, Tailwind CSS-based interface that looks professional and works beautifully on all screen sizes. Its design is minimal and consistent, which allows developers to focus on logic rather than styling.

One of its most appealing features is its one-line CRUD generation. By using a single command—php artisan make:filament-resource—developers can instantly generate listing pages, create and edit forms, and delete functionalities. Each resource comes with built-in search, sorting, and pagination options, which can be customized with straightforward PHP configuration.

The Filament ecosystem continues to expand through community-driven plugins. These include Filament Shield for managing user roles and permissions, Media Library integration for handling file uploads, and powerful dashboard widgets for analytics. Developers can extend functionality easily without touching JavaScript or complex configurations.

Filament also supports role-based access control by integrating seamlessly with Spatie Roles and Permissions. This makes it easy to assign specific permissions to administrators, editors, and general users, ensuring that sensitive data is properly protected.

Another major strength of Filament is its developer-first philosophy. Everything is configured through PHP, which aligns perfectly with Laravel’s design patterns. Relationships, validation, and component reuse are all intuitive. The framework prioritizes productivity, maintainability, and performance.

Example: Building a Blog Dashboard

Creating a blog management system with Filament is simple. You can generate a new resource for blog posts using an Artisan command. Once the resource is created, defining the form fields—such as title, content, and publication status—can be done directly within the resource file. Filament automatically generates the necessary pages for listing, creating, editing, and deleting blog posts.

Within minutes, developers can have a fully functional content management system without writing front-end code. Every page is responsive and styled automatically, making it suitable for production use immediately.

The Laravel Filament Ecosystem in 2025

As of 2025, Filament has grown beyond a standard admin panel. It now includes standalone packages like Filament Forms and Filament Tables, which can be integrated into any Laravel project. There are also official tools for notifications, no-code page building, and plugin development.

The Filament community is active and continues to contribute new features, extensions, and tutorials. This growing ecosystem ensures that Filament remains relevant and future-proof for modern web development.

How to Install Laravel Filament

Installing Filament is simple and beginner-friendly. Developers can install it via Composer and create their first admin user using Artisan commands:


composer require filament/filament
php artisan make:filament-user

After installation, you can visit the /admin route in your browser to access your dashboard. From there, you can start creating resources and managing your application data instantly.

Why Laravel Filament Is the Future of Admin Panels

Laravel Filament combines speed, flexibility, and modern design in a way that no other Laravel admin panel does. It allows developers to create polished dashboards for a variety of applications such as blogs, business tools, analytics panels, and SaaS platforms.

It reduces development time significantly and provides a strong foundation for teams that value maintainability and scalability. Filament’s consistent syntax, excellent documentation, and active community make it a smart choice for any Laravel developer looking to modernize their workflow.

For more information, visit the official website at https://filamentphp.com.

Laravel 8 Jetstream Livewire + Blade

2020-11-08T22:56:00.000+07:00

Salah satu fitur baru Laravel versi 8 adalah Laravel Jetstream. Laravel Jetstream menggantikan scafolding built in otentifikasi laravel yang lama, dilengkapi dengan fitur two factor authentification (2FA) dan session management (berguna untuk menghapus session yang aktif jika melakukan login di browser yang berbeda) serta dilengkapi dukungan API Laravel Sanctum. Laravel jetstream mendukung 2 stack teknologi dalam implementasinya, bisa menggunakan Liveware + Blade atau Inertia.js + Vue. Pada tutorial ini kita akan mencoba menggunakan Livewire + Blade, untuk dapat menginstall laravel 8 dibutuhkan php versi 7.3+ beserta ekstensi php yg dibutuhkan laravel, node js dan npm (node package manager), selengkapnya dapat dibaca pada halaman dokumentasi instalasi laravel.

Buat Database Baru (MySQL)

# Buat database baru menggunakan mysql dengan nama database jetstream
$ mysql -uroot -p
# Masukan root password mysql
mysql> create database jetstream;
mysql> exit

Instalasi Jetstream

Untuk menggunakan fitur jetstream, gunakan argumen --jet setelah nama project. Tutorial ini menggunakan nama project "jetstream" untuk nama project laravelnya.

$ laravel new jetstream --jet
> 0 (Untuk livewire)
> no (Jika aplikasi tidak digunakan untuk tim)
$ cd jetstream
$ npm install && npm run dev
# Buka file .env di root aplikasi dan konfigurasi username, password dan nama database
DB_DATABASE=jetstream
DB_USERNAME=root
DB_PASSWORD=<MYSQL_PASSWORD>
$ php artisan migrate
$ php artisan serve
# Buka browser ketikkan alamat url localhost:8000

Laravel Jetstream running on Valet

Registrasi User Baru

Halaman Dashboard Jetstream

Browser Session Management

Enable Two Factor Authentification

Two Authentification Challenge On Login

Struktur Jetstream

Views / Pages

Jika menggunakan Livewire views terletak pada direktori resources/views, jika menggunakan Inertia views terletak pada direktori resources/js/Pages

Dashboard (Halaman Utama)

View halaman utama / dashboard terletak pada direktori resources/views/dashboard.blade.php jika menggunakan Livewire dan resoureces/js/Pages/Dashboard.vue jika menggunakan Inertia

Actions

Aksi / actions class terdapat pada direktori app/Actions. Class pada direktori ini merupakan bawaan laravel yg terdiri dari 2 component Fortify dan Jetstream. Aksi standar contohnya untuk membuat user baru, update password, update profil dan menghapus user.

Tailwind

Tailwind digunakan untuk melakukan kompilasi CSS atau assets aplikasi. File konfigurasi tailwind terletak pada tailwind.config.js

Livewire Component

Jetstream menggunakan berbagai macam komponen blade seperti button atau modal untuk mendukung teknologi Liverwire. Kita dapat publish komponen Livewire supaya dapat dikustomisasi tampilannya dengan menggunakan artisan command

php artisan vendor:publish --tag=jetstream-views

Mengganti Logo Aplikasi

Jetstream menggunakan svg untuk logo pada aplikasi baik pada halaman otentifikasi ataupun pada navbar aplikasi. Untuk dapat mengganti custom logo aplikasi, ubahlah file-file berikut :

resources/views/vendor/jetstream/components/application-logo.blade.php
resources/views/vendor/jetstream/components/authentification-card-logo.blade.php
resources/views/vendor/jetstream/components/application-mark.blade.php

Contoh script ganti logo aplikasi (resources/views/vendor/jetstream/components/application-logo.blade.php)

Ganti Logo Aplikasi Jetstream (SVG)

Install BRImo pada iPhone yang di Jailbreak

2020-11-03T00:16:00.000+07:00

This device does not meet minimum security requirements for this application

Yes, bahkan tweak sekelas xCon sama Liberty Lite juga tidak mampu membypass jailbreak detection BRImo. Berbagai macam tweak bypass detection di Cydia sudah dicoba tapi hasilnya nihil. Setelah sekian lama menggunakan aplikasi BRI Mobile yang pake token SMS, anehnya hanya di iPhone saja yang menggunakan token SMS, aplikasi BRI Mobile di android tidak menggunakan ~~token SMS~~💩. BRImo menurut saya cocoklah untuk kaum milenial 😁

Salah satu alasan kenapa masih mempertahankan jailbreak menurut pandangan saya adalah kita bisa mendapatkan akses full (root) terhadap iPhone atau iDevice kita tanpa ada batasan dari penyedia sistem operasi.

"my own phone is my own rule"

Bagi pengguna iOS 14.0.x kebawah dapat melakukan jailbreak dengan menggunakan software checkra1n. Berikut ini adalah cara untuk menginstall BRImo dengan menggunakan tweak AppStore++ by CokePokes. Dengan bantuan tweak ini, kita dapat melakukan instalasi upgrade / downgrade versi aplikasi di AppStore. Jadi supaya bisa lancar aplikasi BRIMo silahkan downgrade ke versi 1.3.x (DWYOR)

Pastikan Cydia sudah terinstall di iPhone, buka Cydia, pilih tab menu Sources, tap edit kemudian tap add, ketikan alamat repo berikut lalu tap Add Source:

https://rejail.ru/

Tambah Repo Baru di Cydia

Update Repository Sources

Setelah berhasil menambahkan repo, pilih tab menu Search cari tweak dengan nama AppStore++ dari repo rejail.ru, kemudian install tweak, setelah berhasil install, device akan melakukan restart springboard (respring).

AppStore++ Tweak

Buka App Store, cari aplikasi BRImo, tap dan hold pada tombol install/update, maka akan muncul popup, pilih Upgrade / Downgrade kemudian pilih versi aplikasi 1.3.3

Pilih Versi Aplikasi

Annoying popup sudah hilang 😝

Android Login Retrofit OAuth2

2020-11-02T10:50:00.001+07:00

Pada tutorial kali ini, saya akan membahas tutorial pemrograman android dengan menggunakan kotlin. Library yang akan digunakan adalah Retrofit untuk http request ke API Server yang menggunakan otentifikasi OAuth atau JWT, OkHttpClient untuk request interceptor (bearer token / api key akan disisipkan saat request ke protected resources) dan Kotlin Android Extensions untuk menggantikan fungsi findViewById.

OkHttpClient Interceptor juga dapat digunakan untuk intersepsi request ketika bearer token expired otomatis melakukan request token baru dengan metode refresh token pada OAuth2. Berikut merupakan resume langkah-langkah pembuatannya dengan menggunakan android studio.

Konfigurasi Library pada Gradle (Module)

Buat project baru pada android studio dengan Empty Activiy, isi nama aplikasi dan nama package, tempat penyimpanan project, minimum OS (SDK) dan pilih Kotlin sebagai bahasa pemrogramannya. Pada jendela project browser, buka file Gradle Scripts > build.gradle (Module: <nama_app>.app). Tambahkan baris berikut lalu lakukan sync gradle.

Buatlah package baru dengan susunan sebagai berikut:

com.<company_name>.<app_name>

data

requests
responses

ui
utils

Package Utils

Buatlah Kotlin File/Class dengan tipe object dibawah package utils dengan nama Constants. File ini digunakan untuk membuat konstanta / variabel yg bersifat tetap dan dapat memudahkan jika suatu saat terjadi perubahan variabel pada aplikasi dan variabel sudah digunakan di banyak komponen aplikasi. File Constants ini berisi pengaturan base url API maupun daftar endpoint API.

Buatlah Kotlin File/Class dengan tipe Class dibawah package utils dengan nama SessionManager. File ini berisi SharedPreferences android yang dapat digunakan untuk menyimpan / mengakses data seperti session jika di pemrograman berbasis web. Class SessionManager digunakan untuk menyimpan Bearer Token dari hasil response login yang sukses. Bearer token ini berfungsi seperti apiKey untuk mengakses service atau endpoint yang diproteksi. SharedPreferences ini dapat diakses di activity / fragment android.

Konfigurasi Retrofit

Sebelum membuat class dan interface Retrofit, kita persiapkan dahulu request dan response untuk API login. Request untuk login hanya terdiri dari 2 field, username dan password. Buat file Kotlin File/Class dengan tipe Class dibawah package requests dengan nama LoginRequest. Tambahkan data pada class LoginRequest seperti berikut.

Berikut ini merupakan contoh response JSON jika sukses login.

Untuk dapat membuat data class dari json dengan mudah, install plugin JSON to kotlin pada android studio dan letakkan dibawah package responses dengan nama LoginResponse.

Buatlah Kotlin File/Class dengan tipe Interface dibawah package data dengan nama ApiService. File ini berisi daftar endpoint, method dan parameter yang ada pada API.

Buatlah Kotlin File/Class dengan tipe Class dibawah package data dengan nama RequestInterceptor. File ini digunakan untuk intersepsi pada saat request ke API dan melakukan pengecekan shared preferences dengan nama key access_token (SessionManager), jika access_token tidak kosong akan ditambahkan Header pada request yang berisi Authorization: Bearer <access_token> sehingga pada ApiService tidak perlu lagi menambahkan parameter header access_token / apikey untuk request ke protected resources.

Buatlah Kotlin File/Class dengan tipe Class dibawah package data dengan nama ApiClient. File berisi instance retrofit dan okHttpClient untuk melakukan http request ke API.

Activity dan UI (View)

Pindahkan / refactor MainActivity yang berada dibawah package utama ke package UI, tambahkan juga activity baru (new empty activity) dengan nama LoginActivity. Alur / proses yang akan dibuat nantinya seperti ini.

App Start -> Cek Akses Token (MainActivity) -> Go To Login (LoginActivity) jika tidak ditemukan Akses Token atau Menampilkan Akses token dan Tombol Logout (MainActivity) jika Akses Token ditemukan (SessionManager)

Berikut ini merupakan design UI LoginActivity dan MainActivity

Berikut ini merupakan source code LoginActivity dan MainActivity

Android Manifest dan Permissions

Finally untuk dapat melakukan http request API, maka diperlukan android permission Internet. Konfigurasi MainActivity sebagai LAUNCHER (Activity yang pertama diload ketika aplikasi start) dengan menggunakan intent filter.

TL;DR

Source code dan drawable assets lengkap dapat diunduh dari repo github

Install Apache Hive di Cluster Hadoop CentOS 7

2020-02-02T08:06:00.002+07:00

Apache Hive merupakan project data warehouse dan analytics yang dibangun di atas platform Apache Hadoop. Tools ini awalnya dikembangkan oleh developer Facebook yang menilai cara akses/query data yang disimpan di platform Hadoop terlalu susah karena masih harus menggunakan konsep Map and Reduce yang implementasinya menggunakan programming Java. Untuk itu sebagai solusinya mereka menciptakan sebuah interface yang memungkinkan untuk melakukan retrieval dan manipulasi data menggunakan bahasa yang serupa dengan syntax SQL.

Pada tutorial sebelumnya kita sudah melakukan install apache hadoop multi cluster pada server CentOS 7, tutorial kali ini membahas cara menghubungkan apache hive dengan hadoop cluster yang sudah kita buat.

Download Hive Source

$ wget https://www-us.apache.org/dist/hive/hive-3.1.2/apache-hive-3.1.2-bin.tar.gz
$ tar -zxvf apache-hive-3.1.2-bin.tar.gz
$ sudo mv apache-hive-3.1.2-bin /usr/local/hive

Setup Environment Variable

$ su - hadoop
$ vi ~/.bashrc
# Sesuaikan dengan teks di bawah ini
# Java
export JAVA_HOME=$(dirname $(dirname $(readlink $(readlink $(which javac)))))

# Hadoop
export HADOOP_HOME=/usr/local/hadoop
export HADOOP_INSTALL=$HADOOP_HOME
export HADOOP_MAPRED_HOME=$HADOOP_HOME
export HADOOP_COMMON_HOME=$HADOOP_HOME
export HADOOP_HDFS_HOME=$HADOOP_HOME
export HADOOP_COMMON_LIB_NATIVE_DIR=$HADOOP_HOME/lib/native
export HADOOP_OPTS="-Djava.library.path=$HADOOP_COMMON_LIB_NATIVE_DIR"
export HADOOP_CLASSPATH=${JAVA_HOME}/lib/tools.jar

# Yarn
export YARN_HOME=$HADOOP_HOME

# Hive
HIVE_HOME=/usr/local/hive
HIVE_CONF_DIR=/usr/local/hive/conf

# Classpath
export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar:$HADOOP_HOME/lib/*:$HIVE_HOME/lib/*

# Path
export PATH=$PATH:$HADOOP_HOME/sbin:$HADOOP_HOME/bin:$JAVA_HOME/bin:$HIVE_HOME/bin

Konfigurasi File hive-env.sh

$ cd $HIVE_CONF_DIR
$ sudo cp hive-env.sh.template hive-env.sh
$ sudo chmod +x hive-env.sh
$ sudo vi hive-env.sh
# tambahkan pada akhir baris
HIVE_HOME=/usr/local/hive
HIVE_CONF_DIR=/usr/local/hive/conf

Install MySQL dan JDBC MySQL Connector (Hive Metastore)

$ sudo yum install mariadb-server
$ sudo systemctl enable mariadb
$ sudo systemctl start mariadb
$ sudo mysql_secure_installation
$ wget http://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-5.1.30.tar.gz
$ tar -zxvf mysql-connector-java-5.1.30.tar.gz
$ sudo cp mysql-connector-java-5.1.30/mysql-connector-java-5.1.30-bin.jar $HIVE_HOME/lib/
$ sudo chmod +x $HIVE_HOME/lib/mysql-connector-java-5.1.30-bin.jar

Buat database MySQL dengan nama metastore untuk Hive (initSchema)

$ mysql -u root -p

CREATE DATABASE metastore;
USE metastore;
SOURCE /usr/local/hive/scripts/metastore/upgrade/mysql/hive-schema-3.1.0.mysql.sql;
CREATE USER 'hive'@localhost IDENTIFIED BY '';
GRANT ALL ON *.* TO 'hive'@localhost;
FLUSH PRIVILEGES;

Konfigurasi File hive-site.xml

$ cp $HIVE_CONF_DIR/hive-default.xml.template $HIVE_CONF_DIR/hive-site.xml
$ vi $HIVE_CONF_DIR/hive-site.xml
# hive-site.xml
<property>
    <name>hive.exec.local.scratchdir</name>
    <value>/tmp/hive_temp</value>
    <description>Local scratch space for Hive jobs</description>
  </property>
  <property>
    <name>hive.execution.engine</name>
    <value>mr</value>
    <description>
      Expects one of [mr, tez, spark].
      Chooses execution engine. Options are: mr (Map reduce, default)</description>
  </property>
  <property>
    <name>javax.jdo.option.ConnectionURL</name>
    <value>jdbc:mysql://localhost/metastore?createDatabaseIfNotExist=true&useSSL=false</value>
    <description>metadata is stored in a MySQL server</description>
  </property>
  <property>
    <name>javax.jdo.option.ConnectionDriverName</name>
    <value>com.mysql.jdbc.Driver</value>
    <description>Driver class name for a JDBC metastore</description>
  </property>
  <property>
    <name>javax.jdo.option.ConnectionUserName</name>
    <value>hive</value>
    <description>Username to use against metastore database</description>
  </property>
  <property>
    <name>javax.jdo.option.ConnectionPassword</name>
    <value>***</value>
    <description>password to use against metastore database</description>
  </property>
  <property>
    <name>hive.exec.scratchdir</name>
    <value>/tmp/hive_tmp</value>
    <description>HDFS root scratch dir for Hive jobs which gets created with write all (733) permission</description>
  </property>

Install HBase

$ cd ~/
$ wget http://apache.mirror.gtcomm.net/hbase/stable/hbase-2.2.3-bin.tar.gz
$ tar -zxvf hbase-2.2.3-bin.tar.gz
$ sudo mv hbase-2.2.3-bin /usr/local/hbase
$ sudo chown -R hadoop:hadoop /usr/local/hbase
$ sudo chmod -R g+rwx /usr/local/hbase
$ vi ~/.bashrc
# tambahkan
export HBASE_HOME=/usr/local/hbase
export PATH=$PATH:$HADOOP_HOME/sbin:$HADOOP_HOME/bin:$JAVA_HOME/bin:$HIVE_HOME/bin:$HBASE_HOME/bin
$ source ~/.bashrc
$ cd $HBASE_HOME/conf
$ vi hbase-env.sh
# atur JAVA_HOME
export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64/
$ vi hbase-site.xml
# tambahkan
<configuration>
   <property>
      <name>hbase.rootdir</name>
      <value>hdfs://localhost:8030/hbase</value>
   </property>
	
   <property>
      <name>hbase.zookeeper.property.dataDir</name>
      <value>/hadoop/zookeeper</value>
   </property>
   
   <property>
     <name>hbase.cluster.distributed</name>
     <value>true</value>
   </property>
</configuration>
$ sudo mkdir -p /hadoop/zookeeper
$ sudo chown -R hadoop:hadoop /hadoop/
$ start-hbase.sh

Buat direktori database hive di HDFS

$ hdfs dfs -mkdir /user/
$ hdfs dfs -mkdir /user/hive
$ hdfs dfs -mkdir /user/hive/warehouse
$ hdfs dfs -mkdir /tmp
$ hdfs dfs -chmod -R a+rwx /user/hive/warehouse
$ hdfs dfs -chmod g+w /tmp

Test Hive Console

$ hive
hive> show tables;

HiveQL on Hive Console

Running Metastore dan Hive as Daemon (Background)

$ mkdir $HIVE_HOME/logs
$ hive --service metastore --hiveconf hive.log.dir=$HIVE_HOME/logs --hiveconf hive.log.file=metastore.log >/dev/null 2>&1 &
$ hive --service hiveserver2 --hiveconf hive.log.dir=$HIVE_HOME/logs --hiveconf hive.log.file=hs2.log >/dev/null 2>&1 &

Testing Hive Web UI

$ hiveserver2
Akses ke browser http://hadoop02:10002

HiveServer2 Web UI

Install Hadoop Multi Cluster CentOS 7

2020-02-01T10:19:00.001+07:00

Apache Hadoop adalah kumpulan utilitas perangkat lunak open-source yang memfasilitasi penggunaan jaringan multi komputer untuk memecahkan masalah yang melibatkan data dan komputasi dalam jumlah besar. Hadoop merupakan framework perangkat lunak untuk penyimpanan terdistribusi dan pemrosesan data besar menggunakan model pemrograman MapReduce. Awalnya dirancang untuk klaster komputer yang dibangun dari perangkat keras komoditas dan juga digunakan pada kluster perangkat keras kelas atas. Semua modul di Hadoop dirancang dengan asumsi mendasar bahwa kegagalan perangkat keras adalah kejadian umum dan harus ditangani secara otomatis oleh framework.

Persiapan

4 Server running OS Centos 7 (1 NameNode, 3 Data Node)
Java 8
Hadoop Version 3.2.1

Arsitektur

hadoop02 - 192.168.7.35 - NameNode
hadoop03 - 192.168.7.36 - DataNode
hadoop04 - 192.168.7.37 - DataNode
hadoop05 - 192.168.7.38 - DataNode

**Setup Server (All Server)**

Konfigurasi Hostname dan Host masing-masing server

$ sudo hostnamectl set-hostname hadoop02 # sesuaikan dengan arsitektur
$ sudo vi /etc/hosts
# tambahkan pada akhir baris
192.168.7.35 hadoop02
192.168.7.36 hadoop03
192.168.7.37 hadoop04
192.168.7.38 hadoop05

Disable firewall dan SELinux

$ sudo systemctl stop firewalld
$ sudo systemctl disable firewalld
$ sudo vi /etc/selinux/config
# ubah SELINUX menjadi
SELINUX=disabled
$ sudo reboot now

Buat user hadoop

$ sudo useradd hadoop
$ sudo usermod -aG wheel hadoop
$ sudo passwd hadoop # set password hadoop

Konfigurasi Paswordless SSH

$ sudo su - hadoop
$ ssh-keygen -t rsa # kosongkan passphrase / enter sampai selesai
$ ssh-copy-id hadoop@hadoop02
$ ssh-copy-id hadoop@hadoop03
$ ssh-copy-id hadoop@hadoop04
$ ssh-copy-id hadoop@hadoop05

Install Java 8

$ sudo yum update
$ sudo yum install -y epel-release java-1.8.0-openjdk

Konfigurasi environment variables ~/.bashrc

$ vi ~/.bashrc
# tambahkan pada akhir baris
export JAVA_HOME=$(dirname $(dirname $(readlink $(readlink $(which javac)))))
export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
export HADOOP_HOME=/usr/local/hadoop
export HADOOP_INSTALL=$HADOOP_HOME
export HADOOP_MAPRED_HOME=$HADOOP_HOME
export HADOOP_COMMON_HOME=$HADOOP_HOME
export HADOOP_HDFS_HOME=$HADOOP_HOME
export HADOOP_COMMON_LIB_NATIVE_DIR=$HADOOP_HOME/lib/native
export HADOOP_OPTS="-Djava.library.path=$HADOOP_COMMON_LIB_NATIVE_DIR"
export HADOOP_CLASSPATH=${JAVA_HOME}/lib/tools.jar
export YARN_HOME=$HADOOP_HOME
export PATH=$PATH:$HADOOP_HOME/sbin:$HADOOP_HOME/bin:$JAVA_HOME/bin
$ source ~/.bashrc

Setup NameNode (Master) - 192.168.7.35

Download hadoop-3.2.1

$ cd ~/
$ wget https://www-us.apache.org/dist/hadoop/common/hadoop-3.2.1/hadoop-3.2.1.tar.gz
$ tar -zxvf hadoop-3.2.1.tar.gz
$ sudo mv hadoop-3.2.1 /usr/local/hadoop
$ sudo chown -R hadoop:hadoop /usr/local/hadoop
$ sudo chmod -R g+rwx /usr/local/hadoop

Konfigurasi Hadoop Core Site core-site.xml

$ cd $HADOOP_HOME/etc/hadoop
$ vi core-site.xml # core-site.xml
# tambahkan di dalam tag <configuration>
...
<configuration>
   <property>
      <name>fs.default.name</name>
      <value>hdfs://hadoop02:9000</value>
   </property>
 
   <property>
      <name>dfs.permissions</name>
       <value>false</value>
   </property>
</configuration>
...

Konfigurasi HDFS hdfs-site.xml

$ cd $HADOOP_HOME/etc/hadoop
$ vi hdfs-site.xml # hdfs-site.xml
# tambahkan di dalam tag <configuration>...
<configuration>
   <!-- Setting path direktori namenode -->
   <property>
      <name>dfs.name.dir</name>
      <value>/usr/local/hadoop/data/nameNode</value>
   </property>

   <!-- Setting path direktori datanode -->
   <property>
      <name>dfs.data.dir</name>
      <value>/usr/local/hadoop/data/nameNode</value>
   </property>
 
   <!-- Jumlah replikasi -->
   <property>
      <name>dfs.replication</name>
      <value>3</value>
   </property>
</configuration>
...

Konfigurasi Worker (slave / data node) workers

$ cd $HADOOP_HOME/etc/hadoop
$ vi workers
#isi dengan list hostname slave / data node
hadoop03
hadoop04
hadoop05

Copy hadoop direktori ke semua server data node

$ sudo scp -R /usr/local/hadoop hadoop03:/usr/local/hadoop
$ sudo scp -R /usr/local/hadoop hadoop04:/usr/local/hadoop
$ sudo scp -R /usr/local/hadoop hadoop05:/usr/local/hadoop

Format HDFS filesystem

$ hdfs namenode -format

Setup DataNode (Slave) - 192.168.7.[36-38]

Atur owner / permission direktori hadoop

$ sudo chown -R hadoop:hadoop /usr/local/hadoop
$ sudo chmod -R g+rwx /usr/local/hadoop

Konfigurasi Hadoop Yarn Site yarn-site.xml

...
<configuration>
   <!-- Site specific YARN configuration properties -->
   <property>
      <name>yarn.resourcemanager.hostname</name>
      <value>hadoop02</value>
   </property>
</configuration>
...

Start DFS (on NameNode server)

$ start-dfs.sh

Start Yarn (on NameNode server)

$ start-yarn.sh

Check JVM Process

$ jps

Check / List Yarn Node

$ yarn node -list

Running Hadoop Web Monitoring

http://hadoop02:9870

Hadoop Web Health Check

Hadoop Data Node Usage

Default Authentification Laravel 5.4

2017-05-11T22:13:00.001+07:00

Umumnya pada setiap pekerjaan atau proyek aplikasi web akan membutuhkan authentifikasi pengguna / sistem login sebelum dapat mengakses fitur aplikasi selain untuk alasan keamanan juga. Tutorial kali ini saya akan membahas bagaimana cara mengaktifkan modul authentifikasi default laravel, cukup dengan beberapa perintah, laravel sudah menyediakan mulai dari login akun pengguna, pendaftaran akun pengguna, sampai dengan fitur untuk mereset password jika lupa dan mengirim email untuk mendapatkan token untuk reset password. Kita akan melanjutkan project social yang sebelumnya sudah kita buat, untuk cara instalasi dan membuat project laravel bisa lihat di postingan saya sebelumnya hello laravel.

Konfigurasi Database

Langkah pertama adalah membuat database baru, laravel mendukung beberapa database diantaranya SQLite, MySQL, PostgreSQL dan SQL Server. Untuk tutorial ini saya menggunakan database MySQL. Buat database baru di PhpMyAdmin atau console, nama database terserah, saya membuatnya dengan nama social_db.

Membuat Database Baru di MySQL

Setelah database dibuat, langkah selanjutnya adalah konfigurasi database di laravel. Buka project social di IDE kesayangan anda. Buka file .env di root project, sesuaikan konfigurasi database anda.

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=social_db
DB_USERNAME=adit
DB_PASSWORD=adit

Untuk dapat melihat konfigurasi database secara lengkap ada di file config/database.php

Migration

Secara default, laravel menyediakan 2 file schema database dapat di lihat di direktori/folder database/migrations, schema database gampangnya adalah blueprint dari pembuatan table pada database. Migration pada laravel adalah proses mengubah / migrasi dari schema menjadi tabel-tabel database. Kita akan migrasikan 2 schema : create_users_table dan create_password_resets_table.

Buka terminal / command prompt dan ubah ke direktori atau folder root project social
Jalankan perintah : php artisan migrate

Migrasi Schema ke Database

Lihat hasil migrate, pastikan semua migrasi berjalan sukses, jika sukses periksa database social_db, tabel-tabel dari proses migrasi berhasil dibuat.

Table berhasil di buat

Jika muncul error "Specified key was too long; max key length is 767 bytes", berarti versi MySQL anda di bawah 5.7, laravel versi 5.4 mengubah default collationnya menjadi utf8mb4, karena di versi ini support untuk emoji which is membutuhkan karakter string lebih banyak. Cara mengatasinya, buka file AppServiceProvider.php yang terletak pada direktori app/Providers, kemudian modifikasi seperti berikut :
```
<?php
...
use Illuminate\Support\Facades\Schema;
...
public function boot(){
    Schema::defaultStringLength(191);
}
```

Generate Auth Scaffolding

Setelah tabel-tabel database selesai dibuat, kita akan mengenerate auth scaffolding bawaan laravel, laravel akan mengenerate Controller, Route, Model, dan View secara otomatis.

Buka terminal / command prompt dan ubah ke direktori atau folder root project social
Jalankan perintah : php artisan make:auth

Generate Auth Scaffolding

Jika berhasil, aplikasi bisa langsung di test.

Testing

Buka terminal / command prompt dan ubah ke direktori atau folder root project social
Jalankan perintah : php artisan serve untuk menjalankan server lokal pada port 8000
Buka browser ketikkan alamat http://localhost:8000 atau http://127.0.0.1:8000.

Screenshots

Landing Page

Homepage setelah login

Download source code

Source code artikel ini dapat di download di github.

Hello Laravel!

2017-05-09T19:05:00.000+07:00

Halo sobat blogger, semoga kalian semua masih diberikan kesehatan oleh Allah SWT, amiin. Pada kesempatan kali ini saya akan membahas PHP framework yang cukup terkenal, Laravel. Ya, Laravel yang katanya Framework For Web Artisan (Framework untuk para seniman web). Laravel ini dibuat oleh Taylor Otwell yg basicnya dia itu programmer .net. Yang menurut saya cukup menarik dari framework ini adalah sintaksnya yg simple, human readable, ekspresif banget. Selain itu Laravel juga menyediakan fitur-fitur yg sering digunakan dalam web project seperti migration (seperti version control pada database), autentifikasi, form validation, semuanya disediakan Laravel out of the box. Jika ingin membuat Oauth2 server Laravel sudah menyediakan package Passport, membuat multiple social network login (Facebook, Twitter, G+, etc)? gampang banget, Laravel punya package yang namanya Socialite.

Kebutuhan Server (Requirements)

Untuk dapat menjalankan Laravel, dapat menggunakan Homestead, Valet (Khusus pengguna Mac) atau dapat menjalankan dengan spesifikasi berikut:

PHP minimum versi 5.6.4 atau lebih tinggi
Ekstensi PHP :

OpenSSL
PDO
Mbstring
Tokenizer
XML

Composer (Dependency manager for PHP)

Instalasi Laravel

Pastikan composer telah terinstall baik pada komputer anda, ada 2 cara untuk instalasi Laravel :

Via Laravel Installer

Buka terminal / command prompt dan ubah ke direktori yang diinginkan untuk menyimpan project.

Ketikkan perintah :

composer global require "laravel/installer"

Untuk membuat project baru cukup ketikkan : laravel new <nama_project>
```
laravel new social
```
Tunggu sampai download project selesai

Via Composer Create-Project

Buka terminal / command prompt dan ubah ke direktori yang diinginkan untuk menyimpan project.
Ketikkan perintah : composer create-project --prefer-dist laravel/laravel <nama_project>
```
composer create-project --prefer-dist laravel/laravel social
```
Tunggu sampai download project selesai

Via Github

Download .zip source code laravel
Ekstrak folder master.zip.
Buka terminal / command prompt dan ubah ke direktori folder hasil ekstrak.
Ketikkan perintah :
```
composer update
```
Tunggu sampai proses update selesai.

Instalasi Laravel Sukses

Testing Local Server

Buka terminal / command prompt, masuk ke root direktori project
Ketikkan perintah :
```
php artisan serve
```
Setelah running, akses ke browser http://localhost:8000 atau http://127.0.0.1:8000.

Running Laravel Local Server

"Good programmer write code for machine, great programmer write code for other programmer"

Tutorial OAuth2 dengan CodeIgniter

2016-10-19T15:10:00.001+07:00

Pada kesempatan kali ini, saya akan membahas cara menggunakan OAuth (Open standard for Authentification) versi 2 pada framework CodeIgniter. Sebelumnya apa itu OAuth2? OAuth2 merupakan pengembangan dari OAuth versi pertama, yaitu sebuah protokol atau framework untuk mengamankan resource (biasanya webservice) dengan mengotorisasi penggunanya sebelum dapat menggunakan resource tersebut.

Persiapan :

CodeIgniter 3.1.0.zip. (versi CodeIgniter saat dibuatnya artikel ini)
Kita akan menggunakan library OAuth2 Server CodeIgniter yang telah disediakan oleh bshaffer.
Dump table mysql oauth2.sql dan country.sql
Kita akan menggunakan library CodeIgniter Rest Client milik Phil Sturgeon untuk membuat API

Langkah-Langkah :

Ekstrak CodeIgniter 3.1.0.zip, letakkan di document root web server anda, rename foldernya menjadi ci-oauth2

Ekstrak library OAuth2 Server CodeIgniter dan rename nama foldernya menjadi oauth2, letakkan folder tersebut pada direktori library CodeIgniter (application/libraries/)

Kita akan melakukan instalasi oauth2-server-php dengan composer, buka terminal / console, ubah directory ke application/libararies/oauth2, ketikkan :

composer install

Install OAuth2 Server PHP via Composer

Bagi yang kesulitan menginstall via composer, saya memberikan link lengkap source code di bagian akhir artikel ini.

Buat library CodeIgniter dengan nama Server.php (application/libraries/Server.php), ketikkan listing perintah berikut:

<?php
/**
* @package     Server.php
* @author      Aditya Nursyahbani
* @link        http://www.aditya-nursyahbani.net/2016/10/tutorial-oauth2-dengan-codeigniter.html
* @copyright   Copyright(c) 2016
* @version     1.0.0
**/
date_default_timezone_set('Asia/Jakarta');

class Server{
 function __construct($config=array()){
  require_once(__DIR__.'/../config/database.php');       
  require_once(__DIR__.'/../libraries/oauth2/src/OAuth2/Autoloader.php'); 
  $config = $db['oauth'];
  
  OAuth2Autoloader::register();
  $this->storage = new OAuth2StoragePdo(array('dsn' => $config["dsn"], 'username' => $config["username"], 'password' => $config["password"]));
  $this->server = new OAuth2Server($this->storage, array('allow_implicit' => true));
  $this->request = OAuth2Request::createFromGlobals();
  $this->response = new OAuth2Response();
 }

 /**
 * client_credentials
 */
 public function client_credentials(){
  $this->server->addGrantType(new OAuth2GrantTypeClientCredentials($this->storage, array(
      "allow_credentials_in_request_body" => true
  )));
  $this->server->handleTokenRequest($this->request)->send();
 }

 /**
 * password_credentials
 */
 public function password_credentials(){
  $users = array("adit" => array("password" => 'pass', 'first_name' => 'homeway', 'last_name' => 'yao'));
  $storage = new OAuth2StorageMemory(array('user_credentials' => $users));
  $this->server->addGrantType(new OAuth2GrantTypeUserCredentials($storage));
  $this->server->handleTokenRequest($this->request)->send();
 }

 /**
 * refresh_token
 */
 public function refresh_token(){
  $this->server->addGrantType(new OAuth2GrantTypeRefreshToken($this->storage, array(
   "always_issue_new_refresh_token" => true,
   "unset_refresh_token_after_use" => true,
   "refresh_token_lifetime" => 2419200,
  )));
  $this->server->handleTokenRequest($this->request)->send();
 }

 /**
 * limit scope
 */
 public function require_scope($scope=""){
  if (!$this->server->verifyResourceRequest($this->request, $this->response, $scope)) {
      $this->server->getResponse()->send();
      die;
  }
 }

 public function check_client_id(){
  if (!$this->server->validateAuthorizeRequest($this->request, $this->response)) {
      $this->response->send();
      die;
  }
 }

 public function authorize($is_authorized){
  $this->server->addGrantType(new OAuth2GrantTypeAuthorizationCode($this->storage));
  $this->server->handleAuthorizeRequest($this->request, $this->response, $is_authorized);
  if ($is_authorized) {
     $code = substr($this->response->getHttpHeader('Location'), strpos($this->response->getHttpHeader('Location'), 'code=')+5, 40);
     header("Location: ".$this->response->getHttpHeader('Location'));
    }
  $this->response->send();
 }

 public function authorization_code(){
  $this->server->addGrantType(new OAuth2GrantTypeAuthorizationCode($this->storage));
  $this->server->handleTokenRequest($this->request)->send();
 }
}
 /**
 * password_credentials
 */
 public function password_credentials(){
  $users = array("user" => array("password" => 'pass', 'first_name' => 'aditya', 'last_name' => 'nursyahbani'));
  $storage = new OAuth2\Storage\Memory(array('user_credentials' => $users));
  $this->server->addGrantType(new OAuth2\GrantType\UserCredentials($storage));
  $this->server->handleTokenRequest($this->request)->send();
 }

 /**
 * refresh_token
 */
 public function refresh_token(){
  $this->server->addGrantType(new OAuth2\GrantType\RefreshToken($this->storage, array(
   "always_issue_new_refresh_token" => true,
   "unset_refresh_token_after_use" => true,
   "refresh_token_lifetime" => 2419200,
  )));
  $this->server->handleTokenRequest($this->request)->send();
 }

 /**
 * limit scope
 */
 public function require_scope($scope=""){
  if (!$this->server->verifyResourceRequest($this->request, $this->response, $scope)) {
      $this->server->getResponse()->send();
      die;
  }
 }

 public function check_client_id(){
  if (!$this->server->validateAuthorizeRequest($this->request, $this->response)) {
      $this->response->send();
      die;
  }
 }

 public function authorize($is_authorized){
  $this->server->addGrantType(new OAuth2\GrantType\AuthorizationCode($this->storage));
  $this->server->handleAuthorizeRequest($this->request, $this->response, $is_authorized);
  if ($is_authorized) {
     $code = substr($this->response->getHttpHeader('Location'), strpos($this->response->getHttpHeader('Location'), 'code=')+5, 40);
     header("Location: ".$this->response->getHttpHeader('Location'));
    }
  $this->response->send();
 }

 public function authorization_code(){
  $this->server->addGrantType(new OAuth2\GrantType\AuthorizationCode($this->storage));
  $this->server->handleTokenRequest($this->request)->send();
 }
}

Ekstrak file Codeigniter Rest Client sesuai dengan direktorinya masing pada folder ci-oauth2

Pada artikel ini menggunakan database mysql, buat tabel database dengan nama oauth2, buka phpmyadmin/consol dan import file oauth2.sql dan country.sql ke tabel oauth2.

Konfigurasi koneksi database dengan codeigniter, buka file database.php yang terletak pada direktori application/config. Tambahkan baris berikut:

$db['oauth'] = array(
 'dsn' => 'mysql:dbname=oauth2;host=127.0.0.1',
 'hostname' => 'localhost',
 'username' => 'USERNAME_DB_HERE',
 'password' => 'PASSWORD_DB_HERE',
 'database' => 'oauth2',
 'dbdriver' => 'pdo',
 'dbprefix' => '',
 'pconnect' => FALSE,
 'db_debug' => (ENVIRONMENT !== 'production'),
 'cache_on' => FALSE,
 'cachedir' => '',
 'char_set' => 'utf8',
 'dbcollat' => 'utf8_general_ci',
 'swap_pre' => '',
 'encrypt' => FALSE,
 'compress' => FALSE,
 'stricton' => FALSE,
 'failover' => array(),
 'save_queries' => TRUE
);

Buat direktori dengan nama Oauth2 pada direktori application/controllers, buat controller-controller berikut:
Authorize.php

<?php
/**
* @package     Authorize.php
* @author      Aditya Nursyahbani
* @link        http://www.aditya-nursyahbani.net/2016/10/tutorial-oauth2-dengan-codeigniter.html
* @copyright   Copyright(c) 2016
* @version     1.0.0
**/

defined('BASEPATH') OR exit('No direct script access allowed');

class Authorize extends CI_Controller {
    function __construct(){
        @session_start();
        parent::__construct();
        $this->load->library("Server", "server");
    }

    function index(){
        $scope = $this->input->get("scope");
        $state = $this->input->get("state");
        $client_id = $this->input->get("client_id");
        $redirect_uri = $this->input->get("redirect_uri");
        $response_type = $this->input->get("response_type");

        if(!isset($_POST["authorized"])){
            $this->server->check_client_id();
            $data = array(
                "scope" => $scope,
                "state" => $state,
                "client_id" => $client_id,
                "redirect_uri" => $redirect_uri,
                "response_type" => $response_type,
            );
            $this->load->view("oauth2/authorize", $data);
        }else{
            $authorized = $this->input->post("authorized");
            if($authorized === "yes"){
                $this->server->authorize(($authorized === "yes"));
            }else{
                echo "error";
            }
        }
    }

    function token(){
        $this->server->authorization_code("yes");
    }
}

ClientCredentials.php

<?php
/**
* @package     ClientCredentials.php
* @author      Aditya Nursyahbani
* @link        http://www.aditya-nursyahbani.net/2016/10/tutorial-oauth2-dengan-codeigniter.html
* @copyright   Copyright(c) 2016
* @version     1.0.0
**/

defined('BASEPATH') OR exit('No direct script access allowed');

class ClientCredentials extends CI_Controller {
    function __construct(){
        @session_start();
        parent::__construct();
        $this->load->library("Server", "server");
    }    

    function index(){
        $this->server->client_credentials();
    }
}

PasswordCredentials.php

<?php
/**
* @package     PasswordCredentials.php
* @author      Aditya Nursyahbani
* @link        http://www.aditya-nursyahbani.net/2016/10/tutorial-oauth2-dengan-codeigniter.html
* @copyright   Copyright(c) 2016
* @version     1.0.0
**/
defined('BASEPATH') OR exit('No direct script access allowed');

class PasswordCredentials extends CI_Controller {
    function __construct(){
        @session_start();
        parent::__construct();
        $this->load->library("Server", "server");
    }    

    function index(){
        $this->server->password_credentials();
    }
}

RefreshToken.php

<?php
/**
* @package     RefreshToken.php
* @author      Aditya Nursyahbani
* @link        http://www.aditya-nursyahbani.net/2016/10/tutorial-oauth2-dengan-codeigniter.html
* @copyright   Copyright(c) 2016
* @version     1.0.0
**/
defined('BASEPATH') OR exit('No direct script access allowed');

class RefreshToken extends CI_Controller {
    function __construct(){
        @session_start();
        parent::__construct();
        $this->load->library("Server", "server");
    }    

    function index(){
        $this->server->refresh_token();
    }
}

Test.php

<?php
/**
* @package     Test.php
* @author      Aditya Nursyahbani
* @link        http://www.aditya-nursyahbani.net/2016/10/tutorial-oauth2-dengan-codeigniter.html
* @copyright   Copyright(c) 2016
* @version     1.0.0
**/

defined('BASEPATH') OR exit('No direct script access allowed');

class Test extends CI_Controller {
    function __construct(){
        @session_start();
        parent::__construct();
    }

    function index(){
     $this->load->view("oauth2/api");
    }

}

Buatlah direktori dengan nama oauth2 pada direktori application/views kemudian buatlah view berikut didalam direktori oauth2 :
api.php

<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8">
    <title>CodeIgniter OAuth2 Tutorial</title>
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
    <meta name="description" content="CodeIgniter OAuth2 Tutorial">
    <meta property="og:type" content="website">
    <meta property="og:title" content="CodeIgniter OAuth2 Tutorial">
    <meta property="og:url" content="http://homeway.me">
    <meta property="og:site_name" content="CodeIgniter OAuth2 Tutorial">
    <meta property="og:description" content="CodeIgniter OAuth2 Tutorial">
    <meta name="twitter:title" content="@adit_gudhel">
    <link rel="publisher" href="aditya nursyahbani">
    <link href="http://cdn.bootcss.com/bootstrap/3.3.4/css/bootstrap.min.css" rel="stylesheet">
</head>
<body>

<div class="row">
    <div class="col-md-2"></div>
    <div class="col-md-8">
        <br><br>
        <form class="form-inline">
            <h1>1. Request Access Token (Grant Type)</h1><br><br>

            <div class="form-group">
                <label for="Credentials"><h3>Resource Owner Password Credentials:</h3><br>
                    <div>Param：<code>{ grant_type: "password", username: "adit", password: "pass", client_id: 'client', client_secret:'mysecret', scope:'country' }</code></div><br>
                    <div>Result:<code id="return-PasswordCredentials"></code></div><br>
                </label><br>
                <a id="btn-PasswordCredentials" class="btn btn-success">Get PasswordCredentials</a><br>
            </div>
            <br><br>

            <div class="form-group">
                <label for="ClientCredentials"><h3>Client Credentials: </h3><br>
                    <div>Param:<code>{client_id: 'client', client_secret:'mysecret', grant_type:'client_credentials', scope:'country'}</code></div><br>
                    <div>Result:<code id="return-ClientCredentials"></code></div><br>
                </label><br>
                <a id="btn-ClientCredentials" class="btn btn-success">Get ClientCredentials</a>
            </div>
            <br><br>

            <div class="form-group">
                <label for="authorize">
                    <h3>Access_token（Authorization Code）:</h3>
                    <div>Param：<code>{code: "Authorize code", client_id: 'client', client_secret:'mysecret', password:'pass', grant_type: 'authorization_code', scope:'country'}</code></div><br>
                    <div>Result：<code id="return-Authorize"></code></div><br>
                    <div>Link Auth <a target="_blank" href="/ci-oauth2/oauth2/authorize?response_type=code&client_id=client&redirect_uri=http://www.aditya-nursyahbani.net&state=xyz&scope=country">/ci-oauth2/oauth2/authorize?response_type=code&client_id=client&redirect_uri=<?=base_url('oauth2/test');?>&state=xxx&scope=country</a></div><br>
                </label><br>
                <input type="text" class="form-control" id="authorize-code" placeholder="Authorize code">
                <a id="btn-authorize" class="btn btn-success">Get Authorize Access Token</a>
            </div>

            <br><br>
            <div class="form-group">
                <label for="authorize">
                    <h3>Implicit Grant:</h3><br>
                    <div>Authorization Code Access Token</div><br>
                </label>
            </div>

            <br><br><br>
            <h1>2. Access Token </h1>
            <br><br><br>

            <div class="form-group">
                <label for="refresh-token">
                    <h3>Refresh Access Token</h3><br>
                    <div>Param：<code>{refresh_token: "Refresh Token", client_id: 'client', client_secret:'mysecret', grant_type:'refresh_token', scope:'country'}</code></div>
                    <div>Result: <code id="return-refresh-token"></code></div><br>
                </label><br>
                <input type="text" class="form-control refresh-token" id="old_token" placeholder="Refresh Token">
                <a id="btn-refresh" class="btn btn-success">From Refresh Token Get Access Token</a>
            </div>
            <br><br><br><br>

            <div class="form-group">
                <label for="resource">
                    <h3>From Access Token get Resource</h3><br>
                    <div>Param：<code>{ access_token: "Access Token"}</code></div><br>
                    <div>Result: <code id="return-resource"></code></div><br>
                </label><br>
                <input type="text" class="form-control token" id="resource" placeholder="Resource">
                <a id="btn-resource" class="btn btn-success">Get Resource</a>
                <a id="btn-resource-limit" class="btn btn-success">Get Resource With Scope Error</a>
            </div>
            <br><br>
        </form>
    </div>
</div>

<script src="http://cdn.bootcss.com/jquery/1.11.2/jquery.min.js"></script>
<script>
$(document).ready(function(){
    $("#btn-refresh").click(function (e){
        var data = {refresh_token: $("#old_token").val(), client_id: 'client', client_secret:'mysecret', grant_type:'refresh_token', scope:'country'};
        
        $.post('/ci-oauth2/oauth2/RefreshToken', data, function (d){
            console.log("Get Token => ", d);
            $('#return-refresh-token').html(JSON.stringify(d));
        });
    }); 

    $('#btn-authorize').click(function (e){
        var data = {code: $("#authorize-code").val(), client_id: 'client', client_secret:'mysecret', redirect_uri:"http://www.aditya-nursyahbani.net", grant_type: 'authorization_code', scope:'country'};
        $.post('/ci-oauth2/oauth2/authorize/token', data, function (d){
            $(".refresh-token").val(d.refresh_token);
            console.log("Get Authorize Access Token => ", d);
            $('#return-Authorize').html(JSON.stringify(d));
        },"json");
    });

    $('#btn-resource').click(function (e){
        var data = { access_token: $("#resource").val()};
        
        $.post('/ci-oauth2/api/countries', data, function (d){
            console.log("Get Authorize => ", d);
            $('#return-resource').html(JSON.stringify(d));
        },"json");      
    });

    $('#btn-resource-limit').click(function (e){
        var data = { access_token: $("#resource").val()};
        
        $.post('/ci-oauth2/oauth2/resource/limit', data, function (d){
            console.log("Get Authorize => ", d);
            $('#return-resource').html(JSON.stringify(d));
        },"json");      
    });

    $('#btn-PasswordCredentials').click(function (e){
        var data = { grant_type: "password", username: "adit", password: "pass", client_id: 'client', client_secret:'mysecret', scope:'country' };
        $.post('/ci-oauth2/oauth2/PasswordCredentials', data, function (d){
            console.log("Get Access Token from client credentials => ", d);
            $(".refresh-token").val(d.refresh_token);
            $(".token").val(d.access_token);
            $('#return-PasswordCredentials').html(JSON.stringify(d));
        },"json");
    });

    $("#btn-ClientCredentials").click(function (e){
        var data = {client_id: 'client', client_secret:'mysecret', grant_type:'client_credentials', scope:'country'};
        $.post('/ci-oauth2/oauth2/ClientCredentials', data, function (d){
            //d = d.JSON.parse(d);
            console.log("Get Access Token from password credentials => ", d);
            $(".token").val(d.access_token);
            $('#return-ClientCredentials').html(JSON.stringify(d));
        }, "json");
    });
});
</script>

authorize.php

<?php
$action = "/ci-oauth2/oauth2/Authorize?response_type=".$response_type."&client_id=".$client_id."&redirect_uri=".$redirect_uri."&state=".$state."&scope=".$scope;
?>

<body>
<div style="text-align:center;">
  <form method="post">
       <div class="oauth_content" node-type="commonlogin">
         <p class="oauth_main_info">Authorisasi?  <a href="http://www.aditya-nursyahbani.net/"  target="_blank" class="app_name">Ditya's Life</a></p>
   <input name="authorized" value="yes" hidden>
   <button>submit</button>
  </div>
    </form>
  
    </div>
</body>
</html>

Finally buatlah controller dengan nama Api.php fungsinya untuk membuat service-service apa saja yg mau diprovide / disediakan oleh web service, pada artikel ini kita mengambil contoh listing nama-nama negara. Ketikkan listing program berikut:

<?php
/**
* @package     Api.php
* @author      Aditya Nursyahbani
* @link        http://www.aditya-nursyahbani.net/2016/10/tutorial-oauth2-dengan-codeigniter.html
* @copyright   Copyright(c) 2016
* @version     1.0.0
**/

defined('BASEPATH') OR exit('No direct script access allowed');

require(APPPATH . 'libraries/REST_Controller.php');
 
class Api extends REST_Controller {

 function __construct(){
        @session_start();
        parent::__construct();
        $this->load->library("Server", "server");
     $this->server->require_scope("country");

        $this->load->database('oauth');
     $this->load->model('country_model');
    }

 function country_get(){
  if(!$this->get('id')) {
            $this->response(NULL, 400);
        }
 
        $country = $this->country_model->get($this->get('id'));
         
        if($country) {
            $this->response($country, 200); // 200 being the HTTP response code
        } else {
            $this->response(NULL, 404);
        }
 } 

 function countries_post(){
  $country = $this->country_model->get_all();
         
        if($country) {
            $this->response($country, 200); // 200 being the HTTP response code
        } else {
            $this->response(NULL, 404);
        }
 } 

}

Untuk mencoba oauth2nya ketikkan alamat http://localhost/ci-oauth2/oauth2/test

Download full source code pada artikel ini :

Link

Install mcrypt di Mac OS X Sierra

2016-10-16T23:40:00.002+07:00

Belum lama ini apple merilis sistem operasi baru (Operation System) Mac OS X Sierra. Banyak fitur-fitur baru yang ditawarkan dalam sierra ini. Bagi para developer Web, ternyata web server apache bawaan OS ini adalah versi 2.4 dengan PHP versi 5.6.24. Masalah yang sering timbul ketika update OS X salah satunya adalah service MySQL yang harus dikonfigurasi lagi karena tidak autostart (berjalan otomatis), sehingga perlu di konfigurasi lagi daemon mysqlnya supaya di load saat OS X startup.

Penasaran dengan OS X Sierra ini, akhirnya saya melakukan upgrade OS Macbook Pro. Selain harus mengkonfigurasi ulang service mysql, permasalahan yg timbul adalah extension Mcrypt atau extension yang biasa digunakan untuk mengenkripsi dan merupakan requirement jika kita mengembangkan web dengan framework Laravel ternyata tidak built in di PHP 5.6.24.

Untuk itu, kita harus melakukan compile dan build extension mcrypt secara manual agar dapat di load di PHP. Berikut ini merupakan langkah-langkanya agar ekstensi / library mcrypt dapat di jalankan:

Install Command Line Tools

caranya buka terminal / console ketikkan perintah berikut :

xcode-select --install

Disabled SIP / rootless

nonaktifkan System Integrity Protection (SIP) untuk mengijinkan akses terhadap folder sistem yg diproteksi. Kita tidak dapat menonaktifkan SIP ini dengan normal boot harus dari recovery boot. Berikut ini caranya:

Restart Mac OS X
Masuk ke Recovery Booting (pada saat bunyi startup chime, tekan Command + R secara bersamaan sampai masuk ke recovery booting)
Pilih Utilities -> Terminal
Ketika masuk jendela terminal, ketikkan :

csrutil disable

Download libmcrypt dan PHP

Download libmcrypt 2.5.8 dan PHP 5.6.24 sesuai dengan versi php built in.

Buat folder atau direktori mcrypt di home directory dan pindahkan hasil download ke dalam folder itu.

cd ~/
mkdir mcrypt
cd mcrypt

Ekstrak hasil download dan remove file gz

tar -zxvf libmcrypt-2.5.8.tar.gz
tar -zxvf php-5.6.24.tar.gz

rm *.gz

Konfigurasi libmcrypt

cd libmcrypt-2.5.8
./configure
make
sudo make install

Install Autoconf

cd ~/mcrypt
curl -0 http://ftp.gnu.org/gnu/autoconf/autoconf-latest.tar.gz
cd autoconf-2.69/
./configure
make install
sudo make install

Compile ekstensi libmcrypt pada PHP

cd ../php-5.6.24/ext/mcrypt/
/usr/bin/phpize

Kira-kira outputnya seperti ini :

PHP Api Version: 20131106
Zend Module Api No: 20131226
Zend Extension Api No: 220131226

./configure
make
sudo make install

Hasilnya kira-kira seperti ini:

Installing shared extensions: /usr/lib/php/extension/no-debug-non-zts-220131226

Mengaktifkan mcrypt di ekstensi PHP (mcrypt.so)

Buka php ini (/etc/php.ini), pastikan extension_dl = on dan tambahkan baris berikut di akhir file:

extension=mcrypt.so

Jika file php.ini tidak ada, lakukan hal berikut:

sudo cp /etc/php.ini.default /etc/php.ini
sudo chmod u+w /etc/php.ini

Finally restart apache

sudo service apache2 restart

Konfigurasi dan Instalasi Squid Proxy Server di Windows

2013-11-03T01:31:00.000+07:00

Setelah beberapa bulan udah jarang banget ngeblog, tiba-tiba hari ini gw kangen ngeblog. Pada blog post kali ini gw akan membahas tentang proxy server. Software proxy server yg akan kita gunakan adalah Squid Proxy Server (Squid 2.7 Stable8) dan kita akan mencoba instalasi dan konfigurasi pada platform Windows. Sebelum masuk ke pembahasan, apa sih proxy server itu...

Proxy server adalah sebuah server atau program komputer yang berperan sebagai penghubung antara suatu komputer dengan jaringan internet. Atau dalam kata lain, server proksi adalah suatu jaringan yang menjadi perantara antara jaringan lokal dan jaringan internet. Proxy server dapat berupa suatu sistem komputer ataupun sebuah aplikasi yang bertugas menjadi gateway atau pintu masuk yang menghubungan komputer kita dengan jaringan luar.

Proxy Server

Nah, sampai sini udah pada ngerti kan apa itu proxy server. Banyak manfaat yang dapat kita peroleh jika menggunakan proxy server. Berikut manfaat proxy server itu sendiri :

Mempercepat load page / halaman web yang sering diakses. Squid proxy server dapat melakukan caching web pages atau menyimpan isi dari halaman-halaman yang sering dikunjungi sehingga dapat mempercepat loading halaman web dan juga dapat menghemat bandwidth internet anda.
Content filtering. Dengan menggunakan squid proxy server kita juga memfilter content / memblokir situs-situs pornografi atau situs-situs berbahaya berdasarkan domain, IP ataupun keyword suatu URL.
Squid proxy server juga dapat mengatur kontrol daftar akses / access list, mengalokasi kan bandwith dan membatasi size download.

Instalasi dan Konfigurasi

Download terlebih dahulu Squid 2.7 Stable8.zip untuk sistem operasi Windows.
Ekstrak folder squid dari file Squid 2.7 Stable8.zip dan letakkan pada direktori c:\
Sebelum menginstall squid, lakukan konfigurasi squid terlebih dahulu. File-file konfigurasi squid terletak pada direktori C:\squid\etc\. Terdapat 4 file didalam direktori tersebut

cachemgr.conf.default
mime.conf.default
squid.conf.default
squid_radius_auth.conf.default.

Hapus / Rename semua file dengan ekstensi .default menjadi .conf sehingga semua file menjadi :

cachemgr.conf
mime.conf
squid.conf
squid_radius_auth.conf

Konfigurasi Squid

Buka file squid.conf yang terletak pada direktori C:\squid\etc\ dengan menggunakan Notepad atau text editor lainnya.

1. Setting port squid proxy

Gunakan fungsi Search/Find pada text editor anda, cari dengan kata kunci TAG: http_port. Tentukan no. port yang akan digunakan untuk proxy server, port yang umumnya digunakan adalah port 3128 atau anda juga dapat merubahnya dengan no. port lain.
Sintaks: http_port [no.port] atau http_port [hostname:no.port]
Contoh: http_port 3128 atau http_port localhost:3128 atau http_port 127.0.0.1:3128

# TAG: http_port
# Usage: port [options]
#  hostname:port [options]
#  1.2.3.4:port [options]
#
# The socket addresses where Squid will listen for HTTP client
...
# If you run Squid on a dual-homed machine with an internal
# and an external interface we recommend you to specify the
# internal address:port in http_port. This way Squid will only be
# visible on the internal address.
#
# Squid normally listens to port 3128
http_port 3128

2. Setting Daftar Akses / Access List (acl) dan http_access

ACL digunakan untuk membuat suatu rule/aturan yg akan diterapkan. Gunakan fungsi Search/Find pada text editor anda, cari dengan kata kunci TAG: acl. Karena jaringan di rumah saya menggunakan IP standar 192.168.1.0/24. Maka saya definisikan IP jaringan saya dengan nama_acl my_network (sesuaikan dengan IP jaringan anda).
Sintaks: acl [nama_acl] [tipe_acl] [argument/file]
Contoh: acl my_network src 192.168.1.0/24

# TAG: acl
#  TAG: acl
# Defining an Access List
#
#    Every access list definition must begin with an aclname and acltype, 
#    followed by either type-specific arguments or a quoted filename that
#    they are read from.
#
...
#Recommended minimum configuration:
acl all src all
acl manager proto cache_object
acl localhost src 127.0.0.1/32
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32
#
# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl my_network src 192.168.1.0/24
#

Setelah mendefinisikan access list, langkah selanjutnya adalah pemberian akses (Allow atau Deny) acl yang telah dibuat sebelumnya. Gunakan kembali fungsi find/search pada text editor anda dan cari TAG: http_access. Tambahkan sintaks http_access allow localhost dan http_access allow my_network tepat dibawah sintaks http_access allow localnet untuk memberikan ijin akses internet (http) ke localhost (127.0.0.1) dan IP jaringan kita yg telah didefinisikan pada acl.

#  TAG: http_access
# Allowing or Denying access based on defined access lists
#
# Access to the HTTP port:
# http_access allow|deny [!]aclname ...
#
...
#Recommended minimum configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager
# Deny requests to unknown ports
http_access deny !Safe_ports
# Deny CONNECT to other than SSL ports
http_access deny CONNECT !SSL_ports
#
...
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost
http_access allow my_network

# And finally deny all other access to this proxy
http_access deny all
#

3. Setting DNS (Domain Name Server)

Untuk konfigurasi DNS sesuaikan dengan DNS ISP anda. Untuk alamat DNS Server yang menggunakan Speedy dapat dilihat disini. Konfigurasi DNS bisa anda cari pada TAG: dns_nameservers. Pada tutorial ini saya menggunakan DNS Speedy sebagai DNS primarynya dan OpenDNS untuk DNS secondarynya.
Sintaks: dns_nameservers [DNS Primary] [DNS Secondary]
Contoh: dns_nameservers 202.134.2.5 208.67.222.222

#  TAG: dns_nameservers
# Use this if you want to specify a list of DNS name servers
# (IP addresses) to use instead of those given in your
# /etc/resolv.conf file.
# On Windows platforms, if no value is specified here or in
# the /etc/resolv.conf file, the list of DNS name servers are
# taken from the Windows registry, both static and dynamic DHCP
# configurations are supported.
#
# Example: dns_nameservers 10.0.0.1 192.172.0.4
#
dns_nameservers 202.134.2.5 208.67.222.222
#

CodeIgniter Login Tutorial

2013-03-12T20:22:00.002+07:00

CodeIgniter Login

CodeIgniter Login System Tutorial - Pada kesempatan kali ini saya akan coba membahas tentang bagaimana membuat sistem login dan register account dengan menggunakan framework CodeIgniter, MySQL sebagai database servernya dan Twitter Bootstrap untuk user interface nya. CodeIgniter merupakan PHP framework yang cukup mudah untuk dipelajari dan juga mendukung konsep MVC (Model View Controller). Tutorial ini juga membahas sedikit tentang bagaimana mudahnya membuat GUI (front-end) dengan menggunakan Twitter Bootstrap.

Twitter Bootsrap merupakan sebuah framework yang cukup populer juga saat ini yang dibangun oleh mantan web designer Twitter @mdo dan @fat. Fitur dan komponen Twitter Bootstrap cukup lengkap dengan berbagai animasi yg menarik, kita dapat menggunakan jQuery untuk animasi ataupun dengan html markup yang sudah disediakan. Selain itu, kita tidak perlu lagi membangun web dengan dua versi, versi desktop atau versi mobile, karena Twitter Bootstrap dilengkapi dengan fitur responsive design, kita hanya perlu memodifikasi css dengan mendefinisikan style CSS berdasarkan lebarnya resolusi layar. Thumbnail diatas adalah screenshoot aplikasi pada tutorial ini yg dijalankan di iPhone.

Fitur aplikasi yang akan dibangun :

Proses login ke sistem (memanfaatkan CI Session dan Library Form Validation).
Proses pendaftaran akun (register / create account).
Lihat data akun detail.

Berikut merupakan hasil akhir versi desktop-nya :

CodeIgniter Login - Login and Register Form

Persiapan

XAMPP (Apache Webserver, PHP and MySQL includes)
CodeIgniter 2.1.3
Twitter Bootstrap 2.3.1
jQuery 1.8.3

Database

Hal yang pertama dilakukan adalah membuat basis data (database) dengan MySQL, masuk ke phpMyAdmin, input SQL sintax dibawah ini pada menu SQLquery atau sintax pada phpMyAdmin :

CREATE DATABASE `ci-login` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

USE `ci-login`;

CREATE TABLE IF NOT EXISTS `account` (
  `first_name` varchar(30) NOT NULL,
  `last_name` varchar(30) NOT NULL,
  `email_address` text NOT NULL,
  `username` varchar(30) NOT NULL,
  `password` text NOT NULL,
  PRIMARY KEY  (`username`)
) ENGINE = MYISAM CHARACTER SET utf8 COLLATE utf8_general_ci;

INSERT INTO `account` (`first_name`, `last_name`, `email_address`, `username`, `password`) VALUES
('Aditya', 'Nursyahbani', 'admin@localhost.com', 'admin', '21232f297a57a5a743894a0e4a801fc3');

Alternatif lain, anda juga dapat melakukan fungsi import phpMyAdmin dari hasil dumping file ci-login.sql yg terdapat di source code aplikasi ini. Setting konfigurasi CodeIgniter (config.php, autoload.php, database.php, route.php). Setting base_url dan encryption_key untuk dapat menggunakan CodeIgniter Session, untuk lebih jelas bisa di lihat di tutorial sebelumnya membuat captcha dengan CodeIgniter.

Model

Model merepresentasikan bagaimana operasi / perintah-perintah terhadap suatu basis data yang umumnya terdiri dari CRUD (Create Read Update Delete) operation. Pada tutorial kali ini kita hanya menggunakan satu model dengan nama account_model.php yang terdiri dari fungsi validasi login, membuat akun baru dan untuk melihat akun detail. Buat file account_model.php (application/models) yang isinya sebagai berikut :

<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');

class Account_model extends CI_Model {
  private $table_name = 'account';
  private $pk = 'username';
  
  public function validasi() {
    $this->db->where('username', $this->input->post('username'));
    $this->db->where('password', md5($this->input->post('password')));
    $query = $this->db->get($this->table_name);
    if($query->num_rows == 1) {
      return true;
    }
  }
  
  public function buat_akun() {
    $data_baru = array(   
      'first_name'    => $this->input->post('fname'),
      'last_name'     => $this->input->post('lname'),
      'email_address' => $this->input->post('email'),
      'username'      => $this->input->post('uname'),
      'password'      => md5($this->input->post('pass'))
    );    
    $simpan_data = $this->db->insert($this->table_name, $data_baru);
    return $simpan_data;
  }
  
  public function lihat_data($username){
    $query = $this->db->get_where($this->table_name, array($this->pk => $username));
    return $query->row_array(); 
  }
}
/* End of file account_model.php */
/* Location: ./application/models/account_model.php */

Controller

Controller merupakan mediator antara Model dan View dalam konsep MVC dimana semua request/response di handle oleh controller. Misal user melakukan login yg diakses dari form login (View) -> Controller menerima request dan mengeksekusi fungsi cek login, jika data form yang di submit lengkap, Controller memanggil fungsi validasi pada Model dan Model akan mengecek form yang di submit dengan data yang ada pada database kemudian memberikan nilai kembalian berupa TRUE atau FALSE, pada akhirnya Controller memberikan response kepada user (View). Pada tutorial ini kita akan membuat 2 Controller (application/controllers), login dan user Controller. Controller login menghandle fungsi untuk validasi login, membuat akun dan fungsi logout sedangkan Controller user menghandle fungsi untuk melihat detail akun dan pada saat controller ini di inisialisasi akan menjalankan fungsi pengecekan session yang aktif.

<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');

class Login extends CI_Controller {

  public function __construct(){
    parent::__construct();
    $this->load->model('account_model');
  }

  public function index(){
    $data['content'] = 'login';
    $this->load->view('template/index', $data);
  }
  
  public function cek_login(){
    $user = $this->input->post('username');
    $pass = $this->input->post('password');
 
    if(empty($user) or empty($pass)){
      $this->session->set_flashdata('msg', 'Username or password can\'t be blank');
      redirect('login');
    }
 
    $query = $this->account_model->validasi();
    if($query){
      $data = array(
        'username' => $user,
        'is_logged_in' => true   
      );
 
      $this->session->set_userdata($data);
      redirect('user');
    }else{
      $this->session->set_flashdata('msg', 'Invalid username and password');
      redirect('login');
    }
  }
  
  public function signup(){
    $this->load->library('form_validation');
    $this->form_validation->set_rules('fname', 'First Name', 'trim|required');
    $this->form_validation->set_rules('lname', 'Last Name', 'trim|required');
    $this->form_validation->set_rules('email', 'Email Address', 'trim|required|valid_email');
    $this->form_validation->set_rules('uname', 'Username', 'trim|required|min_length[4]');
    $this->form_validation->set_rules('pass', 'Password', 'trim|required|min_length[6]|max_length[16]');
    $this->form_validation->set_rules('repass', 'Re-Password', 'trim|required|matches[pass]');
 
    if($this->form_validation->run() == FALSE){
      $data['content'] = 'login';
      $this->load->view('template/index', $data);
    }else{
      if($query = $this->account_model->buat_akun()){
        $this->session->set_flashdata('success', 'Your account successfully created! you can login now');
        redirect('login');
      }else{
        $this->session->set_flashdata('msg', 'Error insert database');
        redirect('login');
      }
    }
  }
  
  public function logout(){
    $this->session->sess_destroy();
    $this->index();
  }
}
/* End of file login.php */
/* Location: ./application/controllers/login.php */

Line 5-8 Memanggil / load account_model pada saat inisialisasi controller.
Line 10-13 Menampilkan form login/register ketika tidak ada request method atau fungsi pada controller.
Line 15-37 Fungsi untuk validasi login, jika username atau password kosong akan dikembalikan ke form login dengan pesan error, jika lengkap akan dicocokkan dengan data yang ada pada database. Jika hasilnya cocok maka, 2 sesi / session yang akan di daftarkan, sesi dengan nama username yang menampung nama user yang login dan sesi dengan nama is_logged_in yang diisi dengan nilai true dan akan di arahkan ke controller user.
Line 39-60 Fungsi untuk pendaftaran akun baru yang didalamnya terdapat perintah untuk validasi form input. jika input valid maka data akan di simpan pada database, jika invalid akan muncul pesan error.
Line 62-65 Fungsi untuk logout akun, sesi user yang aktif akan dihapus / dihancurkan dan redireksi ke halaman login.

<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');

class User extends CI_Controller{
  
  public function __construct(){
    parent::__construct();
    $this->is_logged_in(); 
  }
  
  public function index(){
    $data['content'] = 'user_area';
    $this->load->view('template/index', $data);
  }
  
  public function view_account(){
    $this->load->model('account_model');
    $data['account'] = $this->account_model->lihat_data($this->session->userdata('username'));
    $data['content'] = 'user_detail';
    $this->load->view('template/index', $data);
  }  
  
  public function is_logged_in(){
    $is_logged_in = $this->session->userdata('is_logged_in');
    if(!isset($is_logged_in) || $is_logged_in != true){
      $this->session->set_flashdata('msg', 'Access denied! You don\'t have permission to access this page or session has expired. Please use login form!');
      redirect('login');
    }
  }
}
/* End of file user.php */
/* Location: ./application/controllers/user.php */

View

View merupakan antar muka atau tampilan (Graphical User Interface) yang akan berinteraksi langsung dengan end user. Tutorial ini akan menggunakan view yang dinamis (di generate dari template) karena halaman yang statis seperti header, footer dan script akan dipanggil berulang-ulang setiap kali halaman di load, sedangkan halaman yang dinamis yang umumnya berubah yaitu halaman content yang isinya berdasarkan hasil request. Berikut merupakan hirarki view (application/views) yang akan dibuat :

template/ (direktori/folder)

header.php
content.php
footer.php
script.php
modal.php
index.php

login.php
user_area.php
user_detail.php

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>CodeIgniter Login Example Using Twitter Bootstrap</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link href="<?=base_url();?>css/bootstrap.min.css" rel="stylesheet">
    <link href="<?=base_url();?>css/bootstrap-responsive.min.css" rel="stylesheet">
    <link href="<?=base_url();?>css/style.css" rel="stylesheet">
  </head>
  <body>

Buat file content.php pada direktori application/views/template. Kosongkan isinya karena konten akan di generate dinamis dari controller.

<footer class="footer">
  <p>Copyright © 2013 - <a href="https://aditya-nursyahbani.com/">Aditya Nursyahbani</a></p>
</footer>

    </div><!-- /container -->
    <script src="<?=base_url();?>js/jquery-1.8.3.min.js"></script>
    <script src="<?=base_url();?>js/bootstrap.min.js"></script>
  </body>
</html>

<div id="help" class="modal hide fade" tabindex="-1" role="dialog" aria-labelledby="helpLabel" aria-hidden="true">
  <div class="modal-header">  
    <button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
 <h3 id="helpLabel">Help</h3>
  </div><!-- /modal-header -->
  <div class="modal-body">
    <h4>Create Account</h4>
 <p>Create a new account for accessing the user area. You can fill the registration form and click submit button to proceed. After have an account, you can use your <code>Username</code> and <code>Password</code> for login.</p><hr/>
 <h4>Login</h4>
 <p>This is login menu for accessing user area. <code>Username</code> and <code>Password</code> are required.</p><hr/>
 <h4>Logout</h4>
 <p>This is logout menu for exit the application (user area) and destroy the active session.</p><hr/>
 <h4>View Account Detail</h4>
 <p>This menu display the current user account information.</p><hr/>
 <div class="media">
   <a class="pull-left" href="#"><img class="media-object" src="<?=base_url('img/download.png');?>" width="64px" height="64px"></a>
   <div class="media-body">
     <h4 class="media-heading">Download the source code</h4>The source code for this application available on <a href="https://github.com/adit-gudhel/ci-login" target="_blank">GitHub</a> repository.
   </div>
 </div>
    <div class="media">
      <a class="pull-left" href="#"><img class="media-object" src="<?=base_url('img/message.png');?>" width="64px" height="64px"></a>
      <div class="media-body">
        <h4 class="media-heading">Comments and questions</h4>Post your questions and comments on the my blog post link below.
      </div>
    </div>
    <div class="media">
      <a class="pull-left" href="#"><img class="media-object" src="<?=base_url('img/blog.png');?>" width="64px" height="64px"></a>
      <div class="media-body">
        <h4 class="media-heading">Tutorial</h4>See full tutorial on my blog post <a href="https://dityalovers.blogspot.com/2013/03/codeigniter-login-tutorial.html" target="_blank">CodeIgniter Login Tutorial</a>.
      </div>
    </div>
    <div class="media">
      <a class="pull-left" href="#"><img class="media-object" src="<?=base_url('img/twitter.png');?>" width="64px" height="64px"></a>
      <div class="media-body">
        <h4 class="media-heading">Follow me on Twitter</h4><a href="https://twitter.com/adit_gudhel" target="_blank">@adit_gudhel</a>.
      </div>
    </div><hr/>
  </div><!-- /modal-body -->
  <div class="modal-footer">
    <button class="btn" data-dismiss="modal" aria-hidden="true">Close</button>
  </div><!-- /modal-footer -->
</div><!-- /modal -->

<?= $this->load->view('template/header'); ?>
<?= $this->load->view($content); ?>
<?= $this->load->view('template/footer'); ?>
<?= $this->load->view('template/script'); ?>

<?php include 'template/modal.php'; ?>
<div class="navbar navbar-inverse navbar-fixed-top">
  <div class="navbar-inner">
    <div class="container">
      <!-- .btn-navbar is used as the toggle for collapsed navbar content -->
      <a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
        <span class="icon-bar"></span><span class="icon-bar"></span><span class="icon-bar"></span>
      </a>
      <a class="brand" href="<?=base_url();?>">CodeIgniter</a>
      <div class="nav-collapse collapse">
        <ul class="nav pull-right">
          <li class="dropdown">
            <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button">Account <b class="caret"></b></a>
            <ul class="dropdown-menu dropdown-form">
              <li><?php
          echo form_open('signin');
       echo form_fieldset();
       echo form_label('Username');
       echo form_input('username');
       echo form_fieldset_close();
       echo form_fieldset();
       echo form_label('Password');
       echo form_password('password');
       $data = array(      
         'type'    => 'submit',
      'class'   => 'btn pull-right',
      'content' => 'Login'    
       );
       echo form_button($data);
       echo form_fieldset_close();
       echo form_close(); ?>
                <li class="divider"></li>
                <li><a href="#help" data-toggle="modal" data-target="#help">Help</a></li>
              </li>
            </ul>
          </li>
        </ul>
      </div><!--/.nav-collapse -->
    </div><!--/container -->
  </div><!--/.navbar-inner -->
</div><!--/.navbar -->
<div class="container"><?php
  if($this->session->flashdata('msg') != ''){
    echo '
    <div class="row-fluid">
      <div class="span12 alert alert-error">
        <button type="button" class="close" data-dismiss="alert">×</button>'.$this->session->flashdata('msg').'
      </div>
    </div>';
  }  
  if($this->session->flashdata('success') != ''){
    echo '
    <div class="row-fluid">
      <div class="span12 alert alert-success">
     <button type="button" class="close" data-dismiss="alert">×</button>'.$this->session->flashdata('success').'
   </div>
    </div>';
  } ?>
  <div class="row-fluid">
    <div class="span6">
 <?php
   $data = array('class' => 'form-register');
   echo form_open('signup',$data); ?>
      <h2 class="form-register-heading">Create Account</h2>
    <?php
   $data = array('name' => 'fname', 'class' => 'input-block-level', 'placeholder' => 'First Name', 'value' => set_value('fname'));
   echo form_input($data);
   $data = array('name' => 'lname', 'class' => 'input-block-level', 'placeholder' => 'Last Name', 'value' => set_value('lname'));
   echo form_input($data);
   $data = array('name' => 'email', 'class' => 'input-block-level', 'placeholder' => 'Email Address', 'value' => set_value('email'));
   echo form_input($data);
   $data = array('name' => 'uname', 'class' => 'input-block-level', 'placeholder' => 'Username', 'value' => set_value('uname'));
   echo form_input($data);
   $data = array('name' => 'pass', 'class' => 'input-block-level', 'placeholder' => 'Password');
   echo form_password($data);
   $data = array('name' => 'repass', 'class' => 'input-block-level', 'placeholder' => 'Re-Password');
   echo form_password($data);
   $data = array('type' => 'submit', 'class' => 'btn btn-large btn-primary', 'content' => 'Submit');
   echo form_button($data);
   echo form_close();
 ?>
    </div><!--/.span6 -->
    <div class="span6">
      <h1>Login Example</h1>
      <p>Welcome to CodeIgniter Login Example using session</p>
    <?php   
   if(validation_errors()){
     echo'
  <div class="row-fluid">
    <div class="span12 alert alert-error">
      <button type="button" class="close" data-dismiss="alert">×</button>'.validation_errors().'
       </div>
  </div>';
   }
 ?>
    </div><!--/.span6 -->
  </div> <!--/row -->

<div class="navbar navbar-inverse navbar-fixed-top">
  <div class="navbar-inner">
    <div class="container">
   <!-- .btn-navbar is used as the toggle for collapsed navbar content -->
   <a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
     <span class="icon-bar"></span><span class="icon-bar"></span><span class="icon-bar"></span>
   </a>
   <a class="brand" href="<?=base_url();?>user">CodeIgniter</a>
   <div class="nav-collapse collapse">
     <ul class="nav pull-right">
    <li class="dropdown">
      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button">
   <?= $this->session->userdata('username'); ?> <b class="caret"></b></a>
   <ul class="dropdown-menu dropdown-form">
     <li><a href="<?=base_url();?>user/detail">View Account Detail</a></li>
     <li class="divider"></li>
     <li><a href="<?=base_url();?>signout">Logout</a></li>
   </ul>
    </li><!--/.dropdown -->
     </ul>
   </div><!--/.nav-collapse -->
 </div><!--/.container -->
  </div><!--/.navbar-inner -->
</div><!--/.navbar -->
<div class="container">
  <div class="row">
    <div class="span12">
   <div class="hero-unit">
     <h1>Home</h1>
  <p>Welcome <strong><?=$this->session->userdata('username');?></strong>,<br/>This is the main user area.</p>
   </div><!--/.hero-unit -->
 </div><!--/.span12 -->
  </div><!--/.row -->

<div class="navbar navbar-inverse navbar-fixed-top">
  <div class="navbar-inner">
    <div class="container">
      <!-- .btn-navbar is used as the toggle for collapsed navbar content -->
      <a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
        <span class="icon-bar"></span><span class="icon-bar"></span><span class="icon-bar"></span>
      </a>
      <a class="brand" href="<?=base_url();?>user">CodeIgniter</a>
      <div class="nav-collapse collapse">
        <ul class="nav pull-right">
          <li class="dropdown">
            <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button"><?= $account['username']; ?> <b class="caret"></b></a>            <ul class="dropdown-menu dropdown-form">
              <li>
                <li><a href="<?=base_url();?>user/detail">View Account Detail</a></li>
                <li class="divider"></li>
                <li><a href="<?=base_url();?>signout">Logout</a></li>
              </li>
            </ul>
          </li>
        </ul>
      </div><!--/.nav-collapse -->
    </div>
  </div>
</div><!--/.navbar -->
<div class="container">
  <div class="row-fluid">
    <div class="span12">
      <div class="hero-unit">
        <h1><?= ucfirst($account['first_name']); ?> <?= ucfirst($account['last_name']); ?></h1>
        <p><?= $account['username']; ?></p>
      </div>
    </div>
  </div>
  <div class="row-fluid">
    <div class="span12">
      <legend>Your Account Detail :</legend>
      <div class="row-fluid">
        <div class="span8">
          <ul class="nav nav-tabs">
            <li class="active"><a href="#fname" data-toggle="tab">First Name</a></li>
            <li><a href="#lname" data-toggle="tab">Last Name</a></li>
            <li><a href="#email" data-toggle="tab">Email Address</a></li>
          </ul>
          <div class="tab-content">
            <div class="tab-pane active" id="fname"><p><?= $account['first_name']; ?></p></div>
            <div class="tab-pane" id="lname"><p><?= $account['last_name']; ?></p></div>
            <div class="tab-pane" id="email"><p><?= $account['email_address']; ?></p></div>
          </div>
        </div>
        <div class="span4"><p class="text-center"><img class="img-circle" width="140" height="140" src="<?= base_url('img/adit.jpg'); ?>"</p></div>
      </div>
    </div>
  </div>

Finally konfigurasi route.php (application/config) :

$route['user/logout'] = "login/logout";
$route['user/detail'] = "user/view_account";
$route['user'] = "user";

$route['signout'] = "login/logout";

$route['signin'] = "login/cek_login";
$route['signup'] = "login/signup";
$route[':any'] = "login";

$route['default_controller'] = "login";
$route['404_override'] = '';

Screenshoot aplikasi

CodeIgniter Login - Form Validation Error

CodeIgniter Login - Account Created

CodeIgniter Login - Error

CodeIgniter Login - Invalid Username and Password

CodeIgniter Login - View Account Detail

Download the source code

Source code ci-login.zip
Fork me on GitHub repository.

Cara RMA Hard Disk Seagate

2013-02-27T03:17:00.003+07:00

Berikut ini merupakan tutorial langkah demi langkah (step-by-step) untuk melakukan RMA (Return Material Authorization) Hard Disk Seagate, maksudnya RMA adalah mengembalikan Hardisk yang rusak Merk Seagate ke Pihak Seagate untuk diperbaiki dan diganti dengan hard disk pengganti, dengan syarat hard disk yg rusak masih dalam masa garansi.

Minggu yang lalu, pas gw nyalain komputer di BIOS POST message muncul tulisan "S.M.A.R.T Harddisk Check Failure, Press F1 to Continue". Awalnya gw pikir cuma error biasa / cuma scan disk, tapi ternyata setiap booting komputer selalu muncul message tersebut. Ternyata pas gw scan harddisk pake fitur CHKDSK-nya windows, harddisk Seagate 1 Tb gw ada BAD SECTOR-nya. Sempet gw panik, bukan karena data penting / data kuliah / data skripsi gw, tapi koleksi film gw yg udah merenggut 50% dari kapasitas harddisk gw :). Akhirnya gw googling dan ternyata Seagate menyediakan fasilitas RMA, harddisk gw kembali normal lagi dalam 1 minggu.

How-To :

Catat Serial Number (S/N) dan Model Number Harddisk yang ingin dikembalikan. Ada dua cara untuk mengecek S/N dan Model Number harddisk Seagate :

Pertama, bisa dilihat langsung pada fisik harddisk.

S/N dan Model Number Harddisk Seagate
Kedua, dengan menggunakan software SeaTools for Windows (Download dan install, scan hardisk menggunakan software ini, harddisk dalam kondisi terpasang di komputer / laptop).

Short Generic Test using SeaTools for Windows

Cek status garansi harddisk yang rusak di https://support.seagate.com/customer/en-US/warranty_validation.jsp?form=0. Input Serial Number dan Model Number yang sudah dicatat sebelumnya, input kode captcha dan klik Submit.
Jika harddisk masih dalam masa garansi ("In Warranty"), Klik Create Return untuk membuat RMA Order. Ceklist Return dan klik Continue.
Input data-data Anda yang sudah disediakan pada form input Shipping Addres (masukan data dengan lengkap untuk memudahkan proses pengiriman kembali harddisk pengganti, cantumkan juga alamat email anda untuk memudahkan jika ada progress status Order RMA dikirimkan via email), ceklist I Accept Terms and Conditions, klik Review Order/Payment untuk melihat kembali data Order yang telah diinput.
Pilih lokasi pengiriman harddisk yang rusak (Return Location), ada 2 lokasi : PT UPS SCS Indonesia yang terletak di Bandara Soekarno Hatta dan langsung ke Seagate Singapore. Pilih yang terdekat sesuai dengan domisili anda. less shipping cost :)
Pada form berikutnya, Catat Order Number anda. Order Number digunakan untuk mengecek status dan progress Order anda. Klik Print Mailing Label untuk mencetak alamat return location dan order number anda yang nantinya ditempelkan di paket anda pada saat melakukan pengiriman harddisk yang rusak.

Mailing Label (ditempel pada paket yg akan dikirim)
Sebelum melakukan pengiriman harddisk yang rusak ke alamat return location, baca terlebih dahulu petunjuk packing seagate.pdf agar harddisk yang dikirim tidak ditolak oleh Seagate. Backup juga data pada harddisk jika masih memungkinkan, anda juga dapat request jasa backup data dari Seagate (dengan biaya tambahan). Kirim Paket harddisk yang rusak ke alamat Return Location bisa menggunakan jasa JNE/Tiki.
Cek status Order RMA anda secara berkala di https://store.seagate.com. Input Order Number dan Nama Belakang anda, klik Find your Order.
Jika Order Status masih Open dan Received by Seagate No, berarti harddisk yang rusak belum diterima oleh Seagate. Order Status akan menjadi Closed jika harddisk sudah diterima dan dikirimkan kembali.

Cek RMA Order Detail
Seagate akan mengirimkan UPS Tracking Number ke email atau jika harddisk pengganti telah dikirim. Atau juga bisa dicek pada menu Shipment Details pada RMA Order Detail.

Cek Tracking Number pada Shipment Detail
Untuk tracking UPS dapat dicek di situs https://www.ups.com/tracking/tracking.html dengan cara input data Tracking Number yang telah diterima.

Tracking Shipment on UPS Tracking Website

Berikut kronologis kejadiannya (Proses RMA 1 Minggu) :

Senin (18/02/2013)

- Gw cek garansi harddisk dan ternyata masih valid sampai Juli 2013, akhirnya gw daftarin harddisk / Order RMA di situs Seagate.

Selasa (19/02/2013)
- Gw paketin hardisk gw yg rusak dan gw kirim ke alamat Seagate return location yang di Bandara Soeta, PT UPS SCS Indo.

Jumat (22/02/2013)

- Gw terima email (Seagate RMS Receipt Acknowledment RMA) dari seagate yang isinya harddisk yang gw paketin udah nyampe di Seagate Singapore (Received by Seagate) dan Total Return Unrepaired Quantity (RUR) gw 0, klo RUR-nya lebih dari ( >) 0 maka RMA kita ditolak (rejected).

- Gw terima email lg dari Seagate klo harddisk pengganti udah dikirim melalui jasa UPS dan juga gw dapet Tracking Number UPS. Gw coba track ke UPS ternyata Tracking Numbernya Invalid.

Senin (25/02/2013)

- Akhirnya gw track lg di UPS ternyata order gw baru diproses hari ini dan harddisk masih di UPS Singapore.

Selasa (26/02/2013)
- Finally, Harddisk Seagate 1 Tb akhirnya sampe di rumah gw :)

Metroon Windows 8 Dreamboard Theme

2013-02-11T01:00:00.000+07:00

Metroon Dreamboard Theme

Metroon - Windows 8 Metro UI a-like Dreamboard Themes for iPhone. If you wanna make your iPhone looks like Windows 8 GUI (Metro Style UI), you can try this stunning theme that consists of many features like :

Pin / Unpin System
A dynamic pin and unpin system. You can pin any app you like to the home screen. Tiles are auto created but can be customized in many different ways.

Pin / Unpin to Start Menu

HTML 'Live' Tiles
You can use any html widget as a 'live' tile. All live tiles that were compatible with OS7/OS7:Revive will work on with theme.

Desktop Tile
A tile that uses your current wallpaper and allows you to switch to your regular iOS interface without loading times. A press on the home button brings you back to the Metroon interface.

Metroon Desktop View

Easy Way To Change The Tile Size
The tile can be made smaller or larger with the press of a single button.

Lockscreen
A windows style lockscreen with custom media controls that shows your latest appointment you have set in your local calendar app.

Metroon Lockscreen with Control Music Playlist

Launch Animations
The Windows 8 launch and close animations.

Metroon view All Apps

Integrated Music Live Tile
A large music live tile that shows the album art, title and artist of the currently playing song. Pressing the 'smaller' button will change the tile to only show the album artwork.

Integrated Calendar Live Tile
A large calendar tile that shows your latest appointment you have set in your local calendar app.

Integrated Messaging Live Tile
A large messaging tile that shows the latest message you received.

Customization
This theme can (and should be) heavily customized. Things that can be customized:

The tile's/app's name that is displayed
The tile's badge position and size (both for small and large tiles)
The tile image (both for small and large tiles)
The tile image when it has a badge (both for small and large tiles)
The username
The user icon
The background
Every background color

There is a settings section from which you can choose the backgrounds and accent colors you made yourself. There is an unlimited number of slots, so you can have an infinite amount of wallpapers and colors stored that can easily be applied from within the theme.

Download

Metroon_1.1.2-1.deb (see how to install .deb / debian file on iOS)
Original Tile.zip (The tiles shown in the Windows 8 Consumer Preview and included in the Metroon download)
ColorKeyboard Teal Theme.
Metroon_Live_People_tile.zip.

Credit to ModMyi forums :)

Untethered Jailbreak iOS 6 with evasi0n

2013-02-04T21:24:00.000+07:00

evasi0n

Setelah lama ditunggu-tunggu, akhirnya iOS 6 rilis juga Untethered Jailbreak-nya. Maksudnya Untethered Jailbreak, klo iDevice kita mati abis batre / reboot itu tidak memerlukan bantuan komputer untuk booting OS. Berkat perjuangan Evad3rs Team yang terdiri dari @pimskeks, @planetbeing, @pod2g dan @MuscleNerd yang baru saja meluncurkan program bernama evasi0n. evasi0n merupakan sebuah program/software yang dapat digunakan untuk menjailbreak iOS 6.1 (Untethered), evasi0n juga dapat berjalan pada multi platform OS (Linux, Windows and Mac OS X).

Evasi0n supported devices :

iPhone 5
iPhone 4S
iPhone 4
iPhone 3GS
iPad 4
iPad 3 (aka The New iPad)
iPad 2
iPad Mini
iPod Touch 5
iPod Touch 4

Evasi0n iOS firmware supported :

iOS 6.0
iOS 6.0.1
iOS 6.0.2
iOS 6.1

Sebelum melakukan jailbreak, perhatikan hal-hal berikut :

Cek dulu kompabilitas (Cydia Tweaks) khususnya bagi yang masih running iOS 5.1.1, apakah banyak yang kompatibel dengan iOS 6. Soalnya untuk iDevice yg menggunakan processor A5 keatas itu ga bisa downgrade meskipun kita memiliki SHSH blobs Tapi klo iPhone 5 yang bawaan OSnya iOS 6, ga usah pake ragu :)

How-To :

Backup device terlebih dahulu dengan menggunakan iTunes ataupun menggunakan iCloud untuk mencegah terjadinya kesalahan atau kehilangan / data loss sebelum menggunakan evasi0n.
Jika passcode device (Lock Device) diaktifkan, matikan terlebih dahulu.
Pada saat melakukan jailbreak menggunakan evasi0n, pastikan tidak menjalankan iTunes atau program-program lainnya yang dapat mengganggu / menghambat proses jailbreak.
Jika

Downloads :

evasi0n

iOS 6.1 Official Firmware (.ipsw)

iPhone 5 (GSM, CDMA)
iPhone 4S
iPhone 4 (GSM, CDMA)
iPhone 3GS
iPad Mini (GSM, CDMA, Wi-Fi)
iPad 4 (GSM, CDMA, Wi-Fi)
iPad 3 (GSM, CDMA, Wi-Fi)
iPad 2 (GSM, CDMA, Wi-Fi)
iPad 2 16Gb (new)
iPod Touch (4th Generation, 5th Generation)

Backup Cydia Package dengan AppToDeb

2012-10-08T07:52:00.002+07:00

AppToDeb merupakan tweak cydia (Cydia Tweaks) yang dapat digunakan untuk konversi aplikasi-aplikasi yang telah diinstal dari Cydia menjadi file debian (.deb). AppToDeb juga dapat digunakan untuk membuat backup Cydia Package, jadi kita tidak perlu repot mencari aplikasi pada repository Cydia dan menginstall kembali aplikasi / themes yang diinstal dari Cydia ketika ingin melakukan upgrade iOS firmware.

Untuk melakukan backup aplikasi Cydia (single application file backup) menjadi file debian (.deb) berikut langkah-langkahnya:

Buka Aplikasi AppToDeb

AppToDeb Cydia Tweaks
Pilih dan Tap aplikasi yang ingin di backup.
Tap menu make deb.

Make Deb File from AppToDeb
Hasil / outputnya adalah file debian (.deb) yang terletak pada direktori /var/mobile/Library/AppToDeb/ (browse filenya menggunakan iFile dan simpan baik-baik)

Deb File Location

Selain digunakan untuk backup, AppToDeb juga dapat digunakan untuk modifikasi file control debian (berguna jika ingin membuat repository cydia sendiri). Kita dapat mengetahui ketergantungan (Depends) file pada suatu aplikasi Cydia dan modifikasi metadata lainnya.

Modifying debian control on AppToDeb

Bagi yang belum tau atau masih bingung untuk install file debian (.deb) di iOS devices, silahkan kunjungi artikel install file dengan ekstensi .ipa dan .deb

Download AppToDeb :

via Cydia

insanelyi repo
Gudhel Cydia Repository (alternate)

Buka Cydia, tap Manage, tap Source, tap Edit, tap Add, input Cydia/APT URL https://repo.aditya-nursyahbani.com/, browse dan install AppToDeb.

AppToDeb.deb (debian file)