2. Can't you just write simple nodejs process that would watch all files in deirectory and in case on their change, doing the counchdb push?
1. Can't couchdb just serve GETs and accept PUTs normally? That would mean no "amber serve" is needed at all. To remind you, the Amber development process is _not_ bound to amber serve. It can use any server. amber serve is just convenience one. That's why it is unlikely to complicate it with a bridge to couchdb.
2. Can't you just write simple nodejs process that would watch all files in deirectory and in case on their change, doing the counchdb push?
You can implement different transport. If you want to retain .js files as they are today (AMD module), you would probable need to rewrite / write plugin for requirejs.
It seems easier to me to actually be able to serve those files from couchdb directly, by transforming data in/out (I faintly remember there is sometihng that is able to ransform data while serving them; I would presume there is something as well for accepting them via PUT/POST as well; something akin to updateable VIEWs in old SQL).;
If you would be able to also push it here (that is, issue a PUT
/mydb/_design/amberapp/cool.js), than you need nothing else. It would
just work.
> If you could give me a high level of how the transport commit
> infrastructure works, I will take a stab at all this :)
Well, Kernel-ImportExport builds the .js and PUTs it.
You received this message because you are subscribed to a topic in the Google Groups "amber-lang" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/amber-lang/rh9heest5ZQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to amber-lang+...@googlegroups.com.
Hello Hannes,
I'm serving Helios as well, and can currently save packages back to couchDB. I will be posting some questions about where this should live, and I hope to add the ability to create and edit shows, views, and lists, but for now it does what I wanted.
- Brian
On Nov 14, 2014, at 5:52 AM, Brian Brown <br...@clanbrown.us> wrote:My thought is this:
- Serve the amber application through CouchDB (on the local system).
- Run "amber serve" on port 4000
- Modify Helios so that the "Commit package" functionality posts to port 4000.
- Modify the "amber serve" so that after it completes the package commit, it triggers a "couchapp push".
This would allow Helios to be used as normal on the web app served from CouchDB, and still be able to round-trip the packages back to the folder structure representing the couchapp, and push it up to the couch server.
Hi Sebastian,
The motivation is recapturing some of the benefits of the Smalltalk image. Since the couchapp concept of CouchDB creates a self contained web application, and also efficiently serves the site, once you have Helios installed with your app, concerns about the filesystem, WebDAV, etc, go away. You also can take advantage of the built in replication to send not only the app, but it's data as well to any other couch installation.
--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to amber-lang+...@googlegroups.com.