Fork me on GitHub
#off-topic
<
2018-09-14
>
orestis04:09:05

@jayzawrotny do note, heroku dynos don’t have persistent storage. If you are processing user uploads you need to store them in S3. Other than that, it’s pretty easy to convert a Django app to run on heroku. Files are also easy, just need a little bit of research on storage back ends.

valtteri04:09:19

👆 Yep, that’s what I tried to communicate yesterday with https://12factor.net/ link. Dynos actually do have a filesystem where you can store files but Heroku might rotate your dyno any time so in practice it’s good only for /tmp kind of things. For persistent storage you need to use something else.

jaide14:09:30

Ah right, been reading that. We store our uploaded assets on s3 anyway so we should be good.

jaide14:09:26

Though a potential roadblock may be our use of logical decoding in Postgres which a key part of our app depends on. Not sure if Heroku Postgres supports it.

john22:09:57

Alright. It's naming time. What to call a static blog engine that lives 100% in the browser?

Nolan22:09:12

blorg :robot_face:

john22:09:17

That's a pretty good one

Nolan22:09:12

bah, classic

john22:09:48

How about REBL, for Read, Eval, Blog, Loop

wizard 4
Nolan22:09:03

was about to say bepl

Nolan22:09:20

but rebl much better

john22:09:44

rebl it is

richiardiandrea23:09:40

Isn't it what Klipse does?

john23:09:53

The idea is sort of like a combination of bengine, maria.cloud and the github api to make a static blog generator that runs and saves itself into a github repo

john23:09:23

bengine, ported to self-hosted cljs

john23:09:33

So the blog pages people actually read are static pages, with no JS

john00:09:55

Unless you put it in there, optionally. it's just hiccup html

richiardiandrea00:09:15

oh yeah that's nice!

john00:09:54

Yeah, I'm going to try to keep it simple and easy to fork and others can hopefully improve on it.

john00:09:37

Just trying to get the web auth flow sorted out

john22:09:15

I was thinking something like "REPL on a git stick" but that's kinda long

john22:09:23

REBL (Read, Eval, Blog, Loop)

👍 4
danny23:09:41

REBL without a clause

bhauman15:09:59

This is cool I worked on something like this a while back

bhauman15:09:16

I’m assuming it talks straight to github?

bhauman15:09:13

what’s the top level UI?

bhauman15:09:21

a react markdown editor?

bhauman15:09:31

page link navigator?

bhauman15:09:37

@U050PJ2EU I called mine next press

john15:09:51

I'm trying to use pieces of re-view (from the maker of maria.cloud) for rendering code from a text area into neighboring view. And I'm using hiccup forms, ala the bengine static blog method, in those text areas to generate views.

john15:09:42

So hiccup instead of markdown. Though, it'll probably make sense to add a MD editor for all the straight text, and only use the hiccup editor for structural layout.

john15:09:58

So the text area is probably going to be collapsed, I'm thinking, and you can expand it by clicking on it.

john15:09:01

checking out next press

bhauman15:09:17

oh its a mess

bhauman15:09:43

the one interesting thing is it was easily plugable

bhauman15:09:08

the render process was pluggable

john15:09:30

yeah, I see that. Pretty extensive plugin action going on in here

john15:09:17

How does a user pull in a plugin?

bhauman15:09:25

I don’t think I got there

bhauman15:09:36

but you could create your own render chain

bhauman15:09:54

I made this a very long time ago

bhauman15:09:02

and I ran out of steam

john15:09:06

and it could sorta work like the wordpress plugin system

bhauman15:09:28

its a little different in that its just a render pipline

bhauman15:09:43

you hit publish and it assembles all the static resources

bhauman15:09:59

just like Jekyll would

john15:09:00

Well, the niche I've landed upon, because I've got a self-hosted instance built in, I think I'm going to leave everything up to the user.

bhauman15:09:32

sure self hosted is fun

bhauman15:09:01

and would be a great way to add dynamic capability

bhauman15:09:58

I’m looking forward to learning more about your adventures

john15:09:05

Yeah, and half the sell of this thing is the fun factor. It seems like it's be a pretty good first project for learning cljs - hacking on your own blog, in cljs, over github, without installing anything.

john15:09:32

Well, regardless of how ready it is, I'm pushing something out before the end of the weekend.

bhauman15:09:08

good luck!!!

john15:09:45

I don't have any routing in there yet. Just a single page. That page has a view component and an edit component. All the logic that renders the view is in the edit component. All the github api logic lives in that component. So the site just about builds itself and a user should be able to change anything about it.

john15:09:08

One ish I'm running into now is that I want to have editable components within the view component - so another level deeper. And reactions aren't firing to update my sub views.

john15:09:52

If I can't figure that piece out I'm just going to ship something simpler and punt it. I'm sure other folks can come up with way prettier interfaces.

bhauman15:09:18

that sounds hard but I don’t have a really solid idea of what you are talking about, but I do get the gist

john15:09:25

Pretty much a maria.cloud edit component on the left (https://www.maria.cloud/cells) that spits out yet another customized maria.cloud instance on the right (which can in turn have its left editor and right viewer)

john15:09:26

So that you can build the editor that you edit your markdown in, for instance. So the site builds itself, essentially

bhauman16:09:38

oh that’s interesting

john16:09:24

achievement unlocked!

🎉 4
john16:09:48

super hacky though

john23:09:36

Actually, I think I'll go with PEPL (Pull Eval Push Loop), said like "people"

john23:09:04

to keep it focused around the repl on a git stick idea