xendk / cim Goto Github PK
View Code? Open in Web Editor NEWMoved to Drupal.org
Home Page: http://drupal.org/project/cim
Moved to Drupal.org
Home Page: http://drupal.org/project/cim
It's a complete mess, which purpose was to avoid sending arrays back and forth.
Currently local changes get incorporated into the newly created snapshot. They should be reverted before snapshotting, and reapplyed afterwards. Or more elegantly be ignored in the applying of the pushed changeset stage.
Checking if the changeset is valid (Changeset::appliesTo()), rejecting it if not, or applying it otherwise (creating a new snapshot in the process).
Thinking XMLRPC is the straitforward protocol to use (we don't want external dependencies).
And applying the configuration to the client site, making a note of the snapshot for later creation of changesets.
Common element for displaying the changes of a changeset.
Should be as easy as entering the URL of the master, which initiates a FB/Twitter/Google like 'app authentication' where the user is redirected to a login on the master (or skipping directly to the next step if already logged in), and being asked to confirm the hookup (if the user have the appropiate permissions, of course).
There'll be some key exchange done in the background for future communication, but it's important to remember that the client might only be reachable from the local machine (we assume that the client can always communicate with the master), so callbacks from the master is not an option.
When configuration has changed on upstream, there needs to be a way to pull the changes, but retain local changens.
Split admin pages dealing with upstream out from pages dealing with local snapshots.
Split out XMLRPC server stuff out from client code.
This is a reminder.
"The least amount of code that could possibly work".
It still thinks that the upstream is at the previous sha.
Current know upstream sha is together with the local sha that gives the same configuration. However, currently it pushes all local changes, including those that haven't been snapshottet yet, so no local snapshot may exist.
Automatically creating a snapshot could fix it, but I'm not too fond of that.
Only pushing "up to" a given snapshot is another solution, but the UI needs to be tight, so it's obvious that it's "up to", and not just the given changeset. Both options could be handy, but the possibility for confusion is great (the difference between pushing a changeset and a snapshot is small).
From the difference between the last fetched master snapshot and the current client configuration, and pushing it to the master.
As the configuration can contain sensitive information, it must be protected from prying eyes.
While requiring the server to support SSL could be a solution, it's not good enough as it raises the bar for the end users, and we want to keep that as low as humanly possible.
So, some possibilities:
mcrypt
openssl (simple example in here: http://stackoverflow.com/questions/1391132/two-way-encryption-in-php )
The question is how widespread those PHP modules are.
Pure PHP lib: http://phpseclib.sourceforge.net/ (with fallback to mcrypt/openssl, if they're available).
PEAR packages: http://pear.php.net/packages.php?catpid=6
We don't want the features situation where we have "feature components" and "feature sources" and code that unclear on what's it's referring to.... Starting point:
Needs work:
SnapshotInterface -> ConfigInterface
ArraySnapshot -> ConfigArray
Config -> ConfigDrupalConfig (must avoid confusion with the DrupalConfig class).
perhaps?
And everything should be namespaced or prefixed.
To eliminate the dupe '#type' => 'value' item in every form.
Later on it might gain the capability of editing the changeset.
Debug logging of communication would be very nice.
Administrators shoud be able to revert the changes in a single snapshot.
Administration page to list all snapshots and do stuff to them.
So admin can inspect the content of a changeset.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.