John Adams wrote: Mon Apr 15, 2019 5:55 pm My career is automation/CI It is the one thing I still obsess over.

My career is the dev side, but I've always enjoyed setting my personal servers up myself, so pretty at home with Linux, nginx, whatever.
<3 the whole process of everything so I've been tinkering with various things for years.

Been using docker for years, so started using kubernetes recently. My newer sorta eq2 orchestration component uses k8s to launch zone servers as needed, but I never used it for the actual Stitch server yet. Maybe kinda sorta overkill, but hey, I was already using it so it was pretty easy to tap into the API from whatever language.

You will need to install node package manager, php, apache, composer, etc? You have a setup that you can do that?

neatz09 wrote: Tue Apr 16, 2019 7:02 am Id like to give it a try

You will need to install node package manager, php, apache, composer, etc? You have a setup that you can do that?

i want to try it as well i can install anything lol lots of space and cpu cores

I will get a commit going tonight and post a link here. Keep in mind, this is tuned for my database structure and there will be bugs, post them and I will get them fixed ASAP.

Until this is released, I will just zip it up. Long term though, I will have a public GIT.

You will need a .env file, create one in root. During release I will have a .env.sample.

I have never done a Windows install of this stuff, so until I have time to try it and write up a wiki on it, you are own your own.

For me on Debian I install composer like this...
I install node like this.
I run composer
I then run Mix
You are also going to need mod rerewrite I think.

Also, keep it behind a firewall for now. There is no authentication system yet. I am not worried about that though, Laravel already has the framework for password changes and authentication baked in.

WSL is also an option on Windows, for that familiar Linux feel.

Just keep in mind, this was written in about 2-3 weeks total and a lot was done, expect bugs. The bugs will get worked out, it just takes time. Patience is a virtue grasshoppa...

Yeah i can do all that look forward to checking this out! It looks badass in the screenshots

As I was saying in a previous post that I will not know what needs to change until I start using it, well plenty of things need to change. I was storing some of the dropdowns and recently selected id's in the session. I obviously did not think this through. If you have multiple tabs or browsers open then that is a huge issue. I am one to have multiple browsers open. I am thinking of changing some of this to url parameters instead. There is no harm in that unless you are putting in sensitive data. Laravel already handles any type of injection issues in the framework. So I am going to switch gears and go back to the first page and make a bunch of changes. I am going to go ahead and add the authentication while I am at it. Go ahead and play with what is already there but expect major changes coming up.

I am also going to make searching large piles of data easier. On some things I already have filters to filter down the long downdowns, but not everywhere.

Started the install of my debian 9 server . wish me luck

I have the framework in for authentication. Anyone have any suggestions or does it look okay? I am guessing these logos are open for use? I see them all over the place. I need something pretty much round or square like this. I can remove it if someone can foresee an issue using it.