AltME: Web


Yey! Works with Twitter!!
tm: read [
    scheme: 'oauth
    target: 'get
    user-data: context [count: 10]
    key: make key [
        Consumer-Key: #consumer_key
        Consumer-Secret: #consumer_secret
    user: make user [
        token: #user_key
        secret: #user_secret
    awake: :load-json
Endo, I don't think this will help you with Salesforce, but breaking the OAuth part out should make it easier to adapt to OAuth 2.0.
Wow thanks a lot Chris! Thanks for separating OAuth port scheme, unfortunately I'm not familiar with OAuth but I'll try it with Salesforce. Thanks a lot!
I know, I already read it. But SF uses OAuth 2. :(
Is GET supported in read/custom ?
print read/custom http://localhost/test.rsp [get "a=b&c=d"]
Or should I use Graham's custom http?
Read is GET
I tried to change the method without changing the URL when switching POST and GET. Didn't work. Anyway, not a problem.
not sure why you want read/custom for unless you're altering the header contents
read/custom http://localhost.rsp?a=b&c=d [ header [ Cookie: "authtoken=anotherfoo" ]]
There are different authentication methods on Salesforce, so I'm just testing.

I am new to Git. I'd like to use it (or something similar) to keep a distributed copy of a web app I am developing. I'd like copies on two local systems (laptop and desktop) with the possibility of sharing with another developer based far away and deploying the app on my web host.
I sort of get the concept (at least the part about commits, etc), but am not really sure how to keep everything in sync. Is it worth using a hosting service like GitHub or Bitbucket (I know that perhaps defeats the purpose) to assure availability or figuring out how to use the web host for this purpose?
You may want to try Fossil. It's much easier to run your own server
To "keep everything in sync" with Git, you have have to do pairwise syncs. Each pairwise sync can be initiated from either side, the respective commands being "fetch" (from remote to local) and "push" (from local to remote).
If you want to keep many separate sites in sync, mediating the sync via a central host makes sense (as it avoids the exponential explosion of pairwise syncs).
If you have SSH access to your web host, using your web host for a central Git repository is trivial (assuming you have - or can get - Git installed on the web host).
In this one case, the host has instructions to set up Git on a subdomain. I'd have to consider it as it doesn't appear to be private.
Thanks Kaj, will look it over...

I'm trying out BitBucket with Git for now, the control over who can update being for now the deciding factor.  I have the following setup in mind:
(sorry, bit of a crude sketch)
It's entirely probable that I'm using it naively and/or inefficiently, but so far I have the ME and BITBUCKET parts working just as I would have hoped. I'm pretty sure there's a million intricate parts to learn, but feel this is a good start. Am I overlooking anything obvious?
If I set up the link to the web host from the ME area, does that become available to the collaborator? (don't want it to)

Last message posted 34 weeks ago.