Cheatsheet
- https://www.commandlinefu.com
Blog
- dev.to
Cloud Computing
- https://learntocloud.guide
- https://www.server-world.info
Youtube
- Belajar Data Science dari Nol : LINK
Prerequisites
Izinkan Akses MySQL Remote dengan Firewald
Step 1. Buat Sebuah Zona.
firewall-cmd –new-zone=mysql-access –permanent
Step 2. Untuk menerapkan perubahan, reload ulang firewalld.
firewall-cmd –reload
Jika Anda ingin memeriksa ulang dan membuat daftar zona firewalld, jalankan:
firewall-cmd –get-zones
Step 3. Pertama tambahkan alamat IP yang ingin Anda izinkan.
firewall-cmd –zone=mysql-access –add-source=96.52.17.9/32 –permanent
Step 4. Saya akan menambahkan port default MySQL 3306. Jika Anda menggunakan port kustom Anda sendiri, ubahlah di pengaturan.
firewall-cmd –zone=mysql-access –add-port=3306/tcp –permanent
Step 5. Muat ulang firewall untuk menerapkan perubahan baru.
firewall-cmd –reload
Step 6. Untuk memastikan zona akses mysql dikonfigurasi dengan benar, jalankan:
firewall-cmd –zone=mysql-access –list-all
Output:
mysql-access (active) target: default icmp-block-inversion: no interfaces: sources: 96.52.17.9/32 services: ports: 3306/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:
Sekarang Anda harus dapat membuat koneksi antara server MySQL Anda dan mesin Anda. Kesimpulan
Jika Anda memerlukan beberapa aturan khusus untuk diaktifkan atau dinonaktifkan terkait MySQL bisa di konfigurasi dengan firewalld.
Typing vagrant from the command line will display a list of all available commands.
Be sure that you are in the same directory as the Vagrantfile when running these commands!
Creating a VM
vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.
Starting a VM
vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)
vagrant resume -- resume a suspended machine (vagrant up works just fine for this as well)
vagrant provision -- forces reprovisioning of the vagrant machine
vagrant reload -- restarts vagrant machine, loads new Vagrantfile configuration
vagrant reload --provision -- restart the virtual machine and force provisioning
Getting into a VM
vagrant ssh -- connects to machine via SSH
vagrant ssh <boxname> -- If you give your box a name in your Vagrantfile, you can ssh into it with boxname. Works from any directory.
Stopping a VM
vagrant halt -- stops the vagrant machine
vagrant suspend -- suspends a virtual machine (remembers state)
Cleaning Up a VM
vagrant destroy -- stops and deletes all traces of the vagrant machine
vagrant destroy -f -- same as above, without confirmation
Boxes
vagrant box list -- see a list of all installed boxes on your computer
vagrant box add <name> <url> -- download a box image to your computer
vagrant box outdated -- check for updates vagrant box update
vagrant box remove <name> -- deletes a box from the machine
vagrant package -- packages a running virtualbox env in a reusable box
Saving Progress
-vagrant snapshot save [options] [vm-name]
vagrant -v -- get the vagrant version
vagrant status -- outputs status of the vagrant machine
vagrant global-status -- outputs status of all vagrant machines
vagrant global-status --prune -- same as above, but prunes invalid entries
vagrant provision --debug -- use the debug flag to increase the verbosity of the output
vagrant push -- yes, vagrant can be configured to deploy code!
vagrant up --provision | tee provision.log -- Runs vagrant up, forces provisioning and logs all output to a file
Plugins
vagrant-hostsupdater : $ vagrant plugin install vagrant-hostsupdater to update your /etc/hosts file automatically each time you start/stop your vagrant box.
Notes
If you are using VVV, you can enable xdebug by running vagrant ssh and then xdebug_on from the virtual machine's CLI.