Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by JeevanisM

  1. 21 hours ago, LostKobrakai said:

    Imo the most important part missing in conversations about one language vs. the other is context. Just using features for comparison is useful mostly to fanboys. One needs to look at existing knowledge, time to learn, amount of benefit from the learned language (short term and long term), team dynamics (hiring, on-boarding, finding devs already fluent), existing code, …. There's a reason there's so much PHP written for things objectively much simpler done in other languages – because all the above things often outweigh changing away from PHP. Like everything async/stateful (even just websockets) is a pain in the ass in php, because the common way to deploy php is stateless. Does that stop people from doing that with PHP? Nope, people take on a bunch of complexity to do it even with languages/runtimes out there much more suited to the task.

    Take the leap from webdev to ML and the context is completely different.

    Suddenly things like existing code don't exist anymore, ML is "new". ML needs to be learned anyway, so existing PHP knowledge is vain. Other people mostly use python for ML, so it makes sense to use them. Short term there's a clear benefit in moving to python for ML.

    The same should apply to green field projects, but what today is actually properly green field (including team knowledge and such).

    very logical analysis -  different tools for different uses

  2. On 9/5/2020 at 12:05 PM, pwired said:

    On the job market I see a lot of junior and senior php coders wanted. I see hardly anything about python coders wanted.

    I have the assumption that Python Dev is heavily wanted 🙂 my bad . For last 2 years I wanted to learn Python/Django but it seems a lot hurdles. I lost interest at very first time with their Server Setup. In PHP the LAMP Server is super easy to setup for Python, they need some kind of extra steps. The I got confused if PHP can do everything what Python can ( atleast in Web/internet context  ) , whats the point of switching to Python/Django ? 🙂 I have gone through numerous articles about Python vs PHP, mostly Python+ opinions but still  after 2 years, I am with PHP  !sure should I learn Python or Not. 

  3. On 9/1/2020 at 1:02 PM, LostKobrakai said:

    If you have highly variable load I'd suggest going with something like heroku for manual scaling (if planable) or even solutions, which can automatically scale. No need to run a super beefy server for a whole month if only a single day has actual load. 25k/hour is around 7req/s (likely higher for varying load over the duration of the hour), so either requests must be served in <1/7s or you need more server instances.

    yes that right,  I will check the options you provided . thankx 

  4. On 9/2/2020 at 3:53 PM, AndZyk said:

    Sorry, if I didn't understand your case, but if you are looking for a survey tool I can recommend LimeSurvey.

    Of course you could do this with ProcessWire, but a survey tool has most of your points already covered. 😉

    thanks for the reply, but not a Survey, its just an online examination but after reading your comment, seems like  a Survey and a Multiple choice exam look alike 🙂

  5. 15 hours ago, Sergio said:

    25,000 per hour/day/week? It all depends.

    From what you described about the app, even 25k users a day should be fine to start with a VPS with 2GB of RAM. If its usage increase a lot you can move the database to another VPS on its own AND/OR increase the VPS CPU and RAM resources very quick.  

    My advice is to keep things simple and not try to over-engineer the application performance from the start. But if you feel "adventurous" 🙂 or think that the project will have this many users right away on day one (which I doubt) you can start with a "serverless" approach where the infrastructure is scaled on-demand, using https://vapor.laravel.com/ and you don't have to worry. There's a course about this approach that is very interesting: https://serverlesslaravelcourse.com/

    //25,000 per hour/day/week?//  This will happen at  particular date  from 10 AM to 11AM only. This will not happen everyday, only  once in a month or so 

  6. On 8/30/2020 at 3:23 PM, Sergio said:

    Although doable, I'd only recommend a system like this to be implemented using ProcessWire if the rest of the project must, or already is, be highly coupled with PW and it doesn't make sense to decouple it for whatever reason. Otherwise I'd recommend you to implement it using another framework. PW shines in the content management part, and I love it, but it may present you with some limitations in it's developer-experience department when you need to implement some business logic that relies heavily on integration of payment systems, user data input, generation of reports and especially tests. There's also a myriad of similar systems like this already implemented that you can use as a base, like this one https://github.com/LaravelDaily/Laravel-Test-Result-PDF (demo: https://www.youtube.com/watch?v=GmLFHGud7I8). 

    thanx for the input, I was thinking about the Laravel  first but wanted to ask some expert opinion 

  7. Hello friends,

    Got a new project inquiry, the general requirements as below - 

    • Website Type - Online Examination 
    • Questions - Multiple choice Question with one selection for answer 
    • Expected Attendees - 25,000 students 
    • Registration required ( with OTP for confirmation ) with Online Payment mode 
    • After the exam, a student can see the score with results 
    • Admin - various type of lists (  highest mark scored students, categories of percentage etc ) 

    Now, I have a doubt, what kind of Server hosting I should suggest to my client ? Is this 25,000 at a time very high load ? I dont know much about the server load / bandwidth .

    As like that, the requirement, is Processwire a suitable tool to achieve the goal ? if so, what are the modules, I should use, or a general structure / approach ? 


    thank you




    • Like 1

  8. I was reading this article about JAMstack.  Consider a NewMagazine website, a person A would search for articles tagged 'sports' then it should do some DB queries, same time person B would search for article 'politics' then again the DB queries should work. This is conventional CMS work flow. So from the article I understand, JAMstack will generate all kind of possible  DBqueries and save it as a static way for one time only then it will provide the Static HTML . Is my understanding correct ? 



    JAMstack is faster

    Picture a CMS-based solution. For every visitor, the web app would have to generate a number of backend database queries to gather the information needed to generate a web page and send it back to the user.

    With a JAMstack app, you serve generated HTML instead of rendering documents live on the server. This ensures faster loading times, reduces security risks and is a solution that is easy to integrate with a CDN.



  9. 15 hours ago, teppo said:

    When I started working professionally on web projects...

    (don't you just love when folks start with that? "oh man, it's going to be another rant!")

    ... some of the first CMS' I had the pleasure to work with were kind of "static site generators": they generated static HTML files when you saved the content, and if your site had subdirectories, those were literal directories on the disk with more HTML files in them. I believe this was in part because server-side rendering back then was pretty darn slow and clunky, but also because it was easier to build a clean site structure with actual directories filled with static HTML files.

    "Dynamic" features, comment forms, polls, and whatnot were not quite as important back then, mind you.

    Now, I get that modern SSG's are a different beast in many ways, and I think they're actually pretty rad. What bugs me, though, is the amount of marketing bullsh... uhm, opinionated information floating around. Things like this gem from the staticgen.com website (emphasis added):

    I mean... how is this what a "typical CMS driven website" looks like? Any half-decent CMS' has built-in caching support, at least to some extent, and caching plugins regularly pop up amongst those lists of most popular plugins for platform X. You don't need to be a rocket scientist to figure out that running a server-side rendered, CMS generated website with no caching whatsoever is a Very Bad Idea™. Comparisons like this may make the SSG approach sound good, but they've also got very little to do with how things actually work.

    Without hopefully being too blunt, I don't think this is necessarily the best question to ask.

    If you define SSG as an application that reads markdown files from disk and generates a static site from those (that's one of the first definitions that comes up if you search for the term) then I don't see this as a solution most of us could push to our clients. At least not unless the site in question is a static one that doesn't need to update too often, and/or you can convince the client to pay you for each modification on a case-by-case basis.

    On the other hand if you think of an SSG as something that generates static site from dynamic content managed by some piece of software, well... that software you use to generate the content for the SSG? That's a CMS. It may be a headless CMS, but a CMS nevertheless 🙂

    I'm also going to agree with @MoritzLost on the point that ProcessWire + ProCache is indeed a kind of an SSG. Keeping a few potential pitfalls in mind one could definitely use this combination to build a site that pre-renders the whole site and thus doesn't depend on request time server-side rendering.

    The web is full of interesting tech: headless CMS', static site generators, APIs, and whatnot. While the "best" choice depends on the use case — you would have to consider the pros vs. cons and figure out what's best for each particular project, client, and team — in my opinion it's also rarely all that important. Websites are created for end users and end users don't care what you're running the site on — as long as it works, serves their needs, is fast (enough), etc.

    ... and you can get that with any platform 🙂

    Sorry, that last part was a bit off-topic. Overall the SSG market is well worth keeping tabs on. Personally I tend to lean on the "dynamic CMS generated content rendered server-side with efficient caching policy" approach, but that's mostly because I feel it makes sense for the kind of projects and clients I tend to work with. Pros and cons 🤷‍♂️

    To be honest, I guess you will be an awesome journalist or a/an writer/author in literature 🙂

    • Thanks 1

  10. 22 hours ago, MoritzLost said:

    Static site generators will probably be 'the next big thing'. You get way better performance and security by default than you could have with any CMS by definition. Which doesn't mean that you can't have dynamic content like comments, e-commerce etc. But instead of bundling that functionality, you're using external services, APIs, serverless functions and build automation to persist data and trigger builds whenever something changes. I'd recommend reading the Jamstack book (created by the Netlify people), you can get the ebook for free and it explains all the concepts related to SSG.

    By the way, you don't need NodeJS / NPM to have a static site generator. Though many SSG are built with JavaScript, they use NodeJS only as a runtime for the build step, not as an actual server. But there are SSG written in all kinds of languages - check out this site if you want to find one you like. One could argue, by the way, that the ProCache module for ProcessWire is also kind of a SSG generator, even though it works a bit differently than most tools on that list.

    My current recommendation is eleventy, I'm currently rebuilding a couple of my own sites as well as a ProcessWire-related project that I might release soon with it 🙂

    thanks for the detailed explanation 

  11. HI, 

    I have done a few E-commerce projects in OpenCart, which really suitable for the mid-size E-commerce platform. I have tried Magento once but never get a knack on it. I tried to use ProcessWire for the E-Commerce but I realised I have to do a lot of custom coding which I am not that much expert. So I use different tools for different purposes, for any CMS related WEBSITE/WEBAPPS - ProcessWire is a rockstar for me. But for e-commerce I would go for OpenCart 

    • Like 1

  12. On 3/31/2020 at 10:27 PM, fruid said:

    so I need to code the template as php and html after all? I thought it was supposed to be easy to use.
    And after coding the template and all I still need to select the fields that I want to add to the template in the admin panel after all? Isn't that redundant?

    It is not redundant, its actually the processwire way to give extra control to the developer on the pages and code.  

  13. Hello,

    I would like to report a tiny bug in the latest dev branch of PW. I downloaded the dev zip file from here : and tried to install. Everything went fine but hit the error message as in the screenshot. processwirecalhost.png.9db3fde4af2d620cb4ef5fc6df41426d.png








    So its says there is an unexpected * in the site/config.php file. I checked the file and found that it supposed to be a comment actually but somehow, the position of  '/' is wrong to make the comment '/* ' .




    Hence I manually edited the file and went to installation but the error repeated in different line once I passed the admin password setup page. So the PW installer is writing the site/config.php file with newly updated DBinfo. So I manually edited the site/config.php file before click the DB  configuration section, next time. It passed and installation finished. But I think this is somehow a bug ? I dont know, just notifying it here.

    another thing I noticed that - the button says the version 3.0.162 but the downloaded zip installed admin shows ProcessWire 3.0.163 dev © 2020


    • Like 4
  • Create New...