kengitahi

SOLVED! WORDPRESS ASKING FOR LOCAL FTP CREDENTIALS ON XAMPP

A few developers were asking why their localhost instances of WordPress were asking for FTP credentials when trying to install new plugins and themes. If you’re getting the dreaded “Please enter your FTP credentials” page and you’re running XAMPP for your local WP development environment, do not follow the popular StackOverflow answer that tells you to chown your wordpress folder to _www. Read more for the real fix.

There’s a Stackoverflow page that tells you to chown your local environment to www, but according to the <a href=“http://www.apachefriends.org/en/xampp-macosx.html” target=“blank”>recent XAMPP documentation, Apache is running as user ‘daemon.’

So the fix is to go into your Terminal and cd to your local directory. If you develop a lot of wordpress stuff at the same time, you can just chown your htdocs directory (remember that you should never use XAMPP as a production environment, which means you should never follow these ideas for live

kengitahi

10 Front-End Websites You Need To Know As A developer

HTML/CSS Templates

• https://templated.co/
• https://html5up.net/

Design Inspiration

• https://dribbble.com/
• https://www.behance.net/

kengitahi

10 Front-End Websites You Need To Know As A developer

HTML/CSS Templates

• https://templated.co/
• https://html5up.net/

Design Inspiration

• https://dribbble.com/
• https://www.behance.net/

kengitahi

//put your feed in post/page with
//[add_rss url = "my feed uri" 
//items = "number of items to retrieve" 
//title = "title for" 
//show_date = "show date or not" 
//show_author "show author or not" 
//show_summary = "whether to show a summary of each item"]
//declare the function
//from the original wp_widget_rss_output
//bit customized

kengitahi

set -gx PATH $PATH $HOME/.composer/vendor/bin or set -gx PATH $PATH $HOME/config/.composer/vendor/bin

set -U fish_user_paths $HOME/config/.composer/vendor/bin

Check the path after running composer global require "laravel/installer"

kengitahi

After installation
--------------------------
https://laravel-news.com/shouldbestrict


Packages
---------------
composer require --dev phpstan/phpstan (Code analysis, https://github.com/phpstan/phpstan)
composer require tightenco/duster --dev (Code analysis, https://github.com/tightenco/duster)
composer require rector/rector --dev (Code updates and refactoring, https://github.com/rectorphp/rector)

kengitahi

Set up GitHub Actions to handle deployments for your Laravel application. This has similar functionality to Laravel Forge without the recurring cost. GitHub Actions can be used to automate your deployment process on every push to your repository.

Prerequisites

1. Server Access: Ensure you have SSH access to your server where the Laravel app will be deployed.
2. Secrets: Store sensitive information such as your server's IP address, SSH username, and private SSH key in GitHub Secrets. Go to your GitHub repository, navigate to "Settings" > "Secrets and variables" > "Actions", and add the following secrets:
   • DEPLOY_SERVER_IP: Your server's IP address.
   • DEPLOY_SERVER_USER: Your SSH username.
   • DEPLOY_SERVER_KEY: Your private SSH key. Make sure this key is authorized to access your server (~/.ssh/authorized_keys).

• DEPLOY_SERVER_DIR: The directory where you'd like to deploy your app, relative to /var/www/. Ex: example.com