A delightful community-driven framework for managing your bash configuration, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.

:neckbeard: Powerful Slack CLI via pure bash. Rich messaging, uploads, posts, piping, oh my!

:see_no_evil: oh-my-zsh on bash on windows configuration files

Bash style history substitution for Oh My Fish

nixos, nix-darwin, homebrew, oh-my-zsh, dotbot, dotbins, macos, linux, submodules, zsh, bash, awesome modern CLI tools — no place like ~/

Bash.env is a cascading Bash environment system for those who work on different hardware and OS environments. Similar to oh-my-zsh but for Bash, and special sauce for those who work 'ssh' on remote machines.

SEIS 665 Assignment 2: Linux & Git Overview This week we will focus on becoming familiar with launching a Linux server and working with some basic Linux and Git commands. We will use AWS to launch and host the Linux server. AWS might seem a little confusing at this point. Don’t worry, we will gain much more hands-on experience with AWS throughout the course. The goal is to get you comfortable working with the technology and not overwhelm you with all the details. Requirements You need to have a personal AWS account and GitHub account for this assignment. You should also read the Git Hands-on Guide and Linux Hands-on Guide before beginning this exercise. A word about grading One of the key DevOps practices we learn about in this class is the use of automation to increase the speed and repeatability of processes. Automation is utilized during the assignment grading process to review and assess your work. It’s important that you follow the instructions in each assignment and type in required files and resources with the proper names. All names are case sensitive, so a name like "Web1" is not the same as "web1". If you misspell a name, use the wrong case, or put a file in the wrong directory location you will lose points on your assignment. This is the easiest way to lose points, and also the most preventable. You should always double-check your work to make sure it accurately reflects the requirements specified in the assignment. You should always carefully review the content of your files before submitting your assignment. The assignment Let’s get started! Create GitHub repository The first step in the assignment is to setup a Git repository on GitHub. We will use a special solution called GitHub Classroom for this course which automates the process of setting up student assignment repositories. Here are the basic steps: Click on the following link to open Assignment 2 on the GitHub Classroom site: https://classroom.github.com/a/K4zcVmX- (Links to an external site.)Links to an external site. Click on the Accept this assignment button. GitHub Classroom will provide you with a URL (https) to access the assignment repository. Either copy this address to your clipboard or write it down somewhere. You will need to use this address to set up the repository on a Linux server. Example: https://github.com/UST-SEIS665/hw2-seis665-02-spring2019-<your github id>.git At this point your new repository to ready to use. The repository is currently empty. We will put some content in there soon! Launch Linux server The second step in the assignment is to launch a Linux server using AWS EC2. The server should have the following characteristics: Amazon Linux 2 AMI 64-bit (usually the first option listed) Located in a U.S. region (us-east-1) t2.micro instance type All default instance settings (storage, vpm, security group, etc.) I’ve shown you how to launch EC2 instances in class. You can review it on Canvas. Once you launch the new server, it may take a few minutes to provision. Log into server The next step is to log into the Linux server using a terminal program with a secure shell (SSH) support. You can use iTerm2 (Links to an external site.)Links to an external site. on a Mac and GitBash/PuTTY (Links to an external site.)Links to an external site. on a PC. You will need to have the private server key and the public IP address before attempting to log into the server. The server key is basically your password. If you lose it, you will need to terminate the existing instance and launch a new server. I recommend reusing the same key when launching new servers throughout the class. Note, I make this recommendation to make the learning process easier and not because it is a common security practice. I’ve shown you how to use a terminal application to log into the instance using a Windows desktop. Your personal computer or lab computer may be running a different OS version, but the process is still very similar. You can review the videos on the Canvas. Working with Linux If you’ve made it this far, congratulations! You’ve made it over the toughest hurdle. By the end of this course, I promise you will be able to launch and log into servers in your sleep. You should be looking at a login screen that looks something like this: Last login: Mon Mar 21 21:17:54 2016 from 174-20-199-194.mpls.qwest.net __| __|_ ) _| ( / Amazon Linux AMI ___|\___|___| https://aws.amazon.com/amazon-linux-ami/2015.09-release-notes/ 8 package(s) needed for security, out of 17 available Run "sudo yum update" to apply all updates. ec2-user@ip-172-31-15-26 ~]$ Your terminal cursor is sitting at the shell prompt, waiting for you to type in your first command. Remember the shell? It is a really cool program that lets you start other programs and manage services on the Linux system. The rest of this assignment will be spent working with the shell. Note, when you are asked to type in a command in the steps below, don’t type in the dollar-sign ($) character. This is just meant to represent the command prompt. The actual commands are represented by the characters to the right of the command prompt. Let’s start by asking the shell for some help. Type in: $ help The shell provides you with a list of commands you can run along with possible command options. Next, check out one of the pages in the built-in manual: $ man ls A man page will appear with information on how to use the ls command. This command is used to list the contents of file directories. Either space through the contents of the man page or hit q to exit. Most of the core Linux commands have man pages available. But honestly, some of these man pages are a bit hard to understand. Sometimes your best bet is to search on Google if you are trying to figure out how to use a specific command. When you initially log into Linux, the system places you in your home directory. Each user on the system has a separate home directory. Let’s see where your home directory is located: $ pwd The response should be /home/ec2-user. The pwd command is handy to remember if you ever forget what file directory you are currently located in. If you recall from the Linux Hands-on Guide, this directory is also your current working directory. Type in: $ cd / The cd command let’s you change to a new working directory on the server. In this case, we changed to the root (/) directory. This is the parent of all the other directories on the file system. Type in: $ ls The ls command lists the contents of the current directory. As you can see, root directory contains many other directories. You will become familiar with these directories over time. The ls command provides a very basic directory listing. You need to supply the command with some options if you want to see more detailed information. Type in: $ ls -la See how this command provides you with much more detailed information about the files and directories? You can use this detailed listing to see the owner, group, and access control list settings for each file or directory. Do you see any files listed? Remember, the first character in the access control list column denotes whether a listed item is a file or a directory. You probably see a couple files with names like .autofsck. How come you didn’t see this file when you typed in the lscommand without any options? (Try to run this command again to convince yourself.) Files names that start with a period are called hidden files. These files won’t appear on normal directory listings. Type in: $ cd /var Then, type in: $ ls You will see a directory listing for the /var directory. Next, type in: $ ls .. Huh. This directory listing looks the same as the earlier root directory listing. When you use two periods (..) in a directory path that means you are referring to the parent directory of the current directory. Just think of the two dots as meaning the directory above the current directory. Now, type in: $ cd ~ $ pwd Whoa. We’re back at our home directory again. The tilde character (~) is another one of those handy little directory path shortcuts. It always refers to our personal home directory. Keep in mind that since every user has their own home directory, the tilde shortcut will refer to a unique directory for each logged-in user. Most students are used to navigating a file system by clicking a mouse in nested graphical folders. When they start using a command-line to navigate a file system, they sometimes get confused and lose track of their current position in the file system. Remember, you can always use the pwd command to quickly figure out what directory you are currently working in. Let’s make some changes to the file system. We can easily make our own directories on the file system. Type: mkdir test Now type: ls Cool, there’s our new test directory. Let’s pretend we don’t like that directory name and delete it. Type: rmdir test Now it’s gone. How can you be sure? You should know how to check to see if the directory still exists at this point. Go ahead and check. Let’s create another directory. Type in: $ mkdir documents Next, change to the new directory: $ cd documents Did you notice that your command prompt displays the name of the current directory? Something like: [ec2-user@ip-172-31-15-26 documents]$. Pretty handy, huh? Okay, let’s create our first file in the documents directory. This is just an empty file for training purposes. Type in: $ touch paper.txt Check to see that the new file is in the directory. Now, go back to the previous directory. Remember the double dot shortcut? $ cd .. Okay, we don’t like our documents directory any more. Let’s blow it away. Type in: $ rmdir documents Uh oh. The shell didn’t like that command because the directory isn’t empty. Let’s change back into the documents directory. But this time don’t type in the full name of the directory. You can let shell auto-completion do the typing for you. Type in the first couple characters of the directory name and then hit the tab key: $ cd doc<tab> You should use the tab auto-completion feature often. It saves typing and makes working with the Linux file system much much easier. Tab is your friend. Now, remove the file by typing: $ rm paper.txt Did you try to use the tab key instead of typing in the whole file name? Check to make sure the file was deleted from the directory. Next, create a new file: $ touch file1 We like file1 so much that we want to make a backup copy. Type: $ cp file1 file1-backup Check to make sure the new backup copy was created. We don’t really like the name of that new file, so let’s rename it. Type: $ mv file1-backup backup Moving a file to the same directory and giving it a new name is basically the same thing as renaming it. We could have moved it to a different directory if we wanted. Let’s list all of the files in the current directory that start with the letter f: $ ls f* Using wildcard pattern matching in file commands is really useful if you want the command to impact or filter a group of files. Now, go up one directory to the parent directory (remember the double dot shortcut?) We tried to remove the documents directory earlier when it had files in it. Obviously that won’t work again. However, we can use a more powerful command to destroy the directory and vanquish its contents. Behold, the all powerful remove command: $ rm -fr documents Did you remember to use auto-completion when typing in documents? This command and set of options forcibly removes the directory and its contents. It’s a dangerous command wielded by the mightiest Linux wizards. Okay, maybe that’s a bit of an exaggeration. Just be careful with it. Check to make sure the documents directory is gone before proceeding. Let’s continue. Change to the directory /var and make a directory called test. Ugh. Permission denied. We created this darn Linux server and we paid for it. Shouldn’t we be able to do anything we want on it? You logged into the system as a user called ec2-user. While this user can create and manage files in its home directory, it cannot change files all across the system. At least it can’t as a normal user. The ec2-user is a member of the root group, so it can escalate its privileges to super-user status when necessary. Let’s try it: $ sudo mkdir test Check to make sure the directory exists now. Using sudo we can execute commands as a super-user. We can do anything we want now that we know this powerful new command. Go ahead and delete the test directory. Did you remember to use sudo before the rmdir command? Check to make sure the directory is gone. You might be asking yourself the question: why can we list the contents of the /var directory but not make changes? That’s because all users have read access to the /var directory and the ls command is a read function. Only the root users or those acting as a super-user can write changes to the directory. Let’s go back to our home directory: $ cd ~ Editing text files is a really common task on Linux systems because many of the application configuration files are text files. We can create a text file by using a text editor. Type in: $ nano myfile.conf The shell starts up the nano text editor and places your terminal cursor in the editing screen. Nano is a simple text-based word processor. Type in a few lines of text. When you’re done writing your novel, hit ctrl-x and answer y to the prompt to save your work. Finally, hit enter to save the text to the filename you specified. Check to see that your file was saved in the directory. You can take a look at the contents of your file by typing: $ cat myfile.conf The cat command displays your text file content on the terminal screen. This command works fine for displaying small text files. But if your file is hundreds of lines long, the content will scroll down your terminal screen so fast that you won’t be able to easily read it. There’s a better way to view larger text files. Type in: $ less myfile.conf The less command will page the display of a text file, allowing you to page through the contents of the file using the space bar. Your text file is probably too short to see the paging in action though. Hit q to quit out of the less text viewer. Hit the up-arrow key on your keyboard a few times until the commmand nano myfile.conf appears next to your command prompt. Cool, huh? The up-arrow key allows you to replay a previously run command. Linux maintains a list of all the commands you have run since you logged into the server. This is called the command history. It’s a really useful feature if you have to re-run a complex command again. Now, hit ctrl-c. This cancels whatever command is displayed on the command line. Type in the following command to create a couple empty files in the directory: $ touch file1 file2 file3 Confirm that the files were created. Some commands, like touch. allow you to specify multiple files as arguments. You will find that Linux commands have all kinds of ways to make tasks more efficient like this. Throughout this assignment, we have been running commands and viewing results on the terminal screen. The screen is the standard place for commands to output results. It’s known as the standard out (stdout). However, it’s really useful to output results to the file system sometimes. Type in: $ ls > listing.txt Take a look at the directory listing now. You just created a new file. View the contents of the listing.txt file. What do you see? Instead of sending the output from the ls command to the screen we sent it to a text file. Let’s try another one. Type: $ cat myfile.conf > listing.txt Take a look at the contents of the listing.txt file again. It looks like your myfile.conf file now. It’s like you made a copy of it. But what happened to the previous content in the listing.txt file? When you redirect the output of a command using the right angle-bracket character (>), the output overwrites the existing file. Type this command in: $ cat myfile.conf >> listing.txt Now look at the contents of the listing.txt file. You should see your original content displayed twice. When you use two angle-bracket characters in the commmand the output appends (or adds to) the file instead of overwriting it. We redirected the output from a command to a text file. It’s also possible to redirect the input to a command. Typically we use a keyboard to provide input, but sometimes it makes more sense to input a file to a command. For example, how many words are in your new listing.txt file? Let’s find out. Type in: $ wc -w < listing.txt Did you get a number? This command inputs the listing.txt file into a word count program called wc. Type in the command: $ ls /usr/bin The terminal screen probably scrolled quickly as filenames flashed by. The /usr/bin directory holds quite a few files. It would be nice if we could page through the contents of this directory. Well, we can. We can use a special shell feature called pipes. In previous steps, we redirected I/O using the file system. Pipes allow us to redirect I/O between programs. We can redirect the output from one program into another. Type in: $ ls /usr/bin | less Now the directory listing is paged. Hit the spacebar to page through the listing. The pipe, represented by a vertical bar character (|), takes the output from the ls command and redirects it to the less command where the resulting output is paged. Pipes are super powerful and used all the time by savvy Linux operators. Hit the q key to quit the paginated directory listing command. Working with shell scripts Now things are going to get interesting. We’ve been manually typing in commands throughout this exercise. If we were running a set of repetitive tasks, we would want to automate the process as much as possible. The shell makes it really easy to automate tasks using shell scripts. The shell provides many of the same features as a basic procedural programming language. Let’s write some code. Type in this command: $ j=123 $ echo $j We just created a variable named j referencing the string 123. The echo command printed out the value of the variable. We had to use a dollar sign ($) when referencing the variable in another command. Next, type in: $ j=1+1 $ echo $j Is that what you expected? The shell just interprets the variable value as a string. It’s not going to do any sort of computation. Typing in shell script commands on the command line is sort of pointless. We want to be able to create scripts that we can run over-and-over. Let’s create our first shell script. Use the nano editor to create a file named myscript. When the file is open in the editor, type in the following lines of code: #!/bin/bash echo Hello $1 Now quit the editor and save your file. We can run our script by typing: $ ./myscript World Er, what happened? Permission denied. Didn’t we create this file? Why can’t we run it? We can’t run the script file because we haven’t set the execute permission on the file. Type in: $ chmod u+x myscript This modifies the file access control list to allow the owner of the file to execute it. Let’s try to run the command again. Hit the up-arrow key a couple times until the ./myscript World command is displayed and hit enter. Hooray! Our first shell script. It’s probably a bit underwhelming. No problem, we’ll make it a little more complex. The script took a single argument called World. Any arguments provided to a shell script are represented as consecutively numbered variables inside the script ($1, $2, etc). Pretty simple. You might be wondering why we had to type the ./ characters before the name of our script file. Try to type in the command without them: $ myscript World Command not found. That seems a little weird. Aren’t we currently in the directory where the shell script is located? Well, that’s just not how the shell works. When you enter a command into the shell, it looks for the command in a predefined set of directories on the server called your PATH. Since your script file isn’t in your special path, the shell reports it as not found. By typing in the ./ characters before the command name you are basically forcing the shell to look for your script in the current directory instead of the default path. Create another file called cleanup using nano. In the file editor window type: #!/bin/bash # My cleanup script mkdir archive mv file* archive Exit the editor window and save the file. Change the permissions on the script file so that you can execute it. Now run the command: $ ./cleanup Take a look at the file directory listing. Notice the archive directory? List the contents of that directory. The script automatically created a new directory and moved three files into it. Anything you can do manually at a command prompt can be automated using a shell script. Let’s create one more shell script. Use nano to create a script called namelist. Here is the content of the script: #!/bin/bash # for-loop test script names='Jason John Jane' for i in $names do echo Hello $i done Change the permissions on the script file so that you can execute it. Run the command: $ ./namelist The script will loop through a set of names stored in a variable displaying each one. Scripts support several programming constructs like for-loops, do-while loops, and if-then-else. These building blocks allow you to create fairly complex scripts for automating tasks. Installing packages and services We’re nearing the end of this assignment. But before we finish, let’s install some new software packages on our server. The first thing we should do is make sure all the current packages installed on our Linux server are up-to-date. Type in: $ sudo yum update -y This is one of those really powerful commands that requires sudo access. The system will review the currently installed packages and go out to the Internet and download appropriate updates. Next, let’s install an Apache web server on our system. Type in: $ sudo yum install httpd -y Bam! You probably never knew that installing a web server was so easy. We’re not going to actually use the web server in this exercise, but we will in future assignments. We installed the web server, but is it actually running? Let’s check. Type in: $ sudo service httpd status Nope. Let’s start it. Type: $ sudo service httpd start We can use the service command to control the services running on the system. Let’s setup the service so that it automatically starts when the system boots up. Type in: $ sudo chkconfig httpd on Cool. We installed the Apache web server on our system, but what other programs are currently running? We can use the pscommand to find out. Type in: $ ps -ax Lots of processes are running on our system. We can even look at the overall performance of our system using the topcommand. Let’s try that now. Type in: $ top The display might seem a little overwhelming at first. You should see lots of performance information displayed including the cpu usage, free memory, and a list of running tasks. We’re almost across the finish line. Let’s make sure all of our valuable work is stored in a git repository. First, we need to install git. Type in the command: $ sudo yum install git -y Check your work It’s very important to check your work before submitting it for grading. A misspelled, misplaced or missing file will cost you points. This may seem harsh, but the reality is that these sorts of mistakes have consequences in the real world. For example, a server instance could fail to launch properly and impact customers because a single required file is missing. Here is what the contents of your git repository should look like before final submission: ┣archive ┃ ┣ file1 ┃ ┣ file2 ┃ ┗ file3 ┣ namelist ┗ myfile.conf Saving our work in the git repository Next, make sure you are still in your home directory (/home/ec2-user). We will install the git repository you created at the beginning of this exercise. You will need to modify this command by typing in the GitHub repository URL you copied earlier. $ git clone <your GitHub URL here>.git Example: git clone https://github.com/UST-SEIS665/hw2-seis665-02-spring2019-<your github id>.git The git application will ask you for your GitHub username and password. Note, if you have multi-factor authentication enabled on your GitHub account you will need to provide a personal token instead of your password. Git will clone (copy) the repository from GitHub to your Linux server. Since the repository is empty the clone happens almost instantly. Check to make sure that a sub-directory called "hw2-seis665-02-spring2019-<username>" exists in the current directory (where <username> is your GitHub account name). Git automatically created this directory as part of the cloning process. Change to the hw2-seis665-02-spring2019-<username> directory and type: $ ls -la Notice the .git hidden directory? This is where git actually stores all of the file changes in your repository. Nothing is actually in your repository yet. Change back to the parent directory (cd ..). Next, let’s move some of our files into the repository. Type: $ mv archive hw2-seis665-02-spring2019-<username> $ mv namelist hw2-seis665-02-spring2019-<username> $ mv myfile.conf hw2-seis665-02-spring2019-<username> Hopefully, you remembered to use the auto-complete function to reduce some of that typing. Change to the hw2-seis665-02-spring2019-<username> directory and list the directory contents. Your files are in the working directory, but are not actually stored in the repository because they haven’t been committed yet. Type in: $ git status You should see a list of untracked files. Let’s tell git that we want these files tracked. Type in: $ git add * Now type in the git status command again. Notice how all the files are now being tracked and are ready to be committed. These files are in the git staging area. We’ll commit them to the repository next. Type: $ git commit -m 'assignment 2 files' Next, take a look at the commit log. Type: $ git log You should see your commit listed along with an assigned hash (long string of random-looking characters). Finally, let’s save the repository to our GitHub account. Type in: $ git push origin master The git client will ask you for your GitHub username and password before pushing the repository. Go back to the GitHub.com website and login if you have been logged out. Click on the repository link for the assignment. Do you see your files listed there? Congratulations, you completed the exercise! Terminate server The last step is to terminate your Linux instance. AWS will bill you for every hour the instance is running. The cost is nominal, but there’s no need to rack up unnecessary charges. Here are the steps to terminate your instance: Log into your AWS account and click on the EC2 dashboard. Click the Instances menu item. Select your server in the instances table. Click on the Actions drop down menu above the instances table. Select the Instance State menu option Click on the Terminate action. Your Linux instance will shutdown and disappear in a few minutes. The EC2 dashboard will continue to display the instance on your instance listing for another day or so. However, the state of the instance will be terminated. Submitting your assignment — IMPORTANT! If you haven’t already, please e-mail me your GitHub username in order to receive credit for this assignment. There is no need to email me to tell me that you have committed your work to GitHub or to ask me if your GitHub submission worked. If you can see your work in your GitHub repository, I can see your work.

