I completely agree there's room for improvement in cross-interacting with applications across the suite. I think Gallery media should be available throughout the suite and that's something we'd like to work on. I'm not sure I understand the need for attachments to be duplicated in the Gallery, however, so perhaps you could help me better understand your goals. I'm curious why, in the case of a "see you" forum, you wouldn't just use the Gallery app for that... perhaps add a redirect forum or menu item if you're wanting it to be accessible in the forums app. That's really the purpose of the Gallery, so I'd like to understand why you're using the Forums for that purpose and essentially wanting to replicate content... perhaps there's something more we need to do with Gallery? Improve the interaction capabilities (one thing that came up recently is comments in the lightbox, for example), etc.
I do get the gist of what you're looking for, I'm just trying to understand why so we can step further back and evaluate to best fill the need.
We have some cool ideas for the AS that we think should solve most of your concerns, including those mentioned here. On the fly filtering may be one thing. We're not going to do pagination (as in navigate to page 4) as it just doesn't fit technically into the backend of the content discovery module.... but, we are working on navigation and you will be able to click a topic in the stream, hit back and pick up where you left off. I get the sense that's what most want with "pagination" so we'll start there.
That's not months out by any means and should be relatively soon. Virtually any example given regarding "it doesn't do what VNC did" has been successfully refuted. It is every bit as powerful as VNC and then some - I think there's just general confusion on how to use it to its full potential and we need to make a few improvements to make it more intuitive.
Thanks for the tangible, bullet list feedback - it's very helpful.
Well, I've seen quite a few requests for help in this forum now and I thought I'd gather a number of tools you can use to report your status. This will help others help you faster. :D That and additional ability to help yourself as well.
Helpful information The following are information that's often crucial to diagnosing problems. What is the environment you are running your website from?
IPB Hosting / Shared hosting / VPS / Cloud / Dedicated Server?
If VPS/Cloud/Dedi, what are your cpu, ram and disk availability?
Tools The following are tools you can run in order to gather further data. These can be run from ssh and is only accessible for vps, cloud and dedicated servers for linux distributions.
top - Top processes (very useful for any scenario) | top is usually available in all linux OS distros by default.
top (this will constantly output your server's general status as well as top processes, default in CPU usage order)
top n -1 (same as above, but will output your first stat instead of constant loop)
If you'd like more colourful version. There is also htop (usually not available by default. Can get here: http://htop.sourceforge.net/ or rpmforge )
iostat - Input/Output Statistics (very useful in diagnosing disk usage) | iostat is part of sysstat package.
iostat (this will output general stats regarding IO)
iostat -x 10 5 (this will output extra information for 5 times total with 10 second intervals. First stat is always "since boot" and after is since last report)
sar - System Activity Reporter (Displays system performance over time) | sar is part of sysstat package
sar
mpstat - Multiprocessor Usage (Displays system stats in relative to CPU) | mpstat is part of sysstat package
mpstat
Apache Status (Outputs the apache status) | apachectl status, as name suggests requres apache to get the stats. You will also need to have a shell browser to run.
apachectl status (This outputs the simplified current status)
apachectl fullstatus (This outputs the detailed current status. Please be warned that this will list all users and their requests. So, you will want to remove any IP address and further private information)
Connections
netstat -an | grep :80 | wc -l (This lets us know how many people are connected to your server on port 80 [http])
Uptime (How long you've been up)
uptime
vmstat - virtual memory statistics (This is actually not related to virtualization. This is about your swap)
vmstat
free (Shows your memory statistics)
free
free -m (In megabytes)
free -g (In gigabytes)
beancounters (Shows your limits) | Only for those with VPS/Cloud systems
cat /proc/user_beancounters
ifstat (Gives live information about network usage on each network interface)
ifstat
iftop (Similar to ifstat, but per user and top behavior)
iftop
mysqltuner (Gives information and suggestions about your current mysql configuration) | Available at below address
Available at: http://mysqltuner.pl/
You can run the mysqltuner with perl (chmod to 755 and run or call with perl) and type in your administrative mysql user id/pass.
mysqlmymon
Available at: http://mysqlmymon.com/
Similar to mysqltuner, but lot more information about everything else too! This is mostly meant to serve as an all-in-one tool.
MySQL Workbench
http://www.mysql.com...ucts/workbench/
This is a GUI tool that helps you administer, diagnose and plan.
(Complete) Monitoring Solutions
Nagios (Everything - heavy learning curve)
http://www.nagios.org/
Cacti (Network)
http://www.cacti.net/
vnstat (Much more simple network usage logger)
http://humdi.net/vnstat/
Useful to Know Settings
MySQL settings | Only if you have mysql
The settings are often found at:
/etc/my.cnf
Outputting your current information will help others identify problems.
Apache/HTTPD settings | Only if you have apache
The settings are often found at:
/etc/httpd/conf.d/httpd.conf
If you have WHM/cPanel, please look inside WHM instead.
Outputting your current information will help others identify problems.
Nginx Settings | Only if you have nginx
The settings are often found at:
/etc/nginx/nginx.conf
Outputting your current information will help others identify problems.
PHP Information (information regarding your current php build) | Available only to PHP users... for obvious reasons.
To get full php information, there are 2 easy ways. One, make a php file with the below contents and save.
