Let's say you want to host domains first.com
and second.com
.
Create folders for their files:
$ aws configure --profile account1 | |
// To use the profile | |
$ aws s3 ls --profile account2 | |
// To set the default profile | |
$ export AWS_DEFAULT_PROFILE=account1 |
kubectl get services # List all services | |
kubectl get pods # List all pods | |
kubectl get nodes -w # Watch nodes continuously | |
kubectl version # Get version information | |
kubectl cluster-info # Get cluster information | |
kubectl config view # Get the configuration | |
kubectl describe node <node> # Output information about a node | |
kubectl get pods # List the current pods | |
kubectl describe pod <name> # Describe pod <name> | |
kubectl get rc # List the replication controllers |
So you've defined a cronjob.yaml manifest, but it doesn't run until midnight and you want to test it now? Simply replace the variables, and run the following command to create a job from the cronjob.
kubectl create job --from=cronjob/{{ cron_job_name }} {{ the-name-of-this-one-off-job }}
This will create a one-off job in your cluster based on your cronjob.yaml manifest, which might look something like this.
apiVersion: batch/v1beta1
Instruction collected from multiple sources, there may be unnecessary steps, but that what worked with me after 4 days of stuggling :), so I'm recording it all
Install Xdebug 2.9.8
using pecl
sudo apt -y install php7.4-dev php-pear
pecl install xdebug-2.9.8
Create xdebug.ini file in mods-available
DROP TABLE IF EXISTS wp_users; | |
CREATE TABLE wp_users ( | |
ID bigint(20) unsigned NOT NULL auto_increment, | |
user_login varchar(60) NOT NULL default '', | |
user_pass varchar(64) NOT NULL default '', | |
user_nicename varchar(50) NOT NULL default '', | |
user_email varchar(100) NOT NULL default '', | |
user_url varchar(100) NOT NULL default '', | |
user_registered datetime NOT NULL default '0000-00-00 00:00:00', | |
user_activation_key varchar(60) NOT NULL default '', |