Tania – PHP-based free and open source farming management system(github.com)
github.com
Tania – PHP-based free and open source farming management system
https://github.com/Tanibox/tania
25 comments
The documentation is pretty sparse, and no links to a product page. What does this actually do?
The author of the software here. Basically, you can record when you start seedling the crops, when to harvest, record all your seeds inventory, and write to do lists.
This release has pretty basic functions, but it works for a small farm like mine. I'm still improving the features.
So sorry about the documentation. I need time to develop the website to accommodate the doc and the user guide.
This release has pretty basic functions, but it works for a small farm like mine. I'm still improving the features.
So sorry about the documentation. I need time to develop the website to accommodate the doc and the user guide.
No need to apologize; I wasn't criticizing your project; it just doesn't make for a very interesting HN submission until some detail is added. :)
[deleted]
At the least Nice site for any one looking to see a symphony example. I don't use symphony and despite liking most of the code I still hate the idea developers hand typing routes and that's my main selling point for something barebones like code igniter or some other automated routing process like a json-rpc API that can figure out what controller to go to on it's own.
and when you need to rename a single route you do what, rename the whole controller and/or method?
I guess you can use a micro framework, I Use silex. They're much less opionated. It's built with a synfony components so it's very similar (I think it's the same people).
exactly, that's the downside to it.
it's really nice to have /controller/method/param/param routing out of the box, so the speed of 0 to MVP is quick, but on the other side, renaming a route sucks. unless you have a list of overrides in which case, may as well just use hand written routes from the get go
it's really nice to have /controller/method/param/param routing out of the box, so the speed of 0 to MVP is quick, but on the other side, renaming a route sucks. unless you have a list of overrides in which case, may as well just use hand written routes from the get go
That's what I like about Symfony. It's all in my hands to configure.
I don't understand that philosophy. Isn't the ideal that the default is something sensible and you only change it if you want different behavior?
I disagree. That's too magic for my liking. I like Laravel's routing solution where you have to manually map a route to a controller action. You can set route groups and restrict middleware to specific routes and stuff so pretty powerful!
Laravel's routing and the entire framework makes it impossible to go back to CI.
It seems like a cross between a GIS data system and farm inventory manager. Plus it has data layers for time based crops, water systems, etc.
Would be nice if they expounded on that; I'm not really sure what either of those things are (or rather, I have a hard time envisioning how they would improve the life of a farmer), and I grew up on a farm.
What product is this competing against if any?
I am guessing someone in the farming field may know more about what to do with the program but for the layman an explanation or some instructions as to how you use it would be awesome.
There's a whole bunch of products in the 'farm management system' category. YC's entry is called Farmlogs. I previously worked for another such company called Agworld.
https://www.google.com/search?q=farm+management+system
https://www.google.com/search?q=farm+management+system
I'm a Drupal dev and I stumbled upon farmOS[0] awhile ago, it's pretty crazy what all this stuff can do. I guess I shouldn't have been so surprised about the amount of data that's useful to a farmer.
[0] http://farmos.org/
[0] http://farmos.org/
OT: Why is Drupal 8 such a trainwreck? It's been out for quite some time now, had beta releases available since 2014 and so many modules are still unported or in early alpha status with many issues.
I wouldn't say it's a trainwreck. I've used it on a handful of sites so far and it's been pretty great to use, but yeah you'll still have to wait for certain modules to get ported depending on the type of site you're doing.
You've got to remember that Drupal 7 has been out for six years, so that's a long time for the ecosystem to mature. The current way you'd build a site in D7 barely resembles the way you'd do it back in 2011. Also, it was a long time after it was released that you'd be able to pick it over D6, and I think we're in the same situation with D8.
I did launch a D8 site using a bunch of alpha/beta modules last summer and every time I do updates more and more of them have moved to stable. Lots of the big modules are using this as an opportunity to reevaluate how they are approaching things and that can take time to settle.
On top of that it's going to take some time for everyone to get used to OOP, DI, and all of the new ways of doing things. Personally I love it and have built a couple of modules so far and it's way nicer, but if this is a module maintainer's first exposure to OOP it's going to be a rough ride.
The audience has also shifted. D8 is more of a pro framework/CMS than say D6 was. If you're building a brochureware site or a blog you should just use WordPress or Squarespace. That type of site is certainly possible using D8 but it will be more complicated to set up and won't really show its strengths.
You've got to remember that Drupal 7 has been out for six years, so that's a long time for the ecosystem to mature. The current way you'd build a site in D7 barely resembles the way you'd do it back in 2011. Also, it was a long time after it was released that you'd be able to pick it over D6, and I think we're in the same situation with D8.
I did launch a D8 site using a bunch of alpha/beta modules last summer and every time I do updates more and more of them have moved to stable. Lots of the big modules are using this as an opportunity to reevaluate how they are approaching things and that can take time to settle.
On top of that it's going to take some time for everyone to get used to OOP, DI, and all of the new ways of doing things. Personally I love it and have built a couple of modules so far and it's way nicer, but if this is a module maintainer's first exposure to OOP it's going to be a rough ride.
The audience has also shifted. D8 is more of a pro framework/CMS than say D6 was. If you're building a brochureware site or a blog you should just use WordPress or Squarespace. That type of site is certainly possible using D8 but it will be more complicated to set up and won't really show its strengths.
This looks like a limited-feature clone of Agrilyst [http://agrilyst.com/], which won TechCrunch Disrupt SF 2015.
(disclosure: I work at Agrilyst)
(disclosure: I work at Agrilyst)
You forgot free and open source.
Anybody have a dockerfile that will run this? I'm killing myself trying to build one.
Is this focused on a particular farming nitch? Marijuana? The README.md should have more features/benefits and screenshots at the top, not just all technical doc.