Alrc-termux is a framework designed to enrich the Termux user experience by providing bash shell configuration and useful plugins."

Oh-My-Bash site source code

终端美化神器，精美的控制台oh-my-posh配色方案，兼容Windows、Linux、MacOS、Terminal、Powershell、CMD、MSYS、wsl、iTerm、Termius、VS Code、GNOME、bash、zsh等

Oh My Zsh theme based on Parrot OS bash theme

Bash script to install Tmux, ZSH and other of my favorite tools. Autoconfigures tmux to work with ZSH, adds oh-my-zsh and plugins. Currently tested working in Manjaro, EndeavourOS, Ubuntu Mate, Parrot and Kali.

Oh My Bash xxh plugin

Bash automation script to get iTerm2, oh-my-zsh, Fig, material-design-colors, powerlevel9k and nerd-fonts on your Mac.

This script is a custom bash prompt inspired from Oh My ZSH Lambda Theme

Various time-saving scripts, in various languages, for various platforms. Bash scripts, AppleScripts, and PHP scripts, oh my!

How to setup Oh My Posh on Git Bash

my personal configs .bashrc

A bash script to install and config zsh, oh-my-zsh, zsh-syntax-highlighting, zsh-autosuggestions and neofetch in any linux distro automatically.

This Bash script contsin Oh-My-Zsh With command autosuggestion and syntax highlight pligins for TERMUX

