structure

[markthethomas]

@andrewdeekim whatcha thinking for structure? I created some empty dirs and files just to get us going. Figure we need at least client/server and maybe an api proxy in between? idk

also added models for:

• user
• post
• tag
• newsletter

I'd love for it to be able to set up weekly emails for you now that mailchimp costs money and all that

[andrewdeekim]

Weekly emails would be solid!!

Api proxy is also a good idea ^^. never know how big this might become haha. I'll keep brainstorming on this one...

For models, perhaps:

• comment(this might be redundant with post)
• video embedding (this also might be redundant with post)

[markthethomas]

Awesome :) What say we do server-side stuff mostly first, then, and get some of the API all shaped up before we create the client-side stuff? I figure it'll be easier if we know what data we're working with and all that

[Ephapox]

I saw the the latest models and they're looking good! Although I'm not exactly the best judge of models.

Can you explain what you mean by an api proxy? According to the architecture image it looks like there's a proxy between the client and api. I'm not familiar with examples of what that proxy is and what its purpose would be.

[markthethomas]

(for reference)

Idk if we'll necessarily have to have a proxy, but it could be useful. The main use is usually to provide a further means of separation between a client and the actual endpoint itself. Lots of times it's usually w/ a public API, so that the "real" API has some additional protection and you can have one more place to do "real" logic. It's also a nice place for caching and better logging.

Another potential upshot is that if we moved the API to be it's own thing, the proxy could stay w/ the client app more or less and remain it's own thing. This would also probably give us some more flexiblity in terms of backend solution — if, for say, someone wanted just the UI but wanted to wire everything to their own custom backend.

[markthethomas]

Also, there's an error in my sketch — the proxy can also proxy websocket calls, so that should really run through there too.

@Ephapox I think another, perhaps simpler, way to frame the proxy would be as a point of decoupling. So you could potentially make the UI only work w/ the sub-API (I guess? lol) shape and be able to completely swap out back-ends. This would be just one way we could accomplish some of that, though :)