Jump to content

clsource

Members
  • Posts

    374
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by clsource

  1. processwire is love processwire is life
  2. Yes you can do version control with git using processwire (I recommend gitlab in order to host the code https://gitlab.com/ ) https://processwire.com/talk/topic/7441-using-git-instead-of-ftp-in-shared-hostings/ But version controlling a database is something I do not have experience. A quick search drops this result http://programmers.stackexchange.com/questions/241109/is-backing-up-a-mysql-database-in-git-a-good-idea Maybe you can go and make a database dump and git control that file. and using git anex https://git-annex.branchable.com/ in order to keep large files.
  3. I have used Mandrill in a PW project before using the PHP Client. https://mandrillapp.com/api/docs/index.php.html Straight foward and easy to implement. I didn't use the stmp because I was using Mandrill templates and filling the placeholders with user data.
  4. Thanks @mosid and @gebeer. Yes making a module should not be difficult. Anyway sometime ago I tried to including in the core. here's a repo with the PW fork that have Rest included. (its outdated) https://github.com/clsource/ProcessWire/tree/dev
  5. Ah yeah pretty much PW will be a perfect fit. Those games are just traditional websites with a "gaming" purpose. I recommend making the backend with PW and the front end with angular js, ember or similar.
  6. Thanks I mainly use gitlab.com but know there are more alternatives to github or bitbucket is really helpful too
  7. Uploading images vía put is a special edge case. See here http://stackoverflow.com/questions/12340720/how-to-upload-files-using-put-instead-of-post-with-php so You should use fopen(php://input) instead of the common method. Only using post and get is possible when You desing an api for clients that not support put and delete.
  8. So far so good . for the command wireshell backup:db I suggest renaming it to db:backup so for example if you implement a db replace or db merge command in the future. the command will became. db:backup // Dumps an entire db db:replace // Delete existing db and replace it with a backed one db:merge // Merge the existing db with the data from a backed one Again thanks for the great work.
  9. Yes I Use Git a Lot. Try to follow a flow for keeping things in order. Here´s a good read https://about.gitlab.com/2014/09/29/gitlab-flow/
  10. Here are some links that I found relevant to REST and Microservices architecture http://www.slideshare.net/stonse/pros-and-cons-of-a-microservices-architecture-talk-at-aws-reinvent http://www.infoq.com/news/2015/03/benefits-microservices http://www.infoq.com/presentations/rest-misconceptions
  11. Normally using $this is for modules only. Inside templates you should use wire() methods you can also get the object via the $event var. wire()->addHookBefore('Session::logout', null, 'logoutNoCookie'); function logoutNoCookie(HookEvent $event) { $hookObject = $event->object; } See also http://processwire.com/apigen/class-HookEvent.html https://processwire.com/talk/topic/4701-add-hook-in-a-template/ https://processwire.com/api/hooks/#all_or_one http://www.flamingruby.com/blog/using-hooks-to-alter-default-behavior-of-processwire/ Cheers
  12. I don´t know well how PW handles cookies and sessions. maybe this link should do the trick http://stackoverflow.com/questions/1773386/how-to-suppress-remove-php-session-cookie or this http://php.net/manual/es/function.header-remove.php
  13. Wow thanks for using this code and thanks for improving it. Well A technique I use for avoid using sessions is a token and send that token with every request. I previously created a "token" field inside the user page. So when the user logs in a token (normally sha1) is created and saved to his token field. So for example you made a login request and the backend responds with this data. { "status" : "ok", "data" : { "id" : 142, "username" : "clsource", "name: "Camilo", "token": "abc123" } } And then you need to update its name sending a PUT request to the corresponding endpoint PUT { name : Camilo C. } https://api.example.com/v1/users/{token}/profile/name in this case {token} would be "abc123" As the token is saved in the user page you can check if the user exists quering by the token $usr = $users->get("token=$token"); As you may notice the token gives you access for seeing and modifying the user, so its better to keep it safe. A rule of thumb is creating a token with a 1 hour valid time. And when the token is invalid you should request a new one in background. Hope it helps
  14. This is wonderfull news!! Im looking foward what processwire tutorials they are going to do
  15. Maybe they like fedoras, like Indiana Jones xdd +1, Vista Yosemite ? xdd
  16. As some may now, the admins on tuts plus declined making a course on processwire :C Here´s the link http://tutsplus.uservoice.com/forums/248750-what-would-you-like-to-learn/suggestions/6769150-using-processwire-for-web-development So, Maybe we should make our own course?. I found this website for making such courses. https://usefedora.com/ I hope someday, more people will know the joy of processwire
  17. clsource

    GitLab Flow

    Hello folks, I was working on different projects and needed to have a better way to organize my code and a workflow. And I came across this methodology https://about.gitlab.com/2014/09/29/gitlab-flow/ Here's a video explaining the workflow Hope it helps
  18. Hey Happy new Year Everyone! Hope that all your wishes and PW related ones comes true
  19. I don´t know if this if off topic but here´s a request for tut plus. So they make a course on processwire. https://tutsplus.uservoice.com/forums/248750-suggest-a-tuts-course/suggestions/6769150-using-processwire-for-web-development
  20. Yes I think that too. without Ryan's approval this is just a silly (but fun) game. May be he don't want to use nicknames at all xd.
×
×
  • Create New...