Bash, Ack, Git - oh my!

Per Søderlind bagaimana caranya Menjalankan WordPress secara lokal di Mac OS X Lion, Mountain Lion, dan Mavericks Menjalankan WordPress secara lokal di Mac OS X Lion, Mountain Lion, dan Mavericks PER SØDERLIND26 AGUSTUS 2011 Apple dan WordPressIngin menjalankan WordPress di OSX? Saya ingin melakukannya untuk waktu yang lama dan akhirnya berhasil melakukannya. Multisite : Lihat catatan di bawah jika Anda berencana untuk menjalankan Jaringan WordPress (alias multisite) di Mac Anda. Baru : Berikut ini alternatifnya, lihat WordPress di Pow (termasuk "bagaimana cara menambahkan MySQL, PHP5.4.9 dan Ruby 1.9.3 ") Pembaruan: Mountain Lion dan Mavericks Berbagi Web di Mountain Lion dihapus dari System Preferences-> Sharing (tidak tahu mengapa), jadi untuk memulai server web, buka Terminal (atau iTerm ) dan masukkan: [shell light = "true"] $ sudo apachectl start [/ shell ] perintah utama apachectl adalah: start, stop, dan restart. Anda dapat mempelajari lebih lanjut tentang apachectl dengan memasukkan yang berikut di Terminal [shell light = "true"] $ man apachectl [/ shell] apachectl cukup ketika Anda perlu memulai, restart atau menghentikan server saat pengujian, tetapi jika Anda ingin server web untuk memulai secara otomatis setelah reboot, Anda harus mengaktifkan daemon peluncuran untuk server: [shell light = "true"] sudo defaults write /System/Library/LaunchDaemons/org.apache.httpd Disabled -bool false [/ shell] Buat /var/mysql/mysql.sock jika tidak ada (atau ganti /var/mysql/mysql.sock dengan /tmp/mysql.sock lebih jauh di bawah) [shell light = "true"] $ sudo mkdir / var / mysql $ sudo ln -s/tmp/mysql.sock/var / mysql/mysql.sock [/ shell] Juga, Jika Anda mengikuti petunjuk di bawah sebelumnya dan meningkatkan Singa Anda ke Mountain Lion, Anda harus mengaktifkan kembali PHP: [shell light = "true"] $ sudo sh -c "grep php /etc/apache2/httpd.conf|grep LoadModule | cut -d '#' -f2> /etc/apache2/other/php5-loadmodule.conf" $ sudo cp -a /etc/php.ini.default /etc/php.ini $ sudo sh -c “cat >> /etc/php.ini << 'EOF' ;; ;; Kustomisasi pengguna di bawah ; ; Asli - memory_limit = 128M memory_limit = 196M ; Asli - post_max_size = 8M post_max_size = 200M ; Asli - upload_max_filesize = 2M upload_max_filesize = 100M ; Asli - default_socket_timeout = 60 default_socket_timeout = 600 ; Asli - max_execution_time = 30 max_execution_time = 300 ; Asli - max_input_time = 60 max_input_time = 600 ; Asli - display_errors = Mati display_errors = on ; Asli - display_startup_errors = Tidak aktif display_startup_errors = on ; Asli -; date.timezone = date.timezone = 'America / New_York' // Ubah ke zona waktu Anda: http://www.php.net/manual/en/timezones.php EOF ” $ sudo sh -c “cat >> /etc/php.ini <<‘EOF’ ; Original – ;include_path = “.:/php/includes” include_path = “.:/usr/lib/php/pear” EOF” $ sudo sed -i “” ‘s#/var/mysql/mysql.sock#/tmp/mysql.sock#g’ /etc/php.ini $ sudo apachectl restart [/shell] How I installed MAMP + WordPress 1 ) Installed Apache, MySQL and PHP on my Mac. I followed this excellent guide: OS X 10.7 Lion Development: Native MAMP with MySQL installer. Here’s the /Users/<username>/Sites/httpd-vhosts.conf I made: [xml] # # Use name-based virtual hosting. # NameVirtualHost *:80 # # Set up permissions for VirtualHosts in ~/Sites # <Directory “/Users/<username>/Sites”> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny Allow from all </Directory> # For http://localhost in the OS X default location <VirtualHost _default_:80> ServerName localhost DocumentRoot /Library/WebServer/Documents </VirtualHost> # # VirtualHosts below # # wp.local <VirtualHost *:80> ServerName wp.local CustomLog “/Users/<username>/Sites/logs/wp.local-access_log” combined ErrorLog “/Users/<username>/Sites/logs/wp.local-error_log” DocumentRoot “/Users/<username>/Sites/wordpress” </VirtualHost> [/xml] 2) Installed WordPress in /Users/<username>/Sites/wordpress When I tried to install the first plugin, I got the dreaded FTP Connection Information required :/ Luckily, Google to the rescue, I found this fix to allow WordPress automatic plugin installation/update: A) Changed the owner and permissions for the entire WordPress installation, assuming you installed WordPress in /Users/<username>/Sites: [shell] $ cd /Users/<username>/Sites $ sudo chown -R :_www wordpress $ sudo chmod -R g+w wordpress [/shell] B) Added the following to /Users/<username>/Sites/wordpress/wp-config.php: [php light=”true”] define(‘FS_METHOD’, ‘direct’); [/php] How to create a WordPress multisite locally 1) Follow the instructions above, and create a separate database per multisite Easiest is to create a path-based (that is use sub-directories) multisite. My multisite virtual host looks like this: [xml] <VirtualHost *:80> ServerName mu.local CustomLog “/Users/<username>/Sites/logs/mu.local-access_log” combined ErrorLog “/Users/<username>/Sites/logs/mu.local-error_log” DocumentRoot “/Users/<username>/Sites/mu.local” </VirtualHost> [/xml] 2) When WordPress is up and running, follow steps 2 – 6 in the Create a Network guide. If you have any questions, please don’t hesitate to ask below. I’ll try to answer as soon as possible. Twitter Google+ Facebook LinkedIn Email Read Offline:Download PDFDownload ePubDownload mobiPrint INSTALLATIONMAC OS XMAMPMYSQLWORDPRESS PREVIOUS Upgraded to WordPress 3.2 and nothing worked (internal error …) NEXT Front-end editor in WordPress 3.3 is easy 30 Comments bananaaus You legend! MARCH 7, 2012 REPLY Jarratt Hello, I’m just setting up a local installation of WordPress on my Mac with OSX Lion. I’ve managed to install it but I can’t update any plugins, import my blog etc (I’m new to all this so flying blind so to speak). I have read something about changing my FTP permissions? I don’t really understand what the article above is saying, could you please give some further info for me? Thanks a lot, hopefully you can help! Jarratt APRIL 13, 2012 REPLY PerS You have to do the following: A) Changed the owner and permissions for the entire WordPress installation, assuming you installed WordPress in /Users/<username>/Sites: [code lang=”shell” light=”false”] $ cd /Users/<username>/Sites $ sudo chown -R :_www wordpress $ sudo chmod -R g+w wordpress [/code] B) Added the following to /Users/<username>/Sites/wordpress/wp-config.php: [php] define(‘FS_METHOD’, ‘direct’); [/php] APRIL 13, 2012 REPLY Jarratt Hi again, That’s great, all up an running now. Thanks a lot! APRIL 16, 2012 REPLY Nick So I am having a problem with permalinks after setting up my dev environment on OSX Lion. I have AllowOveride All in my httpd.conf and in my vhosts file as you show, mod_rewrite is enabled… Any ideas? Thanks! MAY 1, 2012 REPLY PerS Apakah .htaccess Anda dapat ditulisi oleh wordpress? Milik saya terlihat seperti ini (dan permalinks bekerja): [shell] # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine Pada RewriteBase / RewriteRule ^ index.php $ - [L] RewriteCond% {REQUEST_FILENAME}! -f RewriteCond% {REQUEST_FILENAME}! -d RewriteRule. /index.php [L] </ IfModule> # END WordPress [/ shell] 1 MEI 2012 BALASAN bla bla Sepertinya banyak masalah bagi saya, saya menggunakan mamp pro & coda, std mamp menginstal dan wordpress ke direktori wordpress di folder situs, tidak perlu untuk semua yang mengotak-atik hasil yang sama, oh dan semuanya bekerja seperti pada server langsung, email, permalinks, pembaruan untuk wordpress & plugin, .htaccess yang dapat ditulis dll 4 MEI 2012 BALASAN Bill Robbins Pembenci anonim menghisap. Jika Anda mengeluh cukup untuk meninggalkan sebagai komentar, setidaknya tunjukkan diri Anda. 26 JULI 2012 BALASAN chapman welch Terima kasih atas tipnya. Anda menyelamatkan saya beberapa jam rasa sakit dan penderitaan! 14 JUNI 2012 BALASAN Senica Terima kasih sudah mengirim. Membuatku gila. 9 AGUSTUS 2012 BALASAN Martyn Chamberlin Ini benar-benar luar biasa! Saya telah secara manual menginstal / memperbarui WordPress, kerangka kerja saya, dan plugin saya. Berkat tutorial ini, kerumitan jahat ini telah dikurangi menjadi beberapa klik sederhana. 29 AGUSTUS 2012 BALASAN PakPenyo solusi bagi saya adalah mengubah pengguna dan grup: sudo chown -R _www: _www wordpress Terima kasih. 12 OKTOBER 2012 BALASAN PerS Itu bagus, selama Anda adalah anggota grup _www, jika tidak Anda (seperti pada pengguna Anda) tidak dapat mengedit file. 12 OKTOBER 2012 BALASAN Yanns terima kasih banyak, namun ada pertanyaan .. haruskah saya peduli terhadap apa pun ketika saya memigrasikan situs lokal ke publik? Haruskah saya menghapus yang terakhir seperti dari wp-config.php? 27 JANUARI 2013 BALASAN PerS Saya menggunakan http://ithemes.com/purchase/backupbuddy/ ketika saya memindahkan situs dari localhost ke produksi. Itu melakukan perubahan yang diperlukan untuk wp-config.php 27 JANUARI 2013 BALASAN Yanns ya tetapi apakah menurut Anda membuat perubahan ke wp-config.php sudah cukup? Saya belum pernah melakukannya sebelumnya di WP tetapi saya pikir kita perlu memperbaiki hal-hal lain juga sebelum ditayangkan. Seperti tautan dll .. mungkin pertanyaan saya konyol tapi baiklah, saya akan mencengkeramnya sehari;) 27 JANUARI 2013 BALASAN Yanns ..dan apakah backupbuddy mengurus hak akses yang kami berikan dengan perintah di atas? Maksud saya untuk membuat mereka kembali normal. Saya tidak ingin ada masalah dengan hak akses ketika situs web online .. 27 JANUARI 2013 BALASAN Yanns di baris perintah saya (singa) itu mengatakan: -bash: Pengguna // Situs / pencarian / folder: Tidak ada file atau direktori seperti itu jalan hanyalah sebuah contoh. Saya mencoba mencari di mana jalan rusak, mencoba perintah $ cd dalam potongan kecil tetapi ada lagi masalah yang sama. apa yang harus saya lakukan? 27 JANUARI 2013 BALASAN PerS Anda harus mengganti <username> dalam contoh di atas dengan nama pengguna Anda. 27 JANUARI 2013 BALASAN Yanns Ya, saya telah melakukan itu. apa yang saya lakukan adalah untuk menggambarkan Anda jalan. Akhirnya, masalah itu disebabkan oleh hal konyol yang telah saya lakukan: Saya telah meletakkan spasi di nama file sehingga terminal tidak dapat menemukan folder .. Masalah lainnya adalah saya tidak menulis filepath yang benar. jadi saya mencarinya dan saya menemukan bahwa Anda dapat menulis 1-2 huruf pertama dari nama file Anda dan kemudian tekan Ctrl + tab (untuk mac itu sama, ex.Ctrl + tab, dan perintah + tab tidak akan berfungsi) . Setelah Anda melakukannya, terminal akan menulis nama file untuk Anda! .. Terakhir, masalah lain adalah bahwa saya sedang menulis ..sudo chown -R: _www wordpress Kesalahan saya: Saya harus menulis nama folder induk file. Saya pikir wordpress itu bagian dari perintah. Jadi yang benar adalah: sudo chown -R: _www exampleFilename (ofcourse juga berlaku untuk chmod) Cheers! 27 JANUARI 2013 BALASAN Aidan Boyle Luar biasa! Terima kasih telah memposting ini. Saya memiliki waktu dengan yang satu ini dan ini melakukan trik segera terima kasih! 21 MARET 2013 BALASAN Phil Dipasang WP tetapi memiliki probs ketika mengunggah media karena masalah perizinan. Diburu selama berabad-abad untuk mencari solusi. Situs Anda menyortirnya segera. Tepuk tangan. 8 APRIL 2013 BALASAN PerS Adian dan Phil, Senang aku dapat membantu. Tolong beritahu orang lain menggunakan twitter dll. 8 APRIL 2013 BALASAN Babass Halo, saya memiliki kesalahan saat pemasangan plugin. Sebelum masalah akses ditolak folder, saya memiliki pesan kesalahan baru: “Paket tidak dapat dipasang. PCLZIP_ERR_BAD_FORMAT (-10): Tidak dapat menemukan tanda End of Central Dir Record " Apa artinya? terimakasih atas bantuannya 12 APRIL 2013 BALASAN PerS Ini biasanya berarti bahwa arsip plugin tidak dapat diekstraksi karena terlalu sedikit ruang disk, tetapi mungkin juga karena ini: http://core.trac.wordpress.org/ticket/22913 14 APRIL 2013 BALASAN Babass Terima kasih atas balasan Anda, ini masalah format. Saya mengunggah file zip, dan sekarang berfungsi. 18 APRIL 2013 BALASAN steve Anda harus memasang plugin secara lokal hanya dengan mengubah grup ke _www untuk wp-content dan menambahkan izin menulis ke grup, lalu menambahkan define ('FS_METHOD', 'direct'); baris ke wp-config Anda. 9 JUNI 2014 BALASAN Jarod Taylor Setelah mengubah izin, direktori direktori localhost / ~ username saya tidak ditemukan. 28 NOVEMBER 2014 BALASAN Per Søderlind Apakah ini di Mac OS X Yosemite? Saya berhenti menggunakan apache lokal, saya menggunakan https://github.com/Chassis/Chassis sebagai gantinya.

Vim and Bash and Git, oh my!

List of Oh My Bash / Zsh aliases

A zsh theme and plugin manager based on Antigen, Oh My ZSH, and Bash-it

This Bash script contains Oh-My-Zsh With, command autosuggestion, syntax highlight plugins and terminal header with own name for TERMUX.

LinuxConfiguration aims for a better user experience when you use a pure bash environment, which includes the zsh(oh-my-zsh), tmux, vim....

Oh My UFTB is a next-generation interactive shell customization framework built for developers who want both power and style in their terminal. Inspired by Oh My Zsh, Bash-it, and Fish Shell, this project redefines the command-line experience by combining beauty, speed, and intelligence — all written with simplicity and full customization in mind.

A collection of xsh modules for various plugin managers and frameworks.

My helper functions for ~/.bashrc file