Jump to content

Community

KT Walrus

+Clients
  • Content Count

    1,191
  • Joined

  • Last visited

2 Followers

About KT Walrus

  • Rank
    Community Regular
  • Birthday 11/11/2014

Recent Profile Visitors

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

  1. I'd like to see IPS4 come with support for RoadRunner PHP Application Server.
  2. Don't want to use something like Sendgrid since I'm concerned enough about my users privacy to try not to add and 3rd party services that expose user activity to the 3rd party who does whatever they want to with personal data. I don't also use Google or even any IPS services (like the SPAM service) since I don't want 3rd parties to see any personal data for my users, if I can help it. BTW, I implemented a pretty good solution to this problem today: 2 app settings, one for debugging and one for archiving email with the following syntax: bcc=username@gmail.com,uid=*|<id1,id2,id3,...>,g=*|<gid1,gid2,...> a plugin in my app to check the primary recipient in an outgoing email message against either of these settings and adding the BCC if match Not much to it, but it should allow me to archive all outgoing emails to a dedicated gmail address and debug tracing to my real address on specific users outgoing emails when my site has real users and I need to track down an issue related to outgoing emails. BCC is great for routing email to private email INBOXes without exposing these addresses to the real recipients.
  3. Okay @bfarber. I trust you to focus on what is important to IPS. I don't think an activity log is all that intensive. After all, NGINX manages to log every HTTP request/response to its log files and no one complains how resource intensive that is. An IPS4 activity log would be no more server intensive that NGINX's access logs, and would be more useful to more clients than you might currently think. In the meantime, I've implemented a simple plugin in my app to append all \IPS\Log data to a file. I persist this file on my Docker host and to view the logs cluster wide or from my macbook, I have a little container simply 'tail -f' each php server's log file. This gets the data into Docker where there are plugins for handling/monitoring the container logs. I think it will work fine for error logging and for debug logging. And, activity logging should be easy to add if I spend a day or two to look into where to find this information perhaps session data since IPS4 updates session data with last activity info.
  4. Yes, I just thought that putting the logging into the core classes and not the app's classes is a better place to add logging. Like the DB classes (including ActiveRecords) could log all database activity (for a specific logging level where you want debug info in the logs) and at the controller level (when you want see activity logs generated) and in the Exception classes for error logging, etc.
  5. Then why does NGINX separate access logging and error logging? It is very very useful for even the "average Joe" to be able to monitor both easily with standard monitoring services (available to all for a small monthly fee if you don't have the inclination to do this DIY). Maybe I don't understand your reply? I am basically suggesting this except that logging should go to files (not database) where it is more easily processed and that we should be able to log everything, only separating errors and access logs like NGINX does. The logs from an app will be much more usable than the NGINX logs since they can be much more application specific. And, built in IPS4 logging can be better curated to produce better logs than I have time to implement myself for just my site.
  6. Great idea! I'm all for this one. Maybe even be able to create a Photos forum like IPS4 already supports Questions forums. Same goes for Video forums. It is always nice to see photos and videos presented nicely to all viewers in some specific forums. Attachments just shouldn't be limited to embedding in the post body at a user configurable size. I realize that Gallery is a good option for many sites, but some of us want discussions about specific photos to be inline in the forum topics.
  7. Good idea! I'll probably do this until IPS implements better logging through out the suite. As I wrote above, IPS4 really needs much better logging to monitor all user activity (like NGINX does for HTTP requests/responses). I really want to be able to trace all activity by all users (or a specific set of users) and not just activity that changes content. I want to be able to monitor when content is viewed as well. So, putting logging in the controllers, nodes, active records and other core classes is probably needed too for a better logging facility. Not just redirecting logs to a file. Maybe, I'll work on hooking into these classes as well to make logging more useful to me. But, I'd rather see IPS build in better logging so I don't have to invent my own.
  8. FWIW, I ended up using "+" addressing to my real email address (e.g., kevin+mary@gmail.com for the test user Mary) when I create test users. This delivers all email to my INBOX and tell me which test user got the message. But, this won't work well when my site is live and in production. So, @bfarber, maybe you could implement an ACP setting which is a stack of email addresses to BCC emails to and a filter for selecting the users/groups that the ACP uses for each BCC email address entered. The filter would direct the ACP on which BCC addresses to add to which outgoing message recipients. This would greatly help in production. I could define one "archive" gmail address to be BCC'ed on all outgoing emails, and only add another when I want to "monitor" the email for a specific user, list of users, or list of groups. The BCC'd INBOX will receive an exact copy of what the real recipient sees, so this would be a great feature for both archiving all outgoing messages and for tracking down a specific issue relating to emails to specific users.
  9. I think that now that running in Docker/Kubernetes containers is a real thing for many of your customers, we would appreciate if you could implement a more container friendly logging method. Even if it is logging to a single file, I could always direct the file to stdout so the logs are accessible using Docker logging methods. Saving logs away in a DB is just a pain. I can implement an agent to watch a database table, but that just is extra work. Here is how I redirect logging for my NGINX container: RUN mkdir -p /var/log/nginx && \ ln -sf /dev/stdout /var/log/nginx/access.log && \ ln -sf /dev/stderr /var/log/nginx/error.log NGINX is configured to log to the 2 files and I simply redirect those files to stdout and stderr, respectively. If IPS4 did that, it could have an ACP setting to log session activity to access.log that is easily digested to monitor our websites. The NGINX logs are so cluttered and only track users by IP that it is much harder to analyze how users are using my site. Good logging in IPS4 would really help most admins monitor for problems and optimize their sites for the best user experience possible. @bfarber Hope you reconsider your opinion that your customers don't want better logging in IPS4 and we are "best off with a plugin" and not a standard supported feature.
  10. I got two exceptions the other day when I went to uninstall Toolbox. I didn't keep the tracebacks but I think they were caused by removing "follows" using the a string ("toolbox") instead of an ID (integer type). Sorry I didn't think of reporting this at the time, but you might want to uninstall Toolbox and see if you get the same two exceptions. I simply commented out the SQL that was causing the issue since the follows table didn't have any rows in it to remove anyway.
  11. Thanks. I had thought of something similar months ago, but I don't develop for IPS that often and had forgotten all about that option (to use a email forwarding service). I have forgotten the name of this free forwarding service (and still don't remember), put they allowed you to simply point a domains MX DNS records to their email forwarding service, and redirect all email to there. Now that I think of it, I can probably easily configure Postfix on my server to forward all outgoing SMTP mail sent by IPS to forward to any email address I want. All I have to do is change the SMTP settings in the ACP to use this SMTP service and I should be good to go. Right now, I send all email using AWS SES SMTP, but the emails go to real addresses rather than fake ones.
  12. Thanks. I never thought to look in the footer. Now that I know, I'll probably remember this for next time I can't find it. Still a link in the Developer forums in the descriptions would be a more obvious place to look.. And, I still can't find it in the hamburger menu on mobile where you expect to find all navigation links. Maybe a link in this menu on mobile is warranted also?
  13. Thanks. I try this out. The only issue I have with dumping to the file system on the server is that I won't be able to view in HTML easily unless I download and import them into my email app somehow. Then I can simply click on any verification links or other user actions that might be taken from viewing this notification message in HTML. I suppose I could pipe them into the database and route them to a Support area to view them as HTML. Maybe the process of responding to simulated email is easier than I think. If not, I would request an extra switch to route them as a PM to the admin or forward them to my email address. I also thought of trying to make fake email address for my real email address by using a '+' in my real email address. Some mail services will allow delivery of username+fakename@gmail.com. Probably Gmail supports this and I can just register fake '+' addresses for each of my fake test users. Anyone else have any experience/advice at/for deploying to production and doing adequate testing in a staging environment before pushing to production?
  14. I'd like to see a Test Mode option in the ACP that I can enable, regardless of whether I am IN_DEV or not that causes all outgoing email messages to be sent as PMs to the Admin (or some other internal list). This new Test Mode might also enable other features that help testing a site before deployment. I've configured a bunch of dummy test users on my site (that isn't open for real user registration yet), and I don't want to have to make up real test email addresses for each user to receive notification and respond to them (like account verification emails). I suppose there might be another fix I can do when testing my site before deployment, but this one seems like the easiest solution to me at this time. I'm open to reading about any other ways people have tested their sites before deployment since I'm adding a bunch of user visible changes for my new site that will require thorough testing before opening the site to real users. There might be a better way that I just don't know about instead of adding a new feature in the ACP.
  15. My new site will require better logging method than just logging to the database. It would be better if IPS implemented "Logging Methods" (with several built-in methods) like the "Storage Methods" currently support built-in and user provided options for files managed by a storage extension. And, I'd like the option to collect more specific activity normally collected by IP in the web server logs that allows me to log all session activity to a "Logging Method". This session activity, like viewing content, or navigating to other pages would have the user ids associated with them in the logs so I can do full security audits from these logs without having to investigate the web server logs for suspicious account specific activity (the web server logs might be too hard to analyze on an account specific basis for logged in users).
×
×
  • Create New...