• Content count

  • Joined

  • Last visited

Community Reputation

94 Excellent

About joer80

  • Rank
    Sr. Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Texarkana, TX

Recent Profile Visitors

2,841 profile views
  1. As a quick patch this fixes the error: Change this: $a[trim($cropItems[1])] = trim($cropItems[0]); To this: if(count($cropItems) > 1){ $a[trim($cropItems[1])] = trim($cropItems[0]); }
  2. Very nice! I am going to do something similar on my next project!
  3. A page tree is very flexible, but I think sometimes users want to be guided more. I think the task based dashboard is the way to go as the default view in my situation. I would be interested in screenshots of any dashboards you have done in the past if you have any you an show!
  4. Icons is another good idea to make the main types stand out. Thanks!
  5. Maybe the best way to accomplish this layout would be to allow the "Pages" page to the be the home root, and the other top level types could be top level in appearance only. Just make a way to flag which pages should look top level when its building the page tree. Or better yet, maybe drop people off at a dashboard instead of the page tree with a layout similar to the above. That way I can organize it without messing with routing.
  6. Instead of putting Home at the top and all pages under home, is it possible to have Home on the same level as other pages? Or possible to have more than one top level page? See this example: Pages Home About Posts Blog Post Categories Category 1 Menus Top Bottom Media Photos Video Settings Location Website All bold pages would be top level pages with their own children. Thanks!
  7. I had to do this as well!
  8. I did some testing and it seems if I turn on PHP OPCache it hurts more than helps. Has anyone else noticed this?
  9. Its working now! I think the "npm --unsafe-perm" i did it!
  10. When I login as root and run npm i it says: npm WARN prefer global node-gyp@3.6.2 should be installed with -g > node-sass@4.5.3 install /home/goac/ > node scripts/install.js module.js:471 throw err; ^ Error: Cannot find module '/home/goac/websitehere/site/templates/client/node_modules/node-sass/scripts/install.js' at Function.Module._resolveFilename (module.js:469:15) at Function.Module._load (module.js:417:25) at Module.runMain (module.js:604:10) at run (bootstrap_node.js:389:7) at startup (bootstrap_node.js:149:9) at bootstrap_node.js:504:3 On Centos
  11. I get an error with a clean install when I run "npm i" Error: Cannot find module '/home/goac/mywebsitehere/site/templates/client/node_modules/node-sass/scripts/install.js' at Function.Module._resolveFilename (module.js:469:15)
  12. If you need more default throughput you could always mount user assets, modules and templates separately instead of the whole sites folder. I just did it for convenience. Local storage on each ec2 machine would be a bit quicker but you have to sync them somehow. Using their deploy tools is one way you can do it and push out updates without something like rsync. The wire files don't change that much so I don't mind doing a deploy for those. I just wanted sftp access to the templates to be able to make changes instantly as needed, instead of a versioned setup since I am the only dev and its faster for me. I guess you could always do a hybrid approach and do a deploy for template changes and efs for user assets. Another thing to consider is if you turn on their cdn to serve static assets, I would matter even less. Your EFS is just the authority/pull point.
  13. Limits page says efs has a default throughput of 3 Gigabytes per second each and you can request more. You can mount 10 and files are redundant across multiple Azs/datacenters. It can go to petabyte levels.
  14. No, both the rds and the efs are managed clusters.
  15. I ended up getting this working, but instead of doing the assets folder I did the whole sites folder. That way I could install a module and it go to all http servers. I also added my ec2-user to the webapp group so I could sftp into the share and edit files.