Jump to content

mr-fan

Members
  • Content Count

    837
  • Joined

  • Last visited

  • Days Won

    4

mr-fan last won the day on September 20 2018

mr-fan had the most liked content!

Community Reputation

939 Excellent

About mr-fan

  • Rank
    Hero Member

Profile Information

  • Gender
    Male
  • Location
    Bavaria, Near Munich

Recent Profile Visitors

7,968 profile views
  1. just a short update on this - i am stresstesting the PW way and i'm on the way yust with simple pages for now and see what comes up the road. made a crude script to get dummy data and created around 88k pages (DB are now 35MB) in very fast time on shared hosting...just for example to create 48 testrecords for every day (17260 pages - 2 records per hour) the scripts runs on in about 80 seconds...just for others that are search on create dummy content in a quick and dirty way i let my code here (if there are better ways - at least as a bad example..;) So far next things are to create a script that runs to build the averages of month, year for long term stats and then i will try how reporting and visualisation in an easy graph - works together with a DB that have around 90000 pages with just some integers and floats. I would first try how an easy to use chart library would work (https://gionkunz.github.io/chartist-js/index.html) Since this tools all use JSON data i think i could cache or better prepare this JSON strings for the charts and see how fast it performs...i'll report again. But this is an interesting experiment so far - i could choose how i spend my freetime in two really different worlds ->work on the backend with PW or solder and glue some things together on the hardware parts...before this project i was captured only on the web...;)
  2. Thanks for all input again. Again i was not to clear - single project just for me and just for information no public hits no further usecase for the system. Yes LostKobraKai i think i did'nt plan on this one...until now i didn't have such a usecase or wasn't deep into database performace (what is not really needed for normal websites if you use PW as a base...it scale for this cases and i know that well) So may i am a little bit to naive on this project - and my feeling said "Hey try to ask the dev guys in the forum for hints" ...;) I would first go the hard way and make my hands dirty and will try how far PW could go on this one.... Yes nested page setup like metioned wont scale on things like "live aggregating" all saved data, but i think i would be happy if i could get things like average of year/month/week and store them in separate fields on the dedicated template - so like netcarver wrote if i am modest in granularity it will run fine. But a important Tipp is the FieldtypeEvents module from Teppo, i forgot this one - it would work great for the week dataset so many pages are spared. What i will try with dummy data is now: templates /station/year/month/week station (id, title) year (id, title, temp, humidity, pressure, rain, light) - the average - average from 12 childpages should be no problem month (id, title, temp, humidity, pressure, rain, light) - the average - this will end in 52 childpages for a join for the average week (id, title, records - modified eventtype field for the intraday records) - this will end in 672 entries (if i take a record every 15 minute) in one week field Problems on this one would be selecting from date to date but i would be fine with averages of weeks or months...and maybe the amount of fieldtypeevent tables (52 per year)? I don't have the time to investigate in other DB systems, since this year i've got one more little maid that take over my speartime 😉 But with your interesting input i can think i get in the right direction, and don't have wrong views on aggregation and reporting of the collected data. Since alle of you pointed out that the collection wouln't be the problem with PW or MySql....but all the other stuff. And on these points i could make compromise since this is only a hobby project. I will report (even if it took a while). Even on such rare and offbeat questions in this forum you get helpfull and friendly answers! You all made my weekend! - I love this forum, it is a hidden island in the www
  3. Ok i only thought that the API request would be easier if i could filter with parent pages, then run an SQL trough all pages on the created date field? // Find all entries of May 2019 $records = $pages->get("/2019/05/")->children; with my simple DB wisdom i think PW would find the needed data faster...but this is the topic of this post...my lack in DB background (this is the main reason why i like PW so much...;) the parent structure would be no problem - i've in my mind that the old blog tutorial from Joss save posts with such a system on page save...
  4. Ok sorry for don't beeing more clear in my first post... ("ESP8266" is a Arduino like Microcontroller that runs the sensors and send via WAN to my website for datastorage) like you thought it is one weather station i would like to build up at a minimum collecting temperatur, humidity, pressure, amounth of rainfall and maby a light sensor for sunshine hours per day). So my first "PW way of life" would go for pages... Data simple send every 10 minutes via POST or GET to a template and save data as pages. template "station" as parent holder - maybe i will create a second one at my office...so here we have a title field at least template "record" as child of station for the data records - fields like i wrote 4-6 - temp,humidity,pressure,rain, light - all integer or float fields i think i should try with dummy entries if this setup would work... For better caching and overview i could adapt a kind of blog page tree like /station/2019/07/20 so i get a parent for year/month/day so filtering and data processing via PW API would get much more performant i think?? thanks for all input.
  5. I've searched in the forum and found some entries but no one really fits... project goal - building a simple weatherstation with an ESP and send the data to my PW page and save it...that sounds easy load - would be just 4-6 records like (temp, humidity, pressure, rain, brightness...) but if i set the timer to 10 minutes - there will be 52560 records in only one year....and it should run a few years data... question - how to save the data - that visualisation (d3 or something else), database performance and so on would work... So could i simple run with a page template for the data and save all records to a page (5 years would be 262800 pages...)? Or should i setup a own mysql table for this one - links or examples would be great - with this i'm not experienced? Or could i go with something like RockDataTables ? Where is the right path...i take should i?
  6. Just have to let at least my words here - the last months sadly i don't had much work with PW - but now i was in need of pdf thumbs....and there are two modules....first one doesn't work. This one runs for me now on shared host, PHP 7.2 and PW 3.101 and i have to say thank you again to Adrian! Even the small not polished modules from you work as a charm over years 😉 Best regards from a atm sparetime PW user.....(two daughters have taken over my time almost complete - best wishes to @Pete ) mr-fan
  7. thank you very much...it was the first one - seems to be a laragon problem! (please edit the projectname like i did - forget to rename it for posting...;) Thanks again!
  8. Installed a older site profile into a fresh new PW master version 3.0.123 and get a problem with fieldtype options field. Message Process return no content in the backend fieldsetting and pages that use a optionsfield. On Frontend with debug mode on i get this: ProcessPageEdit: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mydbname.fieldtype_options' doesn't exist #0 W:\laragon\www\12_projectname\wire\modules\Fieldtype\FieldtypeOptions\SelectableOptionManager.php(139): PDOStatement->execute() #1 W:\laragon\www\12_projectname\wire\modules\Fieldtype\FieldtypeOptions\FieldtypeOptions.module(263): ProcessWire\SelectableOptionManager->getOptions(Object(ProcessWire\Field), Array) #2 W:\laragon\www\12_projectname\wire\core\Wire.php(389): ProcessWire\FieldtypeOptions->___wakeupValue(Object(ProcessWire\Page), Object(ProcessWire\Field), Array) #3 W:\laragon\www\12_projectname\wire\core\Wire.php(416): ProcessWire\Wire->_callMethod('___wakeupValue', Array) #4 W:\laragon\www\12_projectname\wire\core\Page.php(1422): ProcessWire\Wire->_callHookMethod('wakeupValue', Array) #5 W:\laragon\www\12_projectname\wire\core\Page.php(1150): ProcessWire\Page->getFieldValue('orientat Field name was orientation and there is the break on the getFieldValue function? But in the DB everything is there - are there bigger changes from PW 2.8 to 3.x?? the used field_orientation table and all the other option fields is there, too... what could here gone wrong on db installation of the site profile or incombatibility from PW 2.x to 3.x? If there is no fast solution or thing that i've not in mind - How could i setup this Fieldtype new? Deinstallation/reinstalltion of this core fieldtype is not easy i think? Best regards mr-fan
  9. default theme was ok...but uikit should have be changed to the default, but i think there were reasons to separate this things... I don't know if i get the time the next two weeks - for every one who wanna try here is my messy start on get the right uikit markup. It builds a responsive grid with standard ui cards with header,body and footer. The view and edit buttons are on the footer - hover on cards with selection not implemented - like i wrote just playing a little bit and have fun.
  10. So just had time to play with the HTML/CSS output...it would much more easies if we could use uikit markup. Just make some dirty changes in renderNotes() and get a fine working responsive grid with uikit cards...if i fin the time i could send you a PR with a own view for uikit theme users...(color and some special CSS classes are missing)... A Fonticon chooser for the single notes would be a other option to differ the single notes, than fiddling around with colors...? Best regards mr-fan
  11. No i think these are very good examples of kind of application that you are looking for and Bernhard let us take a closer look into his building process and decissions...so many things to learn 😉 Welcome to Processwire! @jmartsch just like you - this forum its kind a like a save harbour for straightforward and friendly people getting their things done and help each other...
  12. Great tool - when will you build it as a PW module....just kidding..;)
  13. I don't wanna waste to much words on this but i have to write you my feelings a) i love the concept and design from ryan! b) and i love how constructive and good are all the input on this topic is! (no bashing or i would do it in red...or somehting like that) I know that such a open disscussion could take many wrong turns on other places, but not here! Great people here - wish all a great 2019
  14. Alternative to PS and much more interesting illustrator...for those who hate montly rates...;) https://affinity.serif.com real 30% off - for beginners the workbooks are great!
×
×
  • Create New...