Back to Blog
Laravel pint7/24/2023 ![]() And then there's security.ĩ6% of the websites hacked are running WordPress ( source). Oh, and all those features that don't come with WordPress? They're all included in Statamic core. We're not in the data business, and we keep as little of it as we can. When software is free, you are the product. In most cases you can run Statamic on a $5/mo Digital Ocean server, or deploy a static site to Vercel or Netlify for free.īy paying for software, your money goes directly towards supporting and improving it. Statamic costs $259, one time.Īfter that it's just an optional $59/year whenever you want updates and access to direct support from the team who built it. Not to mention having to keep track of updates, billing, and customer support with a half dozen (or more) different companies. Add Advanced Custom Fields for $49/year, a backup solution for $200/year, a forms module for $349/year, a search plugin for $149/yr, and premium "managed" WordPress hosting, and before you know it you've committed to over $1,000/year just to keep the site online. You'll need to buy Jetpack for $99/year because after all, it's "essential". With WordPress you'll probably need to buy a premium theme and hire a developer to customize it, who might tell you last minute that what you're trying to do isn't possible with the "page builder" you're using and you'll need to switch to another theme and start over. ![]() We'll explain how Statamic saves you money, keeps you safer, and makes changes faster than any other CMS. If you’re looking to just plop a generic theme on the internet and replace placeholder text with your company name and phone number, then maybe you should just use WordPress.īut if you're looking to build and maintain a website that can adapt the way your business adapts, keep reading. No, after every push I see pint's commit:Īnd when I click on the commit, I see a diff with the changes made by Pint.When it seems like everyone else is using WordPress, why use anything else? The full action / code now look like this: name : Check & fix styling on : jobs : phplint : name : Laravel Pint runs - on : ubuntu - latest steps : - uses : actions / checkout v3 with : fetch - depth : 2 - name : Laravel Pint uses : aglipanci / laravel - pint - action 2.0.0 with : preset : laravel configPath : "pint.json" pintVersion : 1.2 - name : Commit changes uses : stefanzweifel / git - auto - commit - action v4 with : commit_message : Fixing styling skip_fetch : true Great! So I now have Laravel Pint running and linting my code and then push it back to my branch so I can also see a diff with the changes and can now make sure that all of the code in my main branch is following laravel Pint rules. name : Commit changes uses : stefanzweifel / git - auto - commit - action v4 with : commit_message : Fixing styling skip_fetch : true In order for me to achieve such behaviour I also have to use a git-auto-commit action. What we really want is Github to also make the suggested changes and push them automatically to our branch as a new commit. So far so good! However, the action above will only notify us about potential code formating issues. The pint.json file in the root of my laravel project will be used for configuration during the run of the Action. ![]() I have personally been using Github actions with aglipanci/laravel-pint-action and it works great! name : Check & fix styling on : jobs : phplint : name : Laravel Pint runs - on : ubuntu - latest steps : - uses : actions / checkout v3 with : fetch - depth : 2 - name : Laravel Pint uses : aglipanci / laravel - pint - action 2.0.0 with : preset : laravel configPath : "pint.json" pintVersion : 1.2 ![]() Inside the workflows folder is where I place my actions as. github/workflows/pint.yml at the top of my repo. Instead of always running PHP CS Fixer or Laravel Pint locally, it might be a good idea to set up a GitHub action, that will reformat the code in Github following the laravel Pint formatting rules after each push.
0 Comments
Read More
Leave a Reply. |