71–80 of 87 posts
This looks really well done, newcrobuzon. Very impressed. I especially love your web UI. It makes it very easy to start experimenting with workflows without the overhead of having to set up a local development environment. I am curious how you store secrets (e.g. AWS access key id, secret access key). There isn't a login wall and it's not clear that the values will be protected from you, so I am loathe to put my cred…
Earlier quoted context omitted.
I'd like you to listen to this file, which is your first 'headline' read by `say`: https://www.dropbox.com/s/fanpqs8lv2d9nvl/say.m4a?dl=0 Now imagine yourself in the shoes of a vision-impaired person relying on a technology like VoiceOver. Do you understand how unbelievably frustrating that is?
> Now imagine yourself in the shoes of a vision-impaired person relying on a technology like VoiceOver —- Yeah - thats “frustrating” for like what, ‘dozens’? As opposed to just the other problems in the world that dwarf this? Now imagine you are a % of the population of the globe who actually requires this to be a thought. Yeah - personally, i see this as a statistical straw-man. Sure, why dont you imagine yourself a…
Nice work! How does it compare to n8n? [0] n8n is the closest OSS alternative to Zapier I've seen so far. [0] https://n8n.io/
n8n is pretty neat as a low-code or no-code tool and comes close to zapier in many cases.
As someone with zero Java experience, this tool seems like a very steep learning curve.
Zapier requires zero coding knowledge for most part and is a great no-code tool.
This looks really well done, newcrobuzon. Very impressed. I especially love your web UI. It makes it very easy to start experimenting with workflows without the overhead of having to set up a local development environment. I am curious how you store secrets (e.g. AWS access key id, secret access key). There isn't a login wall and it's not clear that the values will be protected from you, so I am loathe to put my cred…
After clicking logout, I had no way of logging back in. :)
Earlier quoted context omitted.
Do you have any links to some blog posts discussing it (the "doing it right" approach)? I would agree that it definitely depends on the use case. I will definitely check out Syncari - just opened the landing page and it looks great!
Thanks! Haven't had a chance to write a lot about this (heads down building and selling), but https://syncari.com/a-brief-history-of-todays-data-woes-and-... touches on it a bit. For us, it is about: * implementing deep integrations that are commonplace * not spraying too thin in the quest of supporting hundreds of systems * thinking from a data model/data/eventually consistent system perspective * completely droppin…
It is similar with what I am seeing - i.e. lots of older integration systems are terrible with data simply because they force you to use some way of data modeling (e.g. their OOP data models, WSDLs/XSDs etc.) while the newer ones just rely on json which is good but can lack the (sometimes necessary) complexity. To do some data cleansing on the way then seems like an unachievable task (there is certainly such a thing as overdose on XSLT ;) ).
I also like the approach you took with centralized data dictionary - it certainly is something the industry might need, I would wonder how it impacts change management though (especially in bigger companies).
Wishing you good luck!
that is the crappiest website i've seen in quite sometime. my first impression was that this is either a scam or a joke. in this day and age, if you are can't afford a decently designed site, how am i ever even going to give your product a chance.
This looks really well done, newcrobuzon. Very impressed. I especially love your web UI. It makes it very easy to start experimenting with workflows without the overhead of having to set up a local development environment. I am curious how you store secrets (e.g. AWS access key id, secret access key). There isn't a login wall and it's not clear that the values will be protected from you, so I am loathe to put my cred…
Yes, I would still be careful with passwords in the public beta.
It goes via SSL and you get a unique UUID URL so all-in-all it is kinda secured (plus time-to-live of the instance is only 3 hours which limits any time to hack it) but still this is not 100% secure and I would not recommend it for any kind of production use (including any use of passwords you dont want exposed).
The free instances are not (yet) password protected (other then the UUID) - this on the other hand is useful if you want to share the envrionment with somebody, just send them the link... This is just a beginning of the public hosting so I will need to think through further improvements that would go into the hosting, security-wise and other aspects as well.
My main objective at this stage for the free hosted instances was to give people way to play with Titnaoboa or quickly test something, especially if something is not working in their local environment (say dependencies) and they want quickly re-test in vanilla environment.
If you want to add aws secrets or what not I would suggest to just download/install your local version, it is super easy: https://github.com/mikub/titanoboa#installation
Or if you need a public IP to integration just grab the docker instance and spin it in your AWS ECS or something.
Earlier quoted context omitted.
yes, I am considering this and it should not be that hard (also Kotlin, Nashorn javascript...), but at this stage Titanoboa is just a one-man-show - so patience, I might get there ;)
newcrobuzon you're a genius my friend someone should give you an award I loved your idea and how you approached it it's fantastic for developers. I'm a root Java dev and I have to say you did fantastic work to make developers life easier, you didn't take any approach you made your own this is awesome. If you get Javascript working I feel like I'm getting back into AppJet days! This is fantastic stuff. If you show me…