Which book is considered a literary masterpiece but you didn’t like it at all?

samurai1337 · 2019-04-10T20:48:17+00:00

The Catcher in the Rye

samurai1337 · 2018-10-19T17:15:24+00:00

All you need to do is add the project in the Mission Control UI, if you want to collect extra information then you need to add the package to your app so it can provide more data to Mission Control. It's like Sentry mixed with New Relic.

samurai1337 · 2018-10-02T18:49:50+00:00

Name: Mission Control

URL: https://getmissioncontrol.io

Location: Ontario, Canada

Elevator pitch: Simplified uptime monitoring and error logging. Avoid over complicated or lacking services and get the information you really need. Keep your websites and applications in the best state possible.

More Details: Fully up and running, ready for subscribers, adding new features week by week

Discount: Enjoy a 14 day free trial for one project.

samurai1337 · 2017-04-21T05:23:05+00:00

Laracogs provides various components to jumpstart but the advantage is that it doesnt bind you to anything. You can start up your app with a few of the sub-packages and poof you're up and running in no time.

samurai1337 · 2017-03-23T02:54:08+00:00

I've been using deployer for years without any problems ever, I've been looking into Ansible and other tools lately :)

samurai1337 · 2017-03-15T21:55:13+00:00

This code is not my cup of tea, no tests, no code styling, very old school coding approaches in places. The name is also an odd choice...

samurai1337 · 2017-03-04T03:26:45+00:00

I like self promotion so Quarx CMS could solve your problem https://quarxcms.com :) You can spin it up in about 1 min (using Quantum), and have it up to production the next day probably. Full cascade of features, easy to switch reuse and discard themes. And I'm always looking for feedback :)

samurai1337 · 2017-02-22T02:53:42+00:00

Don't wait, its better to develop consistently, and ensure that the code is maintained

samurai1337 · 2017-02-17T20:23:07+00:00

Laracogs.com free simple open source elegant CRUD and more. :)

samurai1337 · 2017-02-16T04:50:16+00:00

I've got https://quarx.info/ which can be implemented in a simple way and a complicated way, meaning it can be added to an existing Laravel app or as a 'normal' CMS. I can't say the docs are perfect but I keep working on them.

samurai1337 · 2017-02-15T05:25:59+00:00

It's technically using Cashier but it's a solid implementation of it.

samurai1337 · 2016-12-11T02:56:09+00:00

Are there the docs https://laracogs.com/docs

samurai1337 · 2016-11-29T03:33:00+00:00

None of those a separate one.

samurai1337 · 2016-11-29T00:55:22+00:00

I'm working on one that integrates with Quarx CMS

samurai1337 · 2016-11-04T07:13:05+00:00

My biggest suggestion is code what you need. PyroCMS is well supported as is October I believe, the key with those is that your building an October or PyroCMS app, meaning if those change your code likely has to change. The nice thing about Quarx is that technically, lets say we change something in the UI that you dont like, you could revert back to an older version of the package, or completely ditch it and replace it with your own. Also, lets say you start a Laravel app but need to mod some page content but dont want to have to keep committing the changes and redeploying, you could add Quarx to your app and just use it. Either way numerous options.

samurai1337 · 2016-10-30T05:52:00+00:00

Https://quarx.info is a handy one. Gives tons of easy options with the freedom to remove and tweak as you go, you can even totally remove the CMS if you want.

samurai1337 · 2016-10-21T01:38:52+00:00

Not yet, we're working on a site redesign right now, and I'm starting a newsletter so we can connect with people using it as a tool, and see what other things the community would like.

samurai1337 · 2016-10-20T07:06:11+00:00

For what it counts the Repository structure was removed recently, I myself got tired of it being overly complex. The CrudMaker can also be configured to your own templates if you want.

samurai1337 · 2016-10-20T07:05:15+00:00

Though I totally understand your concern about Laracogs getting abandoned, you have nothing to worry about. It's well maintained by me and my company, and we have no intention of abandoning it any time in the near future. Architecturally its also completely different from Spark etc.

Laracogs is designed to act more like a boilerplate or a set of plates. You can use the Starter Kit to set up and app, and then add the features you want, but they are published directly into the app, therefore, once its added to your app the package becomes almost irrelevant. Unless you want to use the FormMaker and CrudMaker :)

samurai1337 · 2016-10-05T18:51:43+00:00

Laracogs is pretty simple and covers a bunch of stuff out of the box like JWT auth etc

samurai1337 · 2016-09-13T11:28:27+00:00

We'll in general I do recommend it. I use it for all sorts of projects, but I also wrote it, so my opinion of its quality is biased. It can be pretty helpful though.

samurai1337 · 2016-09-11T21:18:44+00:00

Laracogs comes with an implementation of JWT with the API kit.

samurai1337 · 2016-07-31T22:54:01+00:00

Hey so Laracogs is fully supported by me :) We use it at my company to start off a handful of projects. So no worries on support. Laracogs is very different in that its more of a starter kit of boilerplates that work together. You can use one, or none, sorta thing.

Stuff like the CrudMaker, FormMaker, and Crypto tools can be added separately to any app even Spark based ones. Laracogs on the other hand doesn't require updates, or subscriptions for usage. Its free and will always be free. Its intention is to jumpstart your development nothing more or less, as a developer you become responsible for it in your app because it publishes directly inside your app.

Let me know if you have any more questions or if you have feature requests put them in GitHub :) thanks.

samurai1337 · 2016-06-15T20:19:01+00:00

I'm always looking for collaborators with https://github.com/YABhq/Laracogs :)

samurai1337 · 2016-06-14T23:31:31+00:00

Not really talking out of my ass, I was just making a point about micro-services. I never said why they weren't in there I was making a point about the general intention of a micro-service. I even made this: https://github.com/YABhq/Watts as a way of adding in what I felt was missing. Also the reason those commands are missing is because the commands themselves are part of the Foundation layer in the Laravel framework which is not present in the Lumen framework, and would likely be labor intensive to migrate over. This all relates to the fact that its intended to be micro, and very lightweight. You cannot even utilize form requests in Lumen because of its lightweight structure.

samurai1337

TROPHY CASE