Well I certainly never expected my project's name to conflict with another "shitty static site generator" haha. I ended up swapping "shitty" for "stupid" however: https://github.com/esell/sssg
I started down the Go template route and quickly realized that pandoc + some other standard tools got me everything _I_ needed. It was a great learning experience for sure!
coming back, i stumbled over this while looking at options: https://docs.alephdata.org/. It is a bit more heavyweight than plain elasticsearch, but it has some nice additions that might make it worth it depending on your situation.
submitter here, just to be clear, i have no association with this company. i just happened to stumble across it today and thought others might enjoy it as well :)
While I love the idea, that price is totally insane. I don't see how anyone would be willing to pay that much for what is essentially a beta device. It seems that it is quite difficult to manufacture these devices, at a reasonable cost, without help from the big names :(
Yeah, the amount of data is pretty small in the grand scheme of things, maybe that is why i'm getting so hung up haha. Elasticsearch was actually the first thing I thought of so maybe I'll just go with that and see what happens...
Yeah, I'm not expecting a ton given the price point, I have my "real" machines for work.I would like an open and functional option for traveling, conferences etc though. Maybe it is because of delivery timelines or something, but I don't see many people reviewing these outside of initial unboxing type details...
Any real, day-to-day usage feedback on the PineBook Pro? I've looked around on their forum + reddit, and outside of a couple of reviews (mainly only a day or so into ownership), I haven't found much. This one seems to be the most in-depth so far: http://students.engr.scu.edu/~sschaeck/misc/pinebookpro.html
put together a tiny wifi hacking/testing stick with my pi zero w. i added a USB plug on it so i can just plug it into my laptop, ssh directly to it (not via wireless), and then use the wifi on the pi to do my wifi hijinx :).
this way i keep my host systems wifi "clean" and can use the pi zero as a standalone device without having to worry about power cables, wifi connections, etc.
Thanks for the response. Just curious, are you single or do you have a family who depends on your income? If the latter, how did your family handle the adjustment?
Wow, thank you everyone for your comments! Literally every comment has provided value and caused me to think a bit more on this. I appreciate all of your responses and hopefully this can help others in a similar situation.
With regards to what do I find interesting, honestly I would put offensive at the top of the list but I do have interests in the defensive side as well as the malware analysis. I am, what I believe, a "problem solver" by nature so I enjoy the idea of being given some unknowns and being told to go figure it out.
I'd like to hear about this as well. OpenBSD has been on my list of "to try" for quite awhile but the app/package thing has been a big question mark for me.
I _really_ enjoy being able to apt-get or brew install pretty much any of the applications out there and am a bit worried about how that experience would be on OpenBSD. I guess the best way to find out would be to try it eh? :)
original author here, maybe giving some background will help explain why this was created (maybe it won't).
at a previous company we were doing the whole micro-services thing + CI/CD and all of the fun that comes with it. every time a service was compiled (dev, test and prod), a deb package was also created as that is how we did deployments. with many services being built on a fairly frequent basis, we ran into an issue using another setup that used s3 as the backing storage (sorry, i don't remember the name) where we were getting race conditions with regards to the repo metadata. that caused all sorts of fun issues during deployments. additionally, the uploading of packages via our build system was a bit clunky.
when i originally wrote this to solve our problems it really was pretty simple, just under 300 lines of actual code and was designed to "solve" the race condition caused by frequent uploads of multiple different packages AND expose the service as a rest endpoint which fit into our build system better.
since i originally wrote deb-simple a few people have come through and submitted AWESOME changes that have made deb-simple a bit more robust without impacting the overall functionality. some of those changes have made deb-simple a bit less... simple, but the trade-off has been well worth it :)
Just curious ,are you using the web based UI to look at your data or the CLI? I use the web UI so I'm wondering how something like this might work with that. I'll have to poke around. Thanks for sharing!
I LOVE Goaccess and highly recommend it as well. My single complaint is the lack of ability to filter/define a date and time range. I know there is an issue for it but last time I checked it had been open for quite some time :(.
I started down the Go template route and quickly realized that pandoc + some other standard tools got me everything _I_ needed. It was a great learning experience for sure!