composer about
composer self-update
composer require <vendor/packagename>
composer global require <vendor/packagename>
See the previouse step here.
First,
apt-get install git-core # maybe suggest installing "git" without "-core"
Next step, i forget..
# SSH Section unstable tutorial, so keep it in mind.
ssh-keygen -t rsa
cat ~/.ssh/id_rsa.pub && ssh git@ipaddress "cat >> ~/.ssh/authorized_keys"
# Creating repo (Server side)
inside /home/git
mkdir repo
cd repo
mkdir test.git
git init --bare test.git
cd test.git
git remote add origin git@ipaddress:repo/test.git
# Clone repo (Client side)
cd
mkdir gitlocal
cd gitlocal
git clone git@ipaddress:repo/test.git
# Enter password (it should suing id_rsa.pub rather than login from ssh)
These must be fixed later...
First,
apt-get install git-core # maybe suggest installing "git" without "-core"
Next step, i forget..
# SSH Section unstable tutorial, so keep it in mind.
ssh-keygen -t rsa
cat ~/.ssh/id_rsa.pub && ssh git@ipaddress "cat >> ~/.ssh/authorized_keys"
# Creating repo (Server side)
inside /home/git
mkdir repo
cd repo
mkdir test.git
git init --bare test.git
cd test.git
git remote add origin git@ipaddress:repo/test.git
# Clone repo (Client side)
cd
mkdir gitlocal
cd gitlocal
git clone git@ipaddress:repo/test.git
# Enter password (it should suing id_rsa.pub rather than login from ssh)
These must be fixed later...
Ingredients:
0. Main OS
1. Have an .iso file for the latest version of Ubuntu Server (download here)
2. Have an Virtual Box inside your Debian (I'm using Kali Linux)
* why using virtual?
* we can modify anything even that Operating System is broken, we just need to reinstall without worrying "Whooaa!! I forget to backup my latest documents... Shit!!"
Steps for creating new virtual machine:
1. Create new OS
2. Name it as Ubuntu Server
3. See addition setting like x32/x64 is match or not with your .iso file
4. Next and follow the recommend setting
5. Wait! You need set your VM path inside your main OS, so it's not eat the Main System Storage
Installing Ubuntu Server:
1. Run the Virtual Ubuntu Server in your Virtual Box
2. Follow the instruction
3. Use entire disk (or else for advanced)
4. Setup name, hostname, username, password
5. Mark as checked for "Ubuntu Server Featured Snaps", may be like these package:
- postgresql
- i forget
- i forget, later will be updated..
Setup network adapter to connect between main OS and Virtual OS:
0. Shutdown the Virtual OS (if it's running)
1. Open your Virtual Box app
2. Select the OS and click Settings
3. Open Network menu and choose Adapter 2
4. Select "Host-only Adapter" on field "Attached to"
5. Select "vboxnet0" on field "Name"
6. Save/OK
7. Run the OS
--------- separator --------
IP Addressing Section
--------- separator --------
8. Login and sudo su
9. Ifconfig and check the interface that was not have and IP address
9b. Remember the interface name, i think the name is 'enp0s8', right?
10. Edit network interfaces using : $ vim /etc/network/interfaces
10b. Write like this:
```
auto enp0s8
iface enp0s8 inet dhcp
```
11. Save and exit vim
12. Restart networking using `service networking restart`
# apt-get install ifupdown # may it needed
Done
Test ping between main OS and Virtual OS
This step is required for the next article.
0. Main OS
1. Have an .iso file for the latest version of Ubuntu Server (download here)
2. Have an Virtual Box inside your Debian (I'm using Kali Linux)
* why using virtual?
* we can modify anything even that Operating System is broken, we just need to reinstall without worrying "Whooaa!! I forget to backup my latest documents... Shit!!"
Steps for creating new virtual machine:
1. Create new OS
2. Name it as Ubuntu Server
3. See addition setting like x32/x64 is match or not with your .iso file
4. Next and follow the recommend setting
5. Wait! You need set your VM path inside your main OS, so it's not eat the Main System Storage
Installing Ubuntu Server:
1. Run the Virtual Ubuntu Server in your Virtual Box
2. Follow the instruction
3. Use entire disk (or else for advanced)
4. Setup name, hostname, username, password
5. Mark as checked for "Ubuntu Server Featured Snaps", may be like these package:
- postgresql
- i forget
- i forget, later will be updated..
Setup network adapter to connect between main OS and Virtual OS:
0. Shutdown the Virtual OS (if it's running)
1. Open your Virtual Box app
2. Select the OS and click Settings
3. Open Network menu and choose Adapter 2
4. Select "Host-only Adapter" on field "Attached to"
5. Select "vboxnet0" on field "Name"
6. Save/OK
7. Run the OS
--------- separator --------
IP Addressing Section
--------- separator --------
8. Login and sudo su
9. Ifconfig and check the interface that was not have and IP address
9b. Remember the interface name, i think the name is 'enp0s8', right?
10. Edit network interfaces using : $ vim /etc/network/interfaces
10b. Write like this:
```
auto enp0s8
iface enp0s8 inet dhcp
```
11. Save and exit vim
12. Restart networking using `service networking restart`
# apt-get install ifupdown # may it needed
Done
Test ping between main OS and Virtual OS
This step is required for the next article.
When i using composer, node, npm, ionic, and other frameworks to install or update some packages, it will checking for the resources availbility on server and it take so long even your network is okay for opening website like Google and YouTube.
Solution is update your dns-nameserver using default DNS that your router get from the ISP. Some people still using 8.8.8.8 or 8.8.4.4 as the dns-nameserver configuration.
For the primary DNS you can set with 192.168.1.1 (your network gateway) and let the router retrieve the default DNS from the ISP. For the second DNS you can set with Google DNS or else.
Some command to check your network:
# ifconfig (Linux) / ipconfig (Windows)
Your wifi's configuration for ssid and password that generated using wpa_passphrase is surely right, router configuration and your network interface setting not the problem.
So, check this file "/etc/dbus-1/system.d/wpa_supplicant.conf". If there is a 'epitest' word in there, do a backup for this file and edit after it. Delete all 'epitest' word on that file and save. Make sure there is no double dot (.) after you delete the 'epitest' word.
After that, run `killall wpa_supplicant` and `wpa_supplicant -B -i wlan0 -Dwext -c /etc/wpa_supplicant.conf`. If there is an error with parameter, run again without `-B` and open new terminal for run another command, that is `dhclient wlan0` and wait until dhclient command was done.
Finally, check `ipconfig` and make sure your wlna0 success getting ip from the rotuer/hotspot/access point.

