Jump to content

Jim Bailie

  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jim Bailie's Achievements

Jr. Member

Jr. Member (3/6)



  1. I'm sorry I don't have any silver bullets, but I've been through this on a development machine and from what I remember, it came down to permissions/config files along with netplan and how I accessed the apps via nginx.conf (i.e server_name). For development, I've always used IP aliases in /etc/network/interfaces a'la ifupdown and set my nginx server blocks to listen to such IP addresses. Netplan doesn't allow this. It says it does, but I don't feel like writing a PhD thesis to get it to work, so I removed netplan and replaced it with ifupdown. I'm not telling you to do this! I did it because I understood the problem and just wanted to use the network stack like I always have.
  2. Do all of your user/groups/permissions line up throughout your config files (nginx/php/php-fpm)? Are these all stock apt-get installs? And the new Debian based distos are using that goofy netplan s%#t. Is that working as advertised?
  3. I had a similar situation a while back, but this thread helped...can't remember any details except that there was a permissions issue in the app's directory structure
  4. Yeah, coming from several applications written from scratch, with codeigniter, and to a lesser extent, wordpress, workflow with Processwire has been tough for me personally, but I am adapting. I've sort of settled into a pattern where after having deployed the initial production application, I try to do as much non-destructive work as possible on this instance. If something may be destructive, then I'll clone the codebase and hit the same database and work on this. If and when everything looks good, I'll just point the DNS to this instance. You can read up on multi-instancing. The reason for the above approach is because with the app I'm working on, the DB is too big to be slinging back and forth to a development machine. Having said all this, while I'm working on production and staging instances, I've also got a half dozen R&D instances on my dev machine than are pretty darn close in structure to production. This all probably sounds nebulous and I hope it helps. And I would certainly keep search-engine'ing things like "processwire development staging production"
  5. Yeah, I am eager to use ProCache. After having built some fairly complex caching functionality with Nginx/Openresty/Lua for a high traffic, public facing site, it would be nice just to let the framework take care of most of the heavy lifting. Most of my work now is for internal CRUD and content management, but as soon as we get an opportunity to build something public facing with PW, we'll whip out the credit card 🙂
  6. Hello - I'm going to buy profields later today or tomorrow, but does anyone know if it ships with a site sample are other examples? I've searched and it seems like usage examples are pretty few and far between. Thanks!
  7. @horst Yeah, I just went and reread the ProFields page which I should have done earlier. I'll probably need to resurrect this thread later, but I think I have enough of plan now to start experimenting. Thanks again for the reinforcement!
  8. @horst Url segments look like they're pretty easy to manage and a date and date-created field will serve as an index so to speak. @monchu Yes! I think a single, uniform, parse-able url segment is the best approach. I know the client wants the urls to look like what's in the initial post, but that seems hokey to me. Now here's a follow-up question: 50+ document templates with 5-40 fields each is going to add up to A LOT of fields...even if a good handful of them will be shared. Does ProFields offer a way to "consolidate" these fields without adding too many tables to the DB? It seems like it would...
  9. Hello All, I would like to accomplish this the PW way, but again, I'm struggling conceptually and don't want to burn days experimenting. So now the people signing the checks want users to be able generate dynamic documents. There are 50-70 documents to chose from and they all will have between 5 and 40 fields...and they need to create multiple versions of each document...repeatedly. /john/2019/6/28/tpr-report/v1/ /john/2019/6/28/tpr-report/v2/ /john/2019/6/28/tpr-report/final/ /john/2019/6/28/stfu-report/v1/ /john/2019/6/30/stfu-report/v2/ /john/2019/6/30/stfu-report/final/ /mary/2019/6/29/wth-summation/final/ /mary/2019/6/29/tpr-report/v1/ What I do know is that I will need ProFields and will be purchasing that. I also know that the reports will need to be their own templates...but the dates and the versioning are the problem for me. Thank you in advance for any guidance! P.S. Would one of the blogging modules be a good fit?
  10. @Gideon So Yeah, it looks like that will work. It also looks like Text Blocks in ProFields could accomplish this as well. But it would be nice just to have a simple a dropdown for editors to select the block. Ok, now I have a starting point. Thanks!
  11. Hello All, Can we pick this thread up again? What if I wanted to have a dropdown box of choices linking to 30-40 static content blocks for page editors to populate in a certain region of a given template. What would be the best approach? That's my chief complaint about PW. Everything works so efficiently, that I'm always afraid I'm missing the most efficient way to do things.
  12. @BitPoet What a terrific write-up. Thanks! You've helped validate a lot of places my mind is going for this project.
  13. Hello, So we're wrapping up an internal application using PW. We have about 6500+ pages in so far and 14 fields. It's a pretty vanilla setup. We've got a lot of positive feedback, etc. Now this app is getting a little more notice than we previously thought and there's interest in merging another application with it. This legacy application has a well established database that will serve the new PW pages very well, but I couldn't, in good conscience, try to convert it to the "Processwire Way". So I'm curious to hear any stories or anecdotes about how others may have legacy DB's working with new PW apps. Are you using two or more db's? Have you folded existing tables into the PW db? I hope this question isn't too nebulous.
  14. @dragan Thanks for your help! I'll look for a hook and do this as a module then.
  15. This is sort of the essence of what I'm dealing with, but there are some legacy routing and session details that need to be dealt with. And I think I have the solution now! A vast majority of the requests will be satisfied by the PW app. Why not just put all this redirect logic into a PW 404 template?? Would you agree?
  • Create New...