please go to the blog repository.

Hrm?

Oh, the angry sinatra thing?

yes

That's windows only, but I'll upgrade whenever we actually start running the blag. In fact, I probably should keep working the blag. That is a good reminder.

Yep/

But we need to discuss the blag.

I think we should change it to nodejs and angular (or nodejs and react or something like that...)

@thesecretmaster because it really does make it easier, and it's much much easier to make a responsive front end with react.

FWOOOSH

finally

XD

← 10 messages moved from The Classroom

good idea

Anyways

can we switch to node js?

Node is fine with me, but I just won't be of much help :)

points out that this is they way to learn new stuff

XD

Yeah, it's not that I don't know node, it's just that I'm still learning.

If you want to get a fresh start, I'll archive the old repo and make a new one

I get that. I'm sure it'll be just fine.

@thesecretmaster good idea.

I'll start a new one (actually 2. one web, one server)

now, another tech choice is the db for the blog.

I don't have a preference here...

Me neither. Anything SQL is fine by me (except sqlite in production). I've only touched nosql dbs a bit, so maybe stick away from them.

I'll look around the "market" to see which techs exist

MySQL/Postgres are big ones

Then there's MariaDB which is basically MySQL, MS SQL Server which isn't free (IIRC)

and mongo, which is mongo and thus difficult

Oh yes, I'd forgotten.

I agree about the MySQL

I'll search for a node package now

MySQL has broader hosting support. Longer usage, and probably better chance of finding help when needed

correct

I have a server which I can donate to the cause.

I think I have node installed, and I definitely have MySQL up and running for other projects

I don't know Ruby and node, or react. I don know MySQL/MariaDB quite well, however, and can offer assistance with that if/when needed.

@thesecretmaster We can use git pages for now

Though, TBH, any SQL variant is going to be 98% equivalent functionally.

Yeah. One of em recently added a JSON type, which made me happy.

I think it was mysql?

Yep

JSON type, as in field, or as in output?

As in, you can create a JSON column.

@ItamarG3 But... with GH pages you have no backend. No DB. Just static frontend stuff.

@thesecretmaster really? didn't know that.

ok

Yeah, it just serves files out of a directory (or a special branch)

@ItamarG3 Made a new GH repo, adding you as an owner. When you've got a skeleton, push it :)

Oops, I didn't see that you'd made one.

Are you planning on making separate server and client side repositories? That seems... strange to me. Any reason not to do them together?

I'm doing the server bit first just the basics, so we'll have something to work with

@thesecretmaster conceptual separation.

Seperation of concerns is good, but we want common history, and lots of the server side and client side stuff will be closely tied together anyways.

true, but it's not difficult to link them

Don't forget, there is still the general storage space on Google Drive if it's needed. tinyurl.com/cseducators-se

Anyway, with that, unless needed, I'll leave you two to your party.

@ItamarG3 It's best to put them together for a couple reasons: Easy setup, common history, and common GH resources (e.g. issues)

Please let's keep them separate

what kind of setup are you referring to?

As in, you know where the views are going to be relative to the root of the project.

Sure, we can keep them separate, it just seems strange to me.

It seemed so to me at first, but I got used to it

(This isn't my first web project XD)

Neither is it mine :) Maybe it's a node thing, I've just never seen it before.

I live in ruby/php/python world, mostly, with a bit of node/go/other stuff sprinkled in.

After a bit of research, it appears to be a mostly node thing -- throwing out the idea of dynamically generating views server-side.

Here's a relevant software engineering.se question