vektra / tachyon Goto Github PK

Call this a different tool, there are lots of different things here.

Thanks!

Just because there's a larger public with js knowledge :)

I like tachyon!! I am a golang developer, can I join your organization?

Hello there.
You project seems to be the only CMS written in Go at the moment. So it would be nice to hear some elaboration on this bit of your README file:

don't wish to runtime eval any golang code

As being something important / worthwhile to comment about in terms of feasibility, some technical analysis.

The thing is that I do find ansible can be very slow... and it's based on python. It would be great to keep the successful ideas of ansible while improving the performance / execution time. Maybe you do already achieve right now quite a good performance with your stated Lisp interpreter. Unfortunately I can't cope with lisp myself. And I suspect it's also a view shared by many others. Tried lisp with emacs and just hated it. Too many ((())) brackets.

So my question really is: what would a GO-based CMS actually look like if it were like Ansible?

We would need the host control machine to have golang (in the same way that ansible requires python as a dependancy). In order to compile user code fragments (modules, user tasks, playbooks) into runtime executable(s). Perhaps cached. Then to run them either locally on the control machine (to exec sequences of SSH cmds / copy over shell scripts) or else to transfer them onto the target machine to be executed directly there. Depending if the target machine's architecture can be compiled or not.

It is feasible? Well I don't know that. Would it work? Don't know. But I think that using the popular implementation language GO throughout may help to gain more interest / community momentum from outside contributors.

Hi @vektra, thanks for a nice software!
Could you add the LICENSE file?

Choosing an Open Source License might helps for choosing a license.

Is this project still maintained?

Hey there, your Travis build is failing and it looks like a configuration issue (rather than a test failure). Might want to check it out!

Hey there, I'd be interested in using code from this package or contributing to it. However, a lot of source files have zero comments or sometimes just one. Would the author mind filling some in? Thank you!