Laradock VS starter-workflows

Haven’t touched Laravel for years pero baka laradock might be good for your use case

This is a function of the apache configuration files. You should examine those and determine what the issue is, using the xampp gui which will let you edit the httpd.conf file, or whatever it is that xampp uses. xampp provides the default settings you need, so I highly doubt this is the issue, but there is a directive called DirectoryIndex that tells apache what files to search for when a url points to a directory. By default that is going to include index.php. So if that is not working, then there is possibly something else going on with the apache config. To figure this all out you really have to understand how the various possible configuration options work. I don't use xampp so I can't tell you with certainty what the defaults are, but directives like Directory, VirtualHost, DocumentRoot etc, can all be used and combined in different ways to create different outcomes. For example, whether or not an index even appears (in the absence of an index.php) is configurable, as is whether or not you can override settings in a .htaccess file. I'm guessing you might be running xampp under windows, and this is yet another reason why in the era of containers, it's just better to use virtualization or containerization rather than something like xampp. As it sounds like you are still in learning mode, it's not too late to turn your attention to something like docker with https://laradock.io/

It's vastly inferior to laradock and does less.

With https://laradock.io/ it should be no more than a couple of minutes. Yes, this is a development environment and not meant for production. But so is yours, just with a worse approach.

The prime example of what I'm referring to is: https://github.com/laradock/laradock

First, we will use Laravel Sail to run the application locally on our dev environment. There are unofficial Docker environments for Laravel like Laradock but Sail is the official docker dev environment for Laravel. Sail is is a wrapper on top of docker compose.

git clone https://github.com/Laradock/laradock.git

GitHub, as one of the leading web-based Git repository hosting service, provides a powerful suite of CI/CD tools in the form of GitHub Actions. These are directly integrated into the platform which empowers developers to increase the speed, efficiency and reliability of delivering products. In this brief article, we will take a look at what CI/CD is, why we should use it, as well as some of its applications in my projects.

GitHub Actions is a modern CI/CD tool integrated natively on GitHub. Itenables the rapid automation of build, test, deployment, and other custom workflows on GitHub with no need for external tools.

GitHub Actions is GitHub's CI/CD solution. You can use it to run automated tasks each time you change your code. Although the platform lacks a built-in Kubernetes integration, third-party plugins such as Azure's Deploy to Kubernetes Cluster action can automate deployments and manage different rollout strategies.

GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.

actions/starter-workflows

The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.

You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.

# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test

You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).