Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by pwired

  1. I will be glad if I am wrong and you guys are right that Docker Desktop is free for commercial use.

    I was reading from here:

    Docker Desktop may be used for free as part of a Docker Personal subscription for:
    -Personal use
    -Education and learning (as a student or instructor, either in an academic or professional environment)
    -Non-commercial open source projects

    So that means a Docker Personal subscription is needed, right ?

    -Personal use I understood as not commercial use but I must be wrong about that.


  2. Quote

    I had problems with laragon and the support is not great.

    So how is that ? They have lots of docs, articles and vids which you don't even need because it works out of the box
    and the interface is self explaining. With version 5.x they did a great job to make it work with php8.x
    Frameworks, Addons, libs, third party tools and features are conveniently bundled in one directory (c:/laragon/bin)
    e.g. easy switch between php5.x 7.x and 8.x for both old and new projects.

    By the way ... did someone mention that Docker Desktop is no longer free like it obvious was before ?
    I don't mean if you are running a company with 250+ employees

    If you develop closed source or proprietary software with Docker Desktop it requires a paid subscription for professional use.
    Selling Websites or Apps developed With Docker Desktop is commercial use and needs a Docker Pro license.

    The Docker engine is free without any hassle so linux might be the better choice of something like Lazydocker ?


  3. Quote

    Also the config of the project can be added to the project's git repo. That means everybody can just do a git pull && ddev start and will have a working version of the project with all the settings and tools needed for it to run. You can't do that with laragon.

    Thanks for posting. Yes I figured it has to do with this flexibility. Virtualbox and even Vmware are poor (bloated) virtual environments when it comes to dev. I tried Vagrant in the past but didn't like it. I already have linux on a second partition so I will try ddev or something like devilbox.

  4. Is DDEV "supposed to be" used on mac or linux ? On windows you need either wsl2 or the docker desktop. On windows, can anyone tell me why Laragon is not by far easier to use than DDEV when it comes to switching between php versions ? Is it about working in virtual environments ? With virtualbox it can just as well be extended, version controlled, and shared.

  5. I have been working with Drupal for a while just to find out if building a website "The Administrative Way" would speed up building websites
    compared to building websites "The Technical Way" with html, css, js and php.

    The thing with Drupal is that you have to work the Drupal system way with it's content types, articles, fields, blocks, entities, nodes and modules.
    With this you can make Drupal Websites without having to write code. Drupal is targeting non coders and with Drupal 9 it has improved
    on it's user-friendly interface for non-technical administrators.

    Drupal 7 was the most loved Drupal version and many Drupal users are against how Drupal 7 evolved into version 8 and now version 9.
    Drupal 8 was less accepted because of worse code readability, incompatible modules, spaghetti of files, far from logical, etc.

    What the community now hates to see ist that the Drupal that they have grown to love over the years,
    with Drupal 9 it is actually being steered towards "Enterprise".

    This is the reason that a group of Drupal coders have branched off from Drupal with the Backdrop cms, a Drupal fork.

    • Like 1
  6. Quote

    But is the replacement (CKEditor 5) the best path forward?

    Let's not forget that CKEditor has many (returning) forum posts/questions about it's behavior and associated hard to find configurations 

    Keep in mind that something like CKEditor5 will be just too much for many clients/end users/office workers/
    who are in need for a more easy and intuitive to use editor:



    • Like 1
  7. I simply resize the website from wide screen to mobile screen .... and then observe at what screen size ... it looks both practically and visually good ... to change from default menu to hamburger menu. This is not so easy done with a fixed set of breakpoints in e.g. bootstrap. But this is very easy done with e.g. something like pocketgrid css where you are totally free to set any breakpoint at any screen size where you want a change to happen in the look and feel of the website.

  8. Quote

    And I have had such a great idea yesterday, I almost can't believe it myself ? It solves all those weird scaling issues and makes it possible to scale any css rule that has a numeric value, like font-size, border, padding/margin, border-radius etc...


    Will the scaling also work for images and html5 videos ? Hope to see more of this $rockfrontend growMin .... growMax ....

  9. Quote

    I get the impression that we're missing a "proper" tutorial here. In my opinion, what we have here are bits and bytes that are out of date. It would be nice to have a "complete" and updated tutorial on how to build a "real" website. What are your opinions?

    There are dozens of quality tutorials and Processwire strategies explained under the Processwire Docs and then there are dozens of more very good tutorials on the internet. So either you are disconnected from Processwire reality or don't know how to use Google. But usually the real issue is that Processwire has unlimited power and freedom under the hood, confusing old habits of making websites. Dive in the Processwire api and make websites with it and many of the questions will melt away. We are here to help you go along.

  10. I don't really bother because I use the pocketgrid css, which works with free to choose unlimited columns and free to choose unlimited breakpoints and blocks. I resize a website from wide screen to mobile screen and simply set breakpoints only where they are needed to resize a font, picture, margin, padding, etc, etc to make it look good. Contrary to something like Bootstrap would be very difficult because Bootstrap and the likes work with a limited set predefined breakpoints.

    • Like 1
  11. For a long time I dived directly in templates and code to build a website.
    I changed that old workflow and use prototyping and wireframing a website
    first in Lunacy and Pencil. Only after that I port it to processwire code.

    • Like 3
  12. In general:
    Apache servers are case sensitive. A request for /directory/file will be treated as a request for a different file
    than one for /Directory/File.

    Search engine’s are case sensitive. They’re going to view /directory/file and /Directory/File as the locations
    of two different documents

    In processwire:


    • Like 4
  13. It is no secret that Wordpress attracs a lot of no-coders and low-coders because of it's available template market. The no-coder buys a template on envato, themeforest, templatemonster, etc. and sells it as a website to the client. Most of the clients don't even know they bought an envato template website because they have no time and no website experience. By the time the client needs to have something changed, the wordpress template limitations won't allow for it and the no-coder is long gone selling a template somewhere else. Sooner a later the client is forced to call for a real coder for the needed level of support. Pagebuilders will attract even more no-coders and low coders. Having followed the Pagebuilder scene in Wordpress with Beaver, Bakery, Brizy, VisualComposer, Elementor, Genesis, Gutenberg, Themify, Divi, Oxygen, GeneratePress .... the list goes on and on. There is almost every month a new Wordpress Pagebuilder on the block. Why spend time in learning the Pagebuilder of the day if you could spend that same time in learning html, js, css and php and never need a Pagebuilder in the first place and give the Client a website that he really deserves: without Template limitations, unused theme functions and without all the Pagebuilder bloated code. Coming to my point: I hope that what is happening in the Wordpress Pagebuilder scene will never happen with future Processwire Pagebuilders.

    • Like 5
  • Create New...