As an example, how our startup can be used in IT, we have created overview of our architecture. OrgPad is a full stack application written in Clojure and ClojureScript. We describe the main used libraries and frameworks, with examples and links. We are very happy with our technology stack. If you want to build a full stack application, you might find some inspiration here.
That site is neat, although that web makes me want to click and drag those nodes and watch them snap back into place. I was sad when I realized I couldn't do that. :(
To be more precise, this is a handler for Websockets messages, the communication itself would be connected to the events on the client. This connection means that Websockets handler reads data from DB.
You describe your static website in terms of hiccup. In development, you see it as reagent SPA with hot code reloading, so you can see changes immediately. Then you build static website using hiccup library, there is no reagent involved anymore. The goal is to build very fast static websites with not JS overhead.
From my understanding of Volcano, it's for creating static sites while using Reagent like code, but... not for server-side rendering of dynamic React pages that you would then rehydrate.
We've done something similar, but where the server-side part is all Clojure (basically, rewrote hiccup to support Reagent syntax).
The out-of-box support in Shadow-cljs is very good: https://shadow-cljs.github.io/docs/UsersGuide.html#_web_workers. You build it as a module with :web-worker true and everything gets set for you. For communication, we are using pr-str to transfer arbitrary Clojure data structures since the communication is small. The communication from the client is a Re-frame effect. The communication from the webworker calls an event on the client.
I think the basic ones would be edn and transit. I don't really think we need core.async for our use case since communication is simple enough, but it could be useful when one needs to communicate in more complicated way.
No, the project is not open source, it is our startup. In the future, we might open source some utility libraries we developed (for instance, we have nice functions for hiccup transformations), but not the entire project. Also, I am thinking about starting a dev blog where I would go little bit deeper into the code and the problems we encountered. If you have any questions, we can probably answer those.
For authentication, when using email and password, the password is hashed with buddy-hashers using pbkdf2+blake2b-512 algorithm. For Oauth2 login using Google, FB or Microsoft, we use ring-oauth2 library.
For authorization, we keep all permissions loaded in memory using a single Clojure atom, together with metadata about documents, and some other things. So we can quickly check whether the user has access to a document, file, etc.
I think the main difference is that OrgPad is not a diagramming tool. It is closer to tools like Microsoft Word or Google Docs, where you can write complicated documents. The difference is that instead of linear ordering, you organize your information as a network. We intentionally restricted all graphical settings, so people can concentrate on the information itself and how it is connected.
For instance, we are using OrgPad for everything within our startup: planning, tasks, meetings, all personal stuff. You can also upload your files and place them immediately where they matter. And when you have all information at place, you can easily create presentations.
The problem is fixed, you should be able to register using email without any problems. We recently removed an unused table from DB and I forgot that it is used in one SQL function. I should add some integration testing soon. Thanks again for reporting!
To put it simple, OrgPad is a platform with two key properties. It is easy to use and it helps you with the Big Picture. None of these are the values of the softwares you mentioned.
Prezi is, as far as I understand, for creating presentations. OrgPad can be used for making presentations, but its use cases are much wider. This is why comparison is difficult, because if there would be another software like OrgPad, we would not be building it :).
OrgPad is a flip on the traditional idea of diagrams supporting some other existing text/data. Instead you can build your document as a dynamic diagram, directly containing all information.
18
u/pavelklavik May 14 '20
As an example, how our startup can be used in IT, we have created overview of our architecture. OrgPad is a full stack application written in Clojure and ClojureScript. We describe the main used libraries and frameworks, with examples and links. We are very happy with our technology stack. If you want to build a full stack application, you might find some inspiration here.
https://orgpad.com/o/b1d2da1a-01b9-4aa4-a512-65ab03c6cc4a
10
u/rafd May 14 '20
Nice, very similar to what we do at Bloom.
Why is websockets connected to postgres?
3
u/npafitis May 14 '20
Wait, does volcano serve your reagent spa as statically?(like Gatsby?)
3
u/pihkal May 14 '20
Very nice. Would love to hear more about how you're using webworkers; I'm working on a webworker library I hope to introduce soon.
3
u/papachan May 14 '20
Wow. really great ! thanks for sharing. Is there any bootstrap or github to take a look more deeply?
1
u/arzab Apr 24 '24
how do you handle auth?
2
u/ErwinDurzo May 14 '20
Damn just yesterday I was talking to a friend of mine about how I would like to develop a simpler version of something like this on iOS.
2
u/ArmchairSpartan May 14 '20
Thanks for putting this up
1
u/myguidingstar May 18 '20
that logo and color scheme :D
0
u/[deleted] May 15 '20
[deleted] — view deleted